Migrating From Yotpo to Judge.me: The Complete Guide

Should you move off Yotpo at all?

Start here, because the migration is a week of attention and the answer is not always yes. Yotpo is a suite: reviews sit next to loyalty and subscriptions in the same account, on one contract, with one support relationship. Judge.me is a review app. It does not replace a loyalty programme or a subscription engine, and nothing in this guide will make it do so. If you use those parts of Yotpo, moving reviews out does not end the Yotpo bill, it just makes your stack wider.

The honest case for moving is narrower than the alternatives pages usually admit. It applies when reviews are effectively all you use, when the price you pay is set by a platform you have outgrown in one direction and never grew into in the other, or when widget weight on the product page has become a performance problem you can measure. If two of those three are true, the move tends to pay for itself. If none is, the better decision may be to renegotiate rather than migrate.

• Reasons that hold up: you use reviews only, the price is set by a suite you do not use, page weight is measurably hurting you.
• Reasons to stay: loyalty or subscriptions run on Yotpo, or you rely on a syndication or brand-partner arrangement inside the platform.
• A reason that is neither: frustration with one support ticket. Migrations do not fix that, they just move it.
• Check your contract term before you plan a date. Leaving mid-term is a decision about money, not about software.

What does this migration actually consist of?

Three jobs, and they have different deadlines. The first is the review records: the ratings, titles, bodies, author names, and dates that fit in a spreadsheet. The second is the media: photos and videos that live on Yotpo infrastructure, which an export can only point at. The third is the structured-data handover, where the markup behind your Google star ratings stops being printed by one app and starts being printed by another.

Most people scope the first job, discover the second late, and never scope the third. That order is why migrations that look finished on Thursday show a blank rating on a product page the following week. Plan all three before you touch anything, and put the media job first in the calendar, because it is the one with a hard deadline attached to your Yotpo account staying open.

How do you get the reviews out of Yotpo?

Look for an export where your reviews are managed in the Yotpo admin, then check the account, data, and settings areas as well. Admin layouts get reorganised and what a given account can export can depend on the plan, so treat the exact path as something to find rather than something to memorise. What you want is a file containing every review, not a download of whatever the current screen is filtered to.

If there is no self-serve export, or the one you find returns less than you need, ask Yotpo support in writing for a full export of your review data, and be specific about what full means to you. Do this while the subscription is active. There is a longer walkthrough of this step, including what a review export can and cannot carry, in the dedicated export guide.

• Run the export before you cancel anything, and keep the original download untouched as a backup.
• Ask explicitly whether merchant replies, verified-buyer status, and moderation state are included.
• Confirm which product key the file uses: a product ID, a handle, or a SKU.
• Count how many rows reference a photo or video, so the media job has a target number.

Does Judge.me import the file, or do you build it yourself?

Review apps commonly offer importers aimed at specific competitors, and those tools change more often than any article about them. So the only current answer is the destination's own documentation, read on the day you migrate. Before you shape a single column, get three things in writing from it: which product key the importer matches on, whether it accepts the original review date rather than stamping the import date, and whether it fetches images from URLs or expects you to have the files.

Those three answers determine the whole shape of the work. If the importer matches on handle and your Yotpo file carries an internal product ID, you need a lookup table built from a Shopify product export before anything else happens. If it stamps the import date, every recency signal in four years of reviews collapses into one day, and you would rather know that now than after. If it does not fetch images, the media job is entirely yours.

• Which product key does it match on, and does your file contain that key on every row?
• Does it preserve the original review date, or overwrite it?
• Does it fetch media from URLs, and does it need those URLs to still resolve?
• What does it do with rows it cannot match: skip them silently, or report them?

What does not survive the move?

Assume nothing outside the core five fields travels. Rating, title, body, author name, and date are reliable. Merchant replies usually sit in a separate table and are frequently absent from an export. Verified-buyer status is a claim the old platform derived from order data it could see, not a portable flag, so either the destination accepts a verified column or it re-derives the status by matching reviewer emails against your Shopify orders. Confirm which, rather than assuming the badges reappear.

Two categories deserve separate thought. Photos and videos are files on Yotpo storage, reachable only while the account is live, which is the deadline mentioned earlier. And syndicated reviews, the ones that arrived through a network arrangement rather than from your own customers, may not be yours to take at all. That is why the count on your widget can be legitimately larger than the count you can move, and why discovering the difference before the cutover is much cheaper than discovering it after.

• Usually travels: rating, title, body, author name, original date, and a product identifier.
• Often does not: merchant replies, helpfulness votes, Q&A threads, moderation state.
• Never as files: photos and videos, which export as links to storage you do not control.
• May not be yours: syndicated reviews and reviews supplied through brand-partner arrangements.

How do you sequence the cutover so your star ratings stay?

Google does not store your ratings. It reads AggregateRating and Review markup from the page on each crawl, so the stars exist only while some app is printing that markup. Remove Yotpo on Monday, finish populating Judge.me on Thursday, and every product page crawled in between reports a product with no rating. The fix is ordering, not luck: install and populate the new app while the old one is still rendering, verify valid markup on real product pages, then remove the old widget. One set of review markup live at every moment, never zero and never two.

Even with a clean handover, expect movement before things settle. The average rating tends to catch up quickly. The review count can lag, because the aggregate has to be recrawled and re-associated with the product. What is not a lag is a permanent shortfall. If two hundred reviews never made the trip, that is the export gap arriving in your search results, several weeks after the moment when it was cheap to fix.

• Install and populate Judge.me while Yotpo is still rendering on the product page.
• Validate structured data on three real product pages, not on a template preview.
• Confirm exactly one aggregate rating is present per page before removing anything.
• Remove the Yotpo widget last, and only after the checks pass.

How do you know the migration worked?

Reconciliation is arithmetic, so it either closes or it does not. Put three numbers side by side: what the Yotpo dashboard reported, how many rows the export file contained, and how many reviews Judge.me now shows. If the third matches the second, everything you exported arrived, and any difference between the first and the second is the export gap you should already have explained. If the third is lower than the second, the difference is import failures, and import failures are almost always product mapping.

Then leave it a week and look again in Search Console. Product pages are recrawled on their own schedule, so a star snippet that has not returned after a day means little, while one that has not returned after a week is worth investigating rather than waiting out.

• Total reviews in Judge.me against the row count in the file, with every row of difference explained.
• Average rating and star distribution against the old Yotpo dashboard.
• Ten product pages checked by hand: your two busiest, and one with a single review.
• Oldest review date, to confirm history was not silently truncated to the import date.
• How many reviews should show a photo, against how many actually do.

What if you work through this and decide to stay?

That is a legitimate outcome, and the work was not wasted. You now hold a dated copy of your review corpus in a place you control, which is worth having whether or not you ever switch apps. Judge.me is cheaper and its review HTML is more readable to crawlers, and both of those are real. Yotpo keeps reviews, loyalty, and subscriptions on one contract, and for a store that uses all three, that is also real. The comparison only resolves once you know which description is yours.

One thing is worth deciding separately from the app choice, because neither answer fixes it. Most review apps are built for the shopper standing on the product page, so review text can be perfectly visible to a person and still be hard for a crawler or an answer engine to read and quote. A migration is the one moment your entire corpus is in your hands as a file, which makes it the natural point to ask whether the reviews you already have are legible to search and to AI answers, not just visible on the page. That gap is what BeyondReviews is built to close, and it survives a migration untouched if nobody asks the question.

Frequently asked questions