I have migrated my store or changed CMS and I no longer see the old reviews

If you have migrated your store or changed CMS, it is possible that the old reviews still exist in Revi but are not displayed in the new store. The most common reason is that during the migration, the IDs or internal product references change, so the old reviews no longer match the new products.

Before opening a ticket, check this:

1. Make sure you are in the correct store in your Revi panel.
2. Verify that the current domain and integration correspond to the store where you want to display the reviews.
3. If you have changed platforms or modules, confirm that the new integration is installed and active.
4. If the problem affects product reviews, check if the migration has changed the old product ID to a new product ID.
5. If you need to migrate product reviews, prepare an Excel or CSV with the correspondence between the old product and the new product. The column names are not important, but the order and content must be clear. It must include at least:

• Old product ID
• New product ID

1. It is recommended to use product IDs. If you do not have them, SKU, reference, or EAN may work, but there is a higher probability that some relationships will not migrate correctly. In that case, it is important that all new products are already synchronized.
2. If you see two stores in your account after the migration, it is not always an error. It can be done to maintain the historical information of the previous installation and the relationship of the reviews with old orders. If that old store is no longer used, it can remain inactive, but the history is preserved.

Open a ticket if:

• the reviews exist in Revi but are not displayed in the new store
• two stores appear after the migration and you do not know which corresponds to the old installation or the new one
• the CMS change has affected specific products or all product reviews
• you need Revi to manually migrate the reviews using the Excel or CSV of old and new IDs

Include in the ticket:

• Old and new URL, if applicable
• Source CMS and destination CMS
• Approximate date of the migration
• whether the problem affects store reviews, product reviews, or both
• Excel or CSV with old product ID and new product ID, if you need to migrate product reviews
• if you do not have IDs, SKU, reference, or EAN, keeping in mind that new products must be synchronized
• screenshots of the store or stores you see in the panel
• if two stores appear, indicate which is the old installation and which is the new one if you know

If the CMS also changes together with the domain, review the order IDs as well. To avoid duplicates or mixed data, orders from the new CMS should ideally have different IDs or start with a higher numbering than old orders. In many cases, a new connection is created to separate the previous integration from the new one and preserve the history.