How to Switch Shopify Review Apps Without Losing Your Star Ratings and Photos

You can switch Shopify review apps without wiping the star ratings and photo proof that already convert on your product pages. The safe path is export first, map product handles, run a small test import, then cut over widgets and rating schema in one pass. Uninstall the old app only after the new widgets look right for a week.

Most merchants delay the move because they fear a blank storefront. That fear is rational. Northwestern's Spiegel Research Center found that products with five reviews have a 270% greater purchase likelihood than products with none. Before you change apps, decide why you are leaving, what must survive, and which app will own display going forward. If you are still comparing tools, start with our Judge.me vs Loox vs Yotpo vs Okendo comparison, then come back here for the migration steps.

This guide uses three practical methods in order: export from the current app, map and import into the destination, then cut over widgets and schema. Do them in that sequence. Skipping export is how stores lose years of proof in one uninstall click.

Why Do Merchants Switch Shopify Review Apps in 2026?

Merchants switch when pricing, photo widgets, request emails, or page-speed weight no longer match the store they run today. The reviews themselves are portable. The display stack is what changes.

Common triggers include hitting a paid tier you no longer want, needing stronger photo galleries, wanting lighter theme scripts, or consolidating after a rebrand. Bazaarvoice reports that 88% of shoppers consult ratings and reviews before a purchase, so the library you already collected is not a vanity metric. It is conversion infrastructure.

Pricing alone is a weak reason to switch if the new app cannot import media cleanly. A cheaper monthly bill that strips photo reviews can erase more conversion than it saves. Measure the switch against conversion and support tickets, not against the invoice line item.

Treat the switch as a data move plus a theme cutover, not as a fresh start. You keep ratings, bodies, dates, and media URLs when the export is complete. You rebuild widgets, request emails, and schema ownership on purpose.

What Should You Inventory Before You Export a Single Review?

Inventory totals, media, product identifiers, and live widgets before you touch export. Skipping this step is how stores discover missing photos after they already uninstalled the source app.

Capture these numbers and screenshots first:

• Published review count by product and storewide, plus any pending or hidden queues.
• Photo and video reviews, because media often lives on the old app's CDN.
• Merchant replies, custom questions, and any verified-buyer flags the export may omit.
• Widget placement on product, collection, and home templates (desktop and mobile).
• Request email timing, discount rewards, and any Klaviyo or Flow triggers tied to the old app.

Freeze major catalog edits for the cutover window. Renaming handles mid-migration orphans rows. If marketplace imports still matter after the switch, keep our Amazon, AliExpress, and marketplace review import roundup nearby so day-two seeding stays separate from the CSV move.

Hot take: The migration risk is not the star count. It is photo CDN URLs that die after uninstall, plus two apps writing AggregateRating markup at once during the overlap week.

How Do You Export Reviews From Judge.me, Loox, Yotpo, and Similar Apps?

Export a full CSV (or vendor export) from the old app while it is still installed, then store a copy outside Shopify. Every major review app supports export. Do not uninstall first.

For Judge.me, open Reviews, use the Export dropdown, and choose published, hidden, or archived. Exports over 25 reviews are emailed, and download links expire in about three hours. Judge.me also notes a 100,000-review cap per CSV file, so large catalogs need filtered batches.

For Loox, Yotpo, Okendo, Stamped, and Junip, use each app's Settings or Data export path and download CSV (or request the emailed file). Open the file in a text editor before Excel. Spreadsheet apps rewrite dates, and slash dates are a common silent import failure.

Verify the export before you celebrate:

1. Row count matches published plus hidden reviews you expect to keep.
2. Product handle or product ID is present on nearly every row.
3. Rating is an integer from 1 to 5.
4. Photo or media URL columns resolve when you open a sample of links.
5. Non-English and emoji reviews still look correct (UTF-8).

Download media locally when URLs point at the old vendor's CDN. Competitor field guides such as AgentReady's migration fields rundown are right about this: ratings and text usually survive; product references, dates, verified flags, and photos are what fray.

How Do You Map and Import the CSV Into Your New Review App?

Install the destination app, map required columns to its template, test-import 10 to 20 rows, then run the full file in batches. Product handle mismatches are the most common silent miss.

Required fields almost always include product handle (or product ID), rating, review date, and reviewer name. Optional fields cover title, body, media URLs, shop reply, and email. Keep ISO dates when you can. Convert ambiguous slash dates before upload.

If you are moving into WiseReviews, the CSV path lives under Reviews, then More actions, then Import via CSV. Download the template, map columns, and keep files at or under 3,000 rows per the CSV import docs. Product handle, rating, review date, and reviewer name are required. Media URLs can be comma-separated. CSV uploads count toward the hold limit (100 on Free, including unpublished; 50,000 on Standard; unlimited on Plus) but do not spend Free's lifetime 300 marketplace URL and Chrome extension allowance.

Practical import order:

1. Sync products in the new app so handles resolve.
2. Upload a 10 to 20 row slice from your bestsellers.
3. Confirm ratings, dates, photos, and product pages before the full run.
4. Import remaining batches. Spot-check one SKU after each batch.
5. Reconcile totals against the export. Investigate orphans instead of uninstalling.

On Free, if you are already near the 100-review hold limit, publish strategy matters: delete or leave unpublished only reviews you do not need on the storefront, or upgrade before a large file. Deletes free hold room; they do not refund marketplace imports. For Etsy-specific star-rating moves, pair this CSV flow with our Etsy-to-Shopify review migration walkthrough.

If your destination app offers a one-click importer for Judge.me, Loox, or Yotpo exports, still keep your own CSV. Vendor importers are convenient, but your downloaded file is the recovery copy if a mapping fails. Prefer destinations that let you repair unmatched rows in-admin instead of dropping them, then re-import only the fixed rows after you confirm the importer fingerprints duplicates safely.

Agency handoffs need one more rule: the client owns the export. Download it to a shared drive the merchant can open without the old login. When the agency later leaves, the review library should not be trapped inside a freelancer's app account.

How Do You Cut Over Widgets and Keep Only One Rating Schema?

Enable the new app's storefront widgets, disable the old widgets in the same session, and leave only one app emitting AggregateRating markup. Dual schema during overlap is a common rich-result foot-gun.

Cutover sequence that keeps social proof visible:

1. Install new widgets on a duplicate theme first when you can. Preview product and collection pages on mobile.
2. On the live theme, turn on the new Product Reviews and Star Rating blocks (or equivalent).
3. Immediately disable the old app's blocks and app embed so shoppers do not see two widgets.
4. Confirm only one app writes review schema or shared rating metafields.
5. Keep the old app installed for at least a week with display off, in case you need another export.

For WiseReviews on Online Store 2.0 themes, enable the app embed, then add Product Reviews and Star Rating blocks from the widget installer. Leave the Product picker empty on product templates so each page shows its own reviews. Collection star ratings and featured carousels are optional once the product pages look right.

Rich snippets are not owned by the old brand name in your theme. They follow structured data. After cutover, test a product URL in Google's Rich Results Test. If you use WiseReviews, the SEO and rich snippets docs show how to add aggregateRating to theme schema when your theme does not inject it automatically.

What Breaks Most Often When You Switch Review Apps?

Photos on vendor CDNs, renamed product handles, date formats, and verified badges that do not re-verify in the new app. Plan around those four, not around the headline review count.

Fix patterns that save a re-import weekend:

• Broken photos: archive media before uninstall; prefer destinations that re-host files into Shopify Files.
• Orphan reviews: sync the catalog, then remap handles or product IDs for renamed SKUs.
• Wrong dates: convert to ISO 8601 with timezone before upload; never let Excel "help."
• Verified badges: treat imported verification as source-asserted unless the new app re-checks orders.
• Duplicate schema: one AggregateRating emitter only until Google re-crawls.

Photo-heavy catalogs should care most. Bazaarvoice found that 60% of shoppers would rather buy a product with 10 reviews that include user images than 200 text-only reviews. Our photo vs text reviews breakdown covers why visual proof still wins after a migration. If Shop App syndication is part of your stack, remember CSV-migrated reviews may not stay Shop-eligible the same way partner-synced reviews do, as covered in our Shop App review import guide.

What Should You Check in the First Week After Switching?

Reconcile counts, watch conversion on seeded SKUs, confirm new request emails send once, and keep the old app installed with widgets off until you trust the cutover. Rushing uninstall is the expensive mistake.

Week-one checklist:

• Storewide and top-20 product review counts match the export (within orphan repairs).
• Star summary near the price and full review block are visible above the fold on mobile.
• Only one review request email fires per order.
• Page speed and theme console show no duplicate review scripts fighting each other.
• Google Rich Results Test still reports aggregateRating on a reviewed product URL.

Spiegel's work also found conversion lifts of about 190% for lower-priced products and 380% for higher-priced ones when reviews were displayed, with purchase likelihood peaking between 4.0 and 4.7 stars. Do not "clean" the library into a fake 5.0 average during migration. Keep honest critical reviews. For the broader conversion case, see how product reviews increase Shopify conversion rates.

Bazaarvoice also reports that having just 10 product reviews can lift conversion by 45%. After cutover, prioritize request emails on SKUs that fell below that floor because of mapping misses, not vanity volume on already-proven bestsellers.

What Legal Rules Still Apply When You Republish Migrated Reviews?

Keep review text and ratings unedited, stay honest about badges, and do not invent verified-buyer claims the destination app cannot support. Migration is republishing customer words, not rewriting marketing copy.

Practical rules for 2026:

• Do not alter star ratings or rewrite negative reviews during CSV cleanup.
• Do not present marketplace-imported or CSV-imported reviews as if they were written on your store if badges imply otherwise.
• Disclose incentives clearly when you restart review-request rewards.
• Remove a review quickly if the original reviewer asks.

The FTC Consumer Reviews and Testimonials Rule has been in effect since October 21, 2024. It targets fake, bought, and misleading reviews. A clean CSV move of real customer reviews is normal commerce. Fabricating volume or suppressing only the critical ones during "cleanup" is not.

Bottom line: switch Shopify review apps by exporting while the old app still works, mapping handles carefully, test-importing, then cutting over widgets and schema with one emitter. Archive photos before uninstall. Keep the old app installed for a week with display off. Your star ratings and photo proof can survive intact when you treat the migration as data ops, not as a theme experiment.