Exporting NCR Retail Online product data for a smooth transition

When an ecommerce platform is discontinued, the product catalog becomes one of the most valuable assets to preserve. Product names, descriptions, prices, stock records, images, variants, categories, and search information all need to move cleanly into a replacement system. A rushed export can leave gaps that affect merchandising, order processing, and customer trust.

NCR Retail Online customers transitioning to platforms such as Magento or WooCommerce through NCR Counterpoint partners should treat the move as a data migration project rather than a simple download. The goal is to create a complete, organized copy of the catalog before changing storefront operations.

A careful process also creates a useful archive. Even if some information requires manual reconstruction, keeping the original files, export dates, field definitions, and validation notes makes it easier to resolve discrepancies after the new store goes live.

Start with a complete data inventory

Begin by listing every type of information currently used by the online store. Core product records usually include stock keeping units, titles, descriptions, manufacturer details, prices, tax settings, inventory quantities, weights, dimensions, and availability status. Do not overlook metadata such as page titles, URL keys, search terms, and related-product relationships.

Separate catalog data from operational data. A product export may contain merchandise details, while customer accounts, order history, shipping rules, payment settings, and discount codes may require different reports or migration procedures. Record where each dataset is stored and whether it can be exported directly from NCR Retail Online, NCR Counterpoint, or a connected system.

Use the live storefront as a second source of truth. Browse representative categories, including men’s accessories, and compare what shoppers see with what appears in administrative records. This can expose missing images, shortened descriptions, discontinued items, or category assignments that are not obvious in a back-office export.

Prepare the catalog before extraction

Clean the source data before importing it into a new platform. Remove duplicate SKUs, correct inconsistent capitalization, standardize brand names, and identify products with missing prices or inventory values. A destination platform may reject a row with an empty required field, so resolving these issues early prevents repeated import attempts.

Create a consistent convention for product identifiers. The SKU should remain stable wherever possible because it may connect products to inventory, point-of-sale records, purchase orders, and historical reports. Avoid changing a SKU simply to fit a new naming preference. If a conversion is necessary, preserve a cross-reference file showing the old and new values.

Review product status carefully. Mark items as active, hidden, discontinued, or seasonal instead of deleting them automatically. Historical products may still be referenced in old orders or customer service requests. Keeping an archived copy preserves business context even when those items will not be published in the replacement store.

Choose a portable export format

A comma-separated values file is usually the most practical foundation for structured catalog data. CSV files are easy to inspect, transform, and import into Magento, WooCommerce, spreadsheets, and data-cleaning tools. Use UTF-8 encoding so accented characters, symbols, and non-English product names survive the transfer.

XML or JSON may be useful when the source system provides nested information such as configurable products, multiple images, or complex attributes. These formats can preserve relationships that are difficult to represent in a flat file, but they often need technical mapping before import. Request documentation for the available export fields and file structure rather than assuming that a downloaded file contains every record.

Keep the original export untouched. Make a working copy for cleanup and transformation, then store the raw file in a restricted location with a clear filename, date, and system identifier. If several exports are required, document the filters used, such as active products only, all inventory locations, or a specific category range.

Map fields to the destination platform

Magento and WooCommerce do not necessarily use the same attribute names or product logic as NCR Retail Online. Build a field-mapping document before importing anything. For example, the source field “Item Number” may become “SKU,” while “Web Description” may need to populate a long-description field and a separate short-description field.

Pay special attention to product types. A simple product has one purchasable item, while a configurable or variable product may contain a parent record and several child SKUs. Size, color, material, and pack quantity should be represented as controlled attributes rather than buried in free-text descriptions.

Categories also need deliberate mapping. Create a translation list that connects each NCR Retail Online category to its destination equivalent. Decide how to handle products assigned to multiple categories, empty categories, renamed departments, and items that no longer fit the new navigation. This is also the right time to review category paths for search-engine and customer-navigation effects.

Preserve images, variants, and merchandising content

Product images are often stored separately from the main catalog export. Identify every image associated with each SKU, including primary photos, alternate views, swatches, diagrams, and downloadable documents. Use predictable filenames and maintain a media manifest that connects each asset to its product identifier.

Check image quality and usage rights before transferring files. Remove obsolete placeholders, duplicate images, and files that display incorrectly. If the export includes image URLs rather than local files, download and verify the assets before the old system becomes unavailable. The same review should cover home and dining merchandise, such as the products represented in everyday dishes.

Descriptions deserve a content review as well. Strip unsupported HTML, repair broken links, and replace references to the former storefront where necessary. Retain useful buying information, but separate specifications from promotional copy so the new theme can display both consistently on desktop and mobile devices.

Validate the migration before the storefront changes

After preparing the files, import a small sample into a staging environment. Select products with different configurations: simple items, products with variants, items with multiple images, discounted products, and records with unusual characters. Confirm that each sample appears correctly in the catalog, search results, category pages, cart, and checkout.

Compare counts between the source and destination. Count active products, variants, categories, images, and inventory records rather than relying on a single total. Investigate mismatches instead of assuming that excluded rows were unimportant. A missing child SKU can make an entire size or color option unavailable even when the parent product appears correctly.

Run business checks with staff who understand merchandising and fulfillment. Verify prices, tax treatment, stock quantities, shipping weights, backorder behavior, and visibility rules. Test redirects for important product URLs and make sure analytics, structured data, and search metadata are populated where required. Keep a defect log with the source value, destination value, correction, and person responsible.

Protect the handoff and plan the final cutover

Product files may seem harmless, but exports can contain supplier costs, internal notes, inventory data, or credentials embedded in image paths. Store them securely, limit access, and transfer them through approved encrypted channels. Do not send sensitive exports through an unprotected public link or leave them in a shared folder indefinitely.

Establish a cutover schedule with the NCR Counterpoint partner or migration team. Freeze catalog edits for a defined period, take a final delta export, and record changes made after the first full extraction. A delta file may include new products, changed prices, updated quantities, and discontinued items that need to be applied immediately before launch.

Keep the legacy data archive after the new site is live. Monitor orders, inventory synchronization, product searches, and customer service requests during the first weeks. If an issue appears, the archived export and mapping document provide a reliable reference for identifying whether the problem began in the source data, transformation process, or destination configuration.

Use these migration practices

• Export the full catalog first, then create filtered files for active, discontinued, and seasonal products.
• Preserve SKUs, image associations, variant relationships, and original source files.
• Build a field map for product attributes, categories, pricing, inventory, and metadata before import.
• Test representative products in a staging store and reconcile record counts against the source.
• Schedule a final delta export and secure archive before switching customers to the replacement platform.

A smooth transition starts with a verified dataset, clear ownership, and enough time for testing. Export the NCR Retail Online catalog in its original form, clean a working copy, map it carefully to Magento or WooCommerce, and coordinate the final synchronization with an NCR Counterpoint partner. That disciplined handoff protects product information while giving the new ecommerce store a dependable foundation.