What to do with old NCR customer reviews and ratings

When NCR Retail Online was discontinued, merchants had to move their storefronts and operational data to alternative platforms such as Magento or WooCommerce. Product descriptions, order history, customer accounts, and inventory records usually receive immediate attention during that process. Customer feedback deserves the same care.

Old NCR customer reviews and ratings can preserve valuable evidence of product quality, service performance, and buyer expectations. They can also create privacy, accuracy, and search visibility problems if copied without review. A careful retention plan helps a business keep useful social proof while removing obsolete, misleading, or legally risky content.

The right approach is rarely to transfer every review automatically. First, preserve the original records, then assess their quality, confirm that they can be reused, and publish them in a way that clearly reflects their source and date.

Start with an evidence-preservation audit

Before changing or exporting anything, create a secure copy of the available review data. Include written comments, star ratings, product identifiers, review dates, response history, moderation status, customer names or display names, attached images, and any internal notes. Export files should be stored separately from the live ecommerce database, with restricted access and a clear retention owner.

Capture the state of the old storefront where possible. Screenshots, archived product pages, and export logs can help establish that a review originally appeared on a particular product page. This is especially useful when product catalogues are being consolidated, renamed, or divided between several new websites.

Keep the review archive separate from sales records. Information about what happens to transaction history after a platform shutdown does not automatically determine how customer testimonials should be handled. A review may refer to an order, but it is a distinct content asset with its own privacy and consent considerations. Businesses managing the wider record-keeping process can also review sales data guidance alongside their feedback archive.

Separate usable proof from legacy noise

Review every entry against a consistent set of rules. Remove duplicate submissions, blank ratings, test records, spam, abusive language, irrelevant comments, and reviews attached to products that no longer exist. Mark content that requires manual investigation instead of making uncertain decisions through an automated import.

Pay close attention to product changes. A review for an earlier model, discontinued colour, altered formula, or different bundle may not accurately describe the current item. It can remain in an archive, but publishing it on a new product page may confuse shoppers. Where the item is substantially unchanged, retain the original date and explain the product relationship when necessary.

Ratings need their own audit. A product with 42 five-star reviews should not appear to have received those ratings recently if they were collected several years ago. Preserve the original submission dates, calculate the imported average accurately, and avoid combining ratings from unrelated products merely to create a stronger score.

Choose where each review belongs

A migrated review can be displayed on the matching product page, placed in a general testimonial area, retained privately for service analysis, or excluded from publication. Product-specific feedback usually has the greatest value on the relevant item page, provided the product identity and version are clear.

For discontinued products, consider an archive page or a replacement-product explanation instead of silently moving every comment to a newer item. A review that says “the previous version fit well” should not be presented as proof for a redesigned product. Linking related products can provide context without rewriting the customer’s original words.

Service reviews may belong on an about page, support page, business profile, or third-party review service rather than inside a product catalogue. Categorising feedback by product, delivery, customer support, returns, and shopping experience makes the migration more useful for both visitors and internal teams.

Protect privacy and preserve authenticity

A customer’s full name, email address, order number, profile image, or location may have been visible in the former system without being appropriate for continued publication. Review the original permission, privacy notice, and applicable data-protection obligations before transferring personal information to a new platform.

Use the smallest amount of identifying information needed to make the review credible. A first name and initial, or a general label such as “Verified customer,” may be safer than displaying a full name. Remove phone numbers, addresses, tracking details, and other information that a customer may have entered accidentally.

Do not rewrite negative reviews to make them sound positive. Minor formatting corrections may be acceptable, but changes to meaning undermine trust. If a review contains an offensive term, personal allegation, or unsupported claim, document the moderation reason and retain the original only in a restricted administrative archive when policy or legal requirements justify doing so.

Incentivised feedback requires additional care. If customers received a discount, loyalty benefit, or promotional reward for leaving reviews, disclose that relationship where required. A separate discount and coupon guide can help teams distinguish ordinary promotions from offers connected to review collection.

Rebuild ratings without misleading shoppers

A new storefront may use a different review application, product identifier, or rating scale. Map the old identifiers to the new catalogue before import, and test the result on a staging site. Check that every review appears beside the correct item and that average ratings match the underlying count.

Avoid presenting imported content as freshly collected feedback. Labels such as “Reviews collected before our platform migration” or “Historical reviews from previous storefront” provide useful context. The wording should be visible enough to inform shoppers without overwhelming the product page.

Search engines also need accurate signals. If the new site uses review structured data, ensure that the markup matches the reviews visible to users. Do not add ratings for products that have no displayed evidence, inflate counts through duplicate imports, or mark up company-wide feedback as though it belonged to one product. Validate structured data after launch and monitor search results for discrepancies.

Keep a migration log showing the old product ID, new product ID, imported review count, rating calculation, exclusions, and approval date. This creates an audit trail when a customer disputes a review, a merchandising team changes a product relationship, or a search platform reports invalid review markup.

Use feedback during the platform transition

Reviews are valuable beyond their role as storefront content. Analyse recurring comments to identify shipping problems, confusing product information, packaging defects, sizing issues, and customer-service gaps. This insight can guide catalogue updates and operational decisions after the NCR system is retired.

Preserve the original chronology when studying trends. A cluster of complaints from one period may correspond to a supplier change or fulfilment disruption that no longer exists. Combining those comments with recent feedback without dates can make current performance look worse or better than it is.

During migration, keep review imports independent from core checkout testing. A storefront can appear ready while product mappings, tax settings, fulfilment rules, and customer account transfers remain incomplete. Teams responsible for continuity can consult guidance on keeping stores operational while the new review system is tested in parallel.

Create a review-retention checklist

Assign responsibility to specific people for export security, privacy review, product mapping, content moderation, and final publication. A single owner should maintain the decision log and approve changes to the retention rules.

Before launch, test the customer-facing experience on desktop and mobile devices. Confirm that ratings, review counts, dates, pagination, images, replies, and accessibility labels work as expected. After launch, sample imported pages regularly instead of assuming a successful bulk import means every record is correct.

• Preserve a read-only archive before altering or deleting legacy feedback.
• Map every old product identifier to a confirmed product in the new catalogue.
• Remove duplicates, spam, private information, and reviews that no longer describe the item.
• Display original dates and label historical or migrated feedback clearly.
• Validate rating averages, review counts, structured data, and customer-facing permissions.

Old feedback can become a durable business asset when it is treated as customer evidence rather than disposable platform content. Complete the audit, document every decision, and publish only the reviews that remain accurate, authentic, and appropriate for the new storefront. This gives shoppers useful context while protecting the business from misleading claims and avoidable privacy problems.