Migration and data portability

Italiano · Deutsch · Français · Español · Português

You can bring your existing reviews in from a CSV file, and take them out again at any time. Both are on the Import page. It is not in the main menu: open it from the guided setup or from Settings.

Importing

The import reads a CSV file from Judge.me or Yotpo (recognised by their column names) and, for any other file — Loox included — looks for the usual column names. The Loox path is not verified against a real Loox export: the preview shows what would happen and names any field it could not find. Photos and “verified” badges in the old file are never imported: an imported review is always pending and never verified. The columns below are the Judge.me names; you can also rename the headers of any file to match them.

Columns

Column names are not case sensitive.

Column	Needed	What it is used for
`rating`	Yes	The stars, from 1 to 5. Values such as `5`, `5.0` or `5 stars` are accepted.
`body`	Yes	The text of the review, up to 4,000 characters. HTML is reduced to plain text.
`reviewer_name`	Yes	The name shown with the review.
`product_id`	One of these five, to match the product	The Shopify product ID, in the form `gid://shopify/Product/123`.
`product_handle`		The product’s handle in your store.
`product_url`		A product address; the part after `/products/` is used as the handle.
`sku`		A variant SKU.
`product_title`		The product’s title.
`title`	No	The review’s title.
`reviewer_email`	No	Kept, encrypted, to answer deletion requests. It is never shown on your store.
`created_at`	No	The original date of the review. It is kept.

Other columns are ignored, including published and reply: a review’s published state and your public reply are not carried over (see below). The file may be saved by Excel (with a byte-order mark) and may use Windows line endings.

The verified column is not read. A verification claim inside the file you are importing is not proof of anything. Imported reviews are never marked as verified purchases. See below.

How a row finds its product

Each row is matched to a product in your catalogue, strongest signal first:

product_id, or product_handle or the handle inside product_url: an exact match. The review is imported.
sku: a probable match, if the SKU belongs to exactly one product. The review is imported.
product_title: never enough on its own. The row is left out.

If a SKU belongs to several products, or no product matches, the row is left out, not attached to the closest-looking product. Sync your catalogue first (step 2 of the guided setup): a product the app does not know cannot be matched. Products you deleted in Shopify are not matched either.

Step by step

On Import, choose the file with Choose the file.
Select See what would happen. This runs exactly the same checks as the real import and writes nothing.
Read the preview:
- to import: rows that will become reviews;
- to decide: rows with no clear product. They are left out of the import, and the preview and the result give how many there are;
- rows skipped: rows the file itself cannot supply, listed with their line number, for example “Row 91: «reviewer’s name» is missing”. The first 20 are listed, followed by how many more there are.
If you are happy, select Import for real. The file you chose is sent again for this step.
The result card shows how many reviews were imported, how many were already there, how many were left out and how many rows were skipped. Past imports are listed under Previous imports.

Line numbers are counted as in a spreadsheet: the header is line 1, so the first review is line

If the file cannot be read at all, for example because a quote is never closed, the app tells you the line where the problem is.

Importing the same file twice

Importing the same file again does not create duplicates: each review is recognised from its content (product, author, rating and text), so rows already imported are counted as already there. The same holds if you re-sort the file or add columns. The same words left on two different products stay two reviews.

What the reviews look like after an import

They are marked Imported as their source and Not verified. A verified purchase can only come from a request sent by this app for a real order. See Collecting reviews.
They all arrive Waiting, whatever your old app had decided. Nothing appears on your store until you publish it. If you have many, Publish all waiting on the Reviews page publishes them in one step.
Public replies written in your old app are not imported. You can write a new reply on the review.
Photos and videos are not imported: the file carries text only.

Rows that were left out

The preview and the result show how many rows were left out because no product could be matched. To import them, add a product_handle or a product_url that matches your catalogue (or a correct product_id) to those rows in your file, and import it again. Rows already imported are recognised and not repeated.

Exporting

You can take all your reviews out whenever you want, on every plan, with no extra step.

On Import, under Export, select Export the reviews. The same button is in Settings → Data and privacy.
A banner says File ready. Select Download the file within two minutes: the link expires quickly, and you can prepare a new one at any time.

The file is a UTF-8 CSV named recensioni-<date>.csv, with these columns: product_id, rating, title, body, reviewer_name, created_at, status, verification, source, reply.

It is a file this app can read back: a test checks the round trip. Reviews imported from an export arrive as Waiting and Not verified, like every imported review: the import does not apply a published state. If you want them live, use Publish all waiting after the import.
It does not contain customers’ email addresses or photos.
Complete: an export holds every review of your store. A very large store (over 50,000 reviews, or a very large amount of text) gets a short message instead of a partial file. Write to info@ifgecommerce.com and we will prepare the set for you.

Exporting is also what you should do before uninstalling: after your store’s data is erased, there is nothing left to export. See Installation.

If something goes wrong

See Troubleshooting.