How to Export Your Reviews From Yotpo (Step by Step)

How do you get your reviews out of Yotpo?

Start in the Yotpo admin and look for an export where your reviews are managed, then check any account, data, or settings area as well. Admin interfaces get reorganised and what is available can depend on your plan, so treat the exact path as something to find rather than something to memorise. What you are looking for is a file containing every review, not a filtered view of the current screen.

If there is no export you can run yourself, or the one you find returns less than you need, ask Yotpo support for a full export of your review data and be specific about what full means to you. Asking is reasonable: these are reviews your customers wrote about your products. Do all of this while the subscription is still active. The worst version of this job is the one that starts after the cancellation, when access has already narrowed.

• Look for the export where reviews are managed, then check the account and data areas too.
• If you cannot find one, or your plan does not include it, ask support in writing.
• Ask for the media as well as the review records, and ask what format each arrives in.
• Run the export before you cancel anything, not after.
• Keep the original file untouched and do all your editing on a copy.

What is in the export, and what is not?

Open the file before you plan anything around it. A review export generally carries the parts of a review that fit in a table: the star rating, the title and body, the reviewer name, the date it was written, and some identifier that ties the review to a product. Column headers differ between platforms and change over time, so match columns by meaning rather than by the name you were expecting.

What tends not to fit in a table is everything that made a review an object rather than a row. Photos and videos are files stored somewhere else. Public replies you wrote may be held separately from the review they answer. Helpfulness votes, Q&A threads, and the verified-buyer flag may or may not appear. None of that is specific to Yotpo. It is the shape of the format, and it is why an export is the start of a migration rather than the whole of one.

• Usually present: rating, title, body, reviewer name, date, a product identifier.
• Worth checking for: replies, verified-buyer status, moderation state, helpfulness votes.
• Usually separate or absent: photos, videos, and Q&A content.
• Confirm which product key you have (handle, SKU, or product ID) before planning the import.

Why do photos and videos need their own job?

Photo and video uploads are hosted on the review platform's own infrastructure, so the most a spreadsheet can carry is a link to a file on a host the next app does not control. Some import tools follow those links and fetch the files. Many do not, and the ones that do can only succeed while the links still resolve. That is the detail that catches people: cancel first, and the media may stop being reachable before anyone has fetched it.

So treat media as a second export with its own deadline. Pull the files down while the account is active, store them somewhere you control, and keep a record of which file belongs to which review. Photo reviews tend to be the ones a shopper actually stops on, which is why losing them costs more than the row count suggests.

Which reviews are not yours to take?

Before you count what you might lose, count what was actually yours. Review platforms syndicate content between merchants and from brand partners, and reviews imported from marketplaces can sit in the same list as reviews your own customers wrote. A review that arrived through a network arrangement is not necessarily part of what you can export and take with you, and the total on your widget can be larger than the total you own.

The verified-buyer flag deserves the same care. It is a claim the old platform made on the strength of order data it could see. If the flag does not survive the export, do not reapply it by hand to reviews you cannot tie back to an order. Re-derive it from your Shopify order history and leave it off wherever the match fails. FTC rules on reviews turn on authenticity and on not misrepresenting what a review is, so a badge that says verified should be one you can substantiate.

How do you check the file before you trust it?

Do this with the file open next to the old dashboard. Take a store showing 3,412 reviews in Yotpo whose export opens with 3,289 rows. Those 123 missing reviews are not a mystery to solve later. They are the work in front of you now, and they are usually some combination of reviews still pending moderation, reviews marked as spam, reviews attached to products you have since deleted, and syndicated reviews that were never yours to move. Keep going until every one of the 123 has a reason. The figures here are illustrative, but the exercise is not.

The reconciliation is arithmetic, so it either closes or it does not. A gap you cannot explain before the import is the same gap, unexplained, after it, except that by then it is showing on your product pages.

• Row count against the dashboard count, with every row of difference accounted for.
• Oldest and newest review dates in the file against the oldest and newest you can see.
• Average rating and star distribution in the file against what the widget reports.
• Product identifier populated on every row: count the blanks now, not after the import.
• How many rows reference a photo or video, so the media job has a target number.

What happens to your star ratings during the cutover?

Star ratings in Google are not stored by Google. They are read on each crawl from the structured data your review app prints into the page, so the risk in any switch is a window where the old markup has gone and the new markup is not yet populated. Keep exactly one set of review markup live at any moment, and order the cutover so the new app is rendering before the old widget comes out.

Even with a clean handover, expect the numbers to move before they settle. The average usually catches 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 a hundred reviews never made the trip, that is the export gap arriving in your search results, which is the argument for reconciling before the cutover rather than after.

There is a version of this problem that survives the migration untouched. Many review apps render reviews for the shopper standing on the page and stop there, so the text is legible to a person and not to a crawler or an answer engine. A migration is the one moment your whole corpus is in your hands as a file, which makes it the natural point to ask whether the next app makes those reviews readable and citable in search and AI answers, not only visible on the product page. That gap is what BeyondReviews is built to close.

How do you confirm the import reconciled?

Reconciliation is a count, not an impression. After the import, put three numbers side by side: what the old dashboard reported, how many rows the export contained, and how many reviews the new app now shows. Using the example above, that is 3,412 and 3,289 and whatever the new app says. If the third number matches the second, everything you exported arrived. If it is lower, 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 come back after a day means little, while one that has not come back after a week is worth investigating.

• Total reviews in the new app against the row count in the file.
• Average rating and star distribution against the old 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.
• Media: how many reviews should show a photo, and how many actually do.
• Structured data on a live product page, run through a validator, showing the new aggregate.

What if you read this and decide to stay?

Some merchants work through the export, see the size of the media job, and conclude the move is not worth it this quarter. That is a legitimate answer, and the work was not wasted. You now hold a dated copy of your review corpus somewhere you control, which is worth having whether or not you ever switch. Put a reminder in the calendar and repeat it.

It is also worth weighing the whole account rather than the review widget. Yotpo is a suite, and if you use the loyalty or subscription parts, reviews are the smaller half of what you would be moving. The point of doing the export first is that it makes the decision reversible, and lets you make it with the data already in your hands rather than as a condition of leaving.

Frequently asked questions