Key takeaways
- Decide early where reviews live and whether the export is usable
- Agree a rule for reviews attached to discontinued or merged products
- Never move reviews onto a product they were not written about
- Review data contains personal data, so moving it needs a lawful basis
- Rating markup must reflect reviews visible on that page
- Verify counts per product after launch against the old platform
Product data gets migrated because it is obviously essential. Reviews get migrated in the last week, badly, because nobody listed them as a deliverable.
They matter commercially and they matter for search, so they deserve the same planning as the catalogue.
Decide the questions early
- Are the reviews held in your platform, or in a third party service?
- Does that service export in a format the new platform can read?
- What happens to reviews attached to products that no longer exist?
- Does the review structured data move with them, and will it still be accurate?
- Are reviewer names and email addresses personal data you are entitled to move?
Question five surprises people. Review data usually contains personal data, and moving it between systems is a processing activity that needs a lawful basis like any other.
Orphaned reviews
Every migration produces reviews attached to products that are being discontinued or merged. You need a rule, agreed in advance:
- Product merged into a replacement: move the reviews if the products are genuinely equivalent, and do not if they are not
- Product discontinued entirely: reviews go with it, and the page returns gone rather than redirecting to an unrelated product
- Product split into several: a judgement call, and usually the reviews stay with the closest successor
Moving reviews onto a product they were not written about is misleading. It is also the sort of thing that erodes trust when a customer notices.
Structured data has to stay truthful
If you emit review or rating markup, it must reflect reviews that are visible on that page.
Keep the rendering crawlable
Reviews loaded only by JavaScript after an interaction may not be seen. If reviews are part of why the page ranks, they need to be in the rendered HTML.
Check the rendered source after migration rather than assuming the widget behaves the same way on the new platform.
Verify after launch
- Review counts per product, compared against the old platform
- A sample of products checked manually for correct attribution
- Structured data validated against what is visible
- Any review page or feed URL included in the redirect map
Reviews are one of the few things a competitor cannot copy. Losing them in a migration is an avoidable own goal.
Frequently asked
Questions readers ask
How do I migrate product reviews to a new platform?
Confirm where the reviews are held, whether that service exports in a format the new platform reads, and what happens to reviews on products that no longer exist. Agree those rules before the migration rather than in launch week.
What happens to reviews for discontinued products?
If the product merged into a genuine equivalent, the reviews can move. If it is discontinued entirely, they go with it and the page returns gone. Moving reviews onto an unrelated product is misleading and customers notice.
Can I keep my star ratings in search results after migrating?
Only if the markup reflects reviews that are actually visible on the page. Carrying an aggregate rating across to a product that does not show those reviews is a misrepresentation and risks a manual action rather than a ranking dip.





