Migrating your reviews to Imagyn
A full walkthrough of the import wizard: upload, preview, and what happens to verification along the way.
Before you start
Export your reviews from your current platform. Judge.me, Loox, Stamped and Ali Reviews each have their own export feature in their own app, usually under a Settings or Export menu. A plain CSV works too, as long as it has a rating and a review body column at minimum.
Nothing about your current platform needs to change before you export. Your existing reviews stay exactly where they are until you choose to import them elsewhere.
Upload and analyze
Upload your file in Imagyn's Import & Migration settings. Imagyn reads the column headers and shows you what it detected for each field: rating, content, reviewer name, product reference, and more.
If a column was detected incorrectly, or a field was not detected at all, you correct the mapping right there before anything else happens. Nothing is imported based on a guessed mapping you have not confirmed.
Preview before anything commits
Once the mapping looks right, Imagyn runs a full preview: every row is checked against your real product catalog and your existing reviews, exactly as a real import would, but nothing is written yet.
The preview shows how many rows matched a product, how many need your review because they were unmatched or matched more than one product ambiguously, and how many look like duplicates of reviews you already have.
What happens to verification
An imported review never becomes an Imagyn Verified Buyer review by itself, regardless of what your old platform claimed. If your old platform marked a review as verified, that claim is kept as a private note for your own reference, never shown to shoppers as an Imagyn verified badge.
This is deliberate: Imagyn can only verify a purchase it can actually check, and it never saw the original order for a review imported from another platform.
After the import
Every import is recorded as its own entry in your import history, with its own counts. If something looks wrong, that specific import can be undone on its own, without touching any review that came from anywhere else.
Running the same file through the import a second time will not create duplicates. Rows Imagyn already has are reported as duplicates, not imported again.
See the real feature this guide describes.
Import & Migration →