Migration — Import Existing Product Reviews
Got a review export from your old review provider or in-house solution? Here's how to import it.
General Import Guidelines for your Product Reviews
Reference Files to Help
- Basic Google Import Template - this is a sample template with columns and advanced data inserted in
Exporting Reviews From Your Previous Review Provider
Before importing your existing Product Reviews into ResellerRatings, you’ll first need to export your review data from your current review platform.
Most providers allow review exports in CSV or Excel format, though some platforms may require assistance from their support or account management teams.
This guide explains:
- what data to export,
- supported file formats,
- and how to export reviews from common review providers.
What Can Be Imported Into ResellerRatings?
Depending on the data available from your previous provider, we may support importing:
- Product Reviews
- Product Catalog Data
- Product Images
- Custom Questions
- Experience Indicators
- Product Attributes
- Product Q&A Content
- Product Taxonomy Relationships
Supported File Formats
We currently support:
- CSV (.csv)
- Excel (.xlsx)
Step 1: Download Your Export File from your existing provider
Export your reviews from your current platform (e.g., Yotpo, Trustpilot, PowerReviews, Stamped, etc.) in CSV or Excel format.
Step 2: Open Your File in Excel or Google Sheets
Different providers use different column names, so we need to match those to our system.
Once opened:
- Review the first row of your spreadsheet
- These values are your column headers
- Rename each column to match the ResellerRatings import format below
Step 3: Match Your Columns to RSR’s Format
🛠 Example Conversion
| Your CSV Export columns | ResellerRatings | |
| Name | rename header to ... | reviewer_name |
| Review Body | rename header to ... | review_text |
| Product Title | rename header to ... | product_name |
| Score | rename header to ... | rating |
| Submitted On | rename header to ... | review data |
| Product Page URL | rename header to ... | URL |
| rename header to ... | review_email |
📤 Step 4: Save Your File
•Save as .csv or .xlsx
•Make sure the first row contains only the renamed headers
•Double-check that no required columns are missing
Step 5: Send to Your Account Manager or Upload it into the Dashboard
Email the cleaned file to your ResellerRatings onboarding manager or upload it via the dashboard import tool.
We’ll take care of the rest. 💪
Let's import it - You can import product reviews in two ways
- via dashboard
- Go to Setting > Product Reviews > Import Reviews
Format and Description of All Columns
| product_name | This name of the Product in string format. For example ‘Canon 5d Mark II’ or ‘Rachel Roy Red sweater’ |
| sku | A unique product identifier |
| url | The product page that goes to the product itself (ie https://www.mystore.com/product/id |
| rating | Overall rating out of 5. Integer value 1 to 5 |
| review_text | The review text body. String value |
| review _date | The date the review was submitted in your system. Format as follows (Y-m-d H:i:s) or (2016-12-1 17:50:22) |
| reviewer_name | Username of the reviewer |
Optional data field for more robust syndication to Google for syncing
Why Optional Fields Matter
Providing additional data helps power:
- Better product syndication
- Richer Google integrations
- Advanced segmentation and analytics
- More detailed shopper filtering
- Enhanced reporting
- Future advertising and publisher integrations
| mpn | Manufacturing Part Number - used in Google Syndication |
| GTIN | Global Trade identification Number, used in both Google and Bing syndication |
| Review_email (Optional but must have for Google Syndication) | The email address of the reviewer. We use this value to ensure it is an authenticated review and syndicate to Google. |
Optional data field for more robust display usage
The following data fields helps organize and categorize your product listings in your dashboard so you can see collection rates by brand and category. It also helps your teams start pulling measurement data from various categorical trends.
Importing Optional data helps
- Data analytics and deep dive segmentation on the platform
| brand | Expands search and data segmentation and insights options on the dashboard - The Brand the product belongs to, “Nike, Puma, Coke, etc” |
| category | Expands search and data segmentation and insights options on the dashboard - The Category the product belongs to, ‘Apparel, etc’. |
| Title | The title or headline for the review.The beginning of the review body is generally used if no title is provided |
| Invoice | If the review was solicited after the sale, provide the invoice of the order made by the reviewer. |
| Location | Location the reviewer is from (city name).This will show below the reviewers name when rendered. |
| verified | Is this a verified review (yes , or no).This will show the user is verified. |
| recommend | Is this a recommended review, yes or no.This will display a recommended checkmark by the review. |
| status | Approved or Rejected – the status of the review content in case old review content is rejected for flag violations. |
| review_id | Older review_id matching to your system.This will be critical for UGC matching. |
Advanced Import - Custom Questions, Experience Indicators, Parent / Child
At this point, you can always contact us (chat) or give you account rep a call. But here are some instructions for even MORE advanced data import.
Importing Custom Questions and Attributes
-
Custom questions are effectively specific feedback questions your team uses to get more information regarding products. For example, ‘How was the unboxing experience of this product?’
-
Experience Indicators are specific attributes to a product that your customers can rate. For example, the FIT of a shoe or the COMFORT
🎯 Why Import Custom Questions and Attributes with Your Reviews
1. Richer, Structured Data = Better Shopper Decision-Making
Custom questions (like “Did the product fit as expected?” or “What’s your skin type?”) help surface nuanced information that standard star ratings can’t. This leads to:
•Fewer returns (because shoppers know what to expect)
•Faster purchase decisions
•Stronger trust in the review content
Uploading Experience Indicators
Let's start off with Experience Indicators. Uploading custom question data you may have had in the past is relatively easy providing you can output the correct format. 
Formatting your Custom Attributes
Custom attributes and custom data are PART of the custom import data review files. They are not separate files. Include all the data into one file.
-
Custom Attribute Rules
-
Limit of 5 custom attributes per SKU
-
Each consist of two elements (attribute name and rating)
-
Attribute Ratings are integers from 1-5
The column names follow the format: the column corresponding to the attribute name is “attribute_x”, and its corresponding rating column name is of the form “attribute_rating_x”, where x is an integer from 1 – 5.
For example, if there were two custom attributes, the columns would look like:
attribute_1,attribute_rating_1,attribute_2,attribute_rating_2
With two custom attributes for two reviews, this would look like:
If a review doesn’t have a rating for a given custom attribute, both the attribute and attribute rating can be left blank.
Importing Custom Questions
Custom Questions are very similar to Custom Attributes in formatting.
Custom questions consists of three column elements
-
A short form question
-
The question model type
-
An Answer
For example, if there were two custom attributes, the columns would be:
question_1,question_type_1,answer_1,question_2,question_type_2,answer_2
With values from two reviews your csv would include the following:
As with custom attributes, if a review does not contain an answer for a particular question, those values can be left blank.
Ingesting parent / hierarchy data
Sometimes you may want to collect reviews for individual products, but display them all under an aggregate rating. For example, perhaps you have sunglasses that have different colored frames, all with different SKUS. But you want to use the aggregate of that content.
All you have to do when ingesting content is to create a new column with parentID (which can be a sku).
Did this answer your question?