Review Import
Review import moves the corpus when the store moves house, keeping years of proof alive through the switch.
What review import is
Review import is moving the corpus when you move house: bringing existing reviews into a new review platform or storefront, by file export, app migration, or syndicated feed, so years of collected proof survive the switch.
Why review import matters
Reviews are an appreciating asset attached to a depreciating tool: stores outgrow review apps, replatform, and consolidate, and the corpus either travels or dies with the subscription. A store that switched and started from zero looks brand new in the worst way, empty stars on products with years of happy customers, which makes the import path a real criterion when choosing review software in the first place.
What a clean migration preserves
- The content: text, ratings, photos, and video, exported completely before the old app closes
- The metadata: dates, reviewer names, and product mappings, so history reads as history
- Verification status: purchase-verified flags carried over, or honestly reset where they can’t be
- The display and schema: imported reviews rendering on-page and marked up like native ones
Frequently asked questions
Do imported reviews keep their star snippets in search?
It depends on provenance rules: engines distinguish reviews a store collected firsthand from third-party content, and rich-result eligibility follows those origin policies rather than what the page displays. Reviews migrated between the store’s own systems generally stand; borrowed corpora from other sources face stricter treatment.
What breaks most often in review migrations?
The mappings: reviews orphaned from renamed products, variants collapsing wrong, dates flattening to import day, and photos left behind in the old app’s storage. The fix is a dry run against a product sample and a full export archived before anything is switched off.