Product reviews can disappear, detach from the wrong SKU, or lose context during a platform move. Preserve them because they help shoppers judge products, but keep authorship, dates and moderation status accurate. A review count alone does not prove a good migration.
How to make the decision
Export reviews with stable product keys, author display rules, date, rating, text, images where licensed, and moderation state. Check the target review app or platform’s import format before changing the catalog. Map each review to the correct product or variant and preserve the original date where supported. Rehearse with a product that changed SKU, a discontinued product and a review awaiting moderation. Inspect the public product page and admin record after import. Keep the source export and mapping log so a missing review can be investigated.
Worked example
Illustrative catalog: 320 reviews import and the count matches, but three reviews for a discontinued blue variant appear on the replacement red product. The team separates product identity from SKU, moves only reviews with a defensible match, and archives the rest for support. A spot check compares rating, date, text and product association on ten selected pages. The corrected report shows 317 public reviews and three held for review, not a false 100% transfer.
What to verify
- Is the product mapping traceable?
- Are dates and moderation states retained?
- Have changed and discontinued products been sampled?
- Does the public page match the source record?
Limits and ownership
Do not fabricate reviews, change sentiment or remove negative reviews to make the destination look better. Platform review and structured-data rules still apply.
What to hand over
Save a review-transfer exception list with source review ID, old product, proposed new product and reason for holding it. A merchant reviewer should approve ambiguous mappings. If the destination app changes display rules, retest public pages so an honest negative review is not hidden or detached.
Common question
Can reviews be copied as plain text?
Only if the destination preserves their real context and disclosure; use a supported import path where possible.
Next useful step
Use Migration Rollback Plans: What Must Be Reversible for the adjacent decision. For an implementation review, see Megvi’s ecommerce website development service and bring the source records, proposed checks and open exceptions.
Source checked 28 October 2026: WooCommerce: migration and product review import options. Check current platform settings before changing a live store or report.
The worked example is illustrative and is not presented as a Megvi client outcome.