Data Formats NCR Exports Support for Migration

Migrating from NCR Retail Online requires more than copying product pages into a new ecommerce platform. Store data, customer records, inventory quantities, orders, pricing rules, images, and configuration details must be extracted, cleaned, mapped, and loaded into the replacement system.

Because NCR Retail Online has been discontinued, merchants commonly move to platforms such as Magento or WooCommerce with assistance from NCR Counterpoint partners. The exact export options can depend on the account setup, connected retail systems, and partner tools used during the transition.

In practical terms, migration data is usually handled through structured formats such as CSV, XML, JSON, database extracts, and image files. The important issue is not simply whether a format exists, but whether it preserves the relationships between products, variants, stock locations, customers, and transactions.

Why Export Format Matters

A file format determines how easily information can be validated and imported. CSV is widely supported and works well for flat records such as product catalogs, customer lists, price books, and inventory snapshots. Its simplicity makes it convenient, although complex relationships may require several linked files.

XML and JSON can represent nested information more effectively. A product with multiple variants, attributes, categories, images, and channel-specific prices may be easier to describe in one structured document than in a collection of spreadsheets. These formats are particularly useful when a migration partner is connecting systems through an application programming interface.

The format also affects data quality. A spreadsheet may display a stock quantity correctly while losing leading zeros in a SKU, changing date values, or converting a barcode into scientific notation. Structured exports can reduce some of these errors, but they still require field mapping and validation before import.

Common Formats Used in Retail Migration

CSV is generally the most practical format for a first-pass ecommerce migration. Separate files may contain products, categories, customers, orders, inventory, and pricing. Columns should use stable identifiers, such as SKU or customer ID, so that records can be matched during repeated imports.

XML is useful when the export includes hierarchical data. Product options, tax rules, shipping details, and order line items can be represented with parent-child relationships. XML may be supplied by a connector, a custom report, or a partner-developed export rather than by a simple administration download.

JSON is common in modern integrations and web services. It can carry catalog, order, and customer objects in a format that developers can process programmatically. If a Counterpoint partner provides an API-based extraction, JSON may be the format used between the source system and the migration script, even if the final import is delivered as CSV.

Database exports are another possibility for larger or more customized environments. A partner may provide SQL extracts, relational database backups, or transformed files generated from retail management records. These methods can capture more detail than a standard catalog export, but they require careful interpretation of table relationships and business rules.

Matching Formats to Business Records

Product data usually includes SKU, title, description, brand, category, cost, retail price, tax status, weight, dimensions, and stock status. Variant products need additional links between the parent item and child SKUs. Images are often exported separately as JPG, PNG, or WebP files, with filenames or URLs stored in the product feed.

Inventory data may be delivered as CSV, XML, JSON, or a database extract. It should identify the item, location, available quantity, reserved quantity, and, where applicable, quantity on hand. A migration team must clarify whether the number represents sellable inventory or physical stock before it is imported into the new store.

Customers and orders require additional privacy controls. Customer exports may contain names, addresses, email accounts, phone numbers, and account identifiers. Order exports can include payment references, refunds, tax, shipping, discounts, and fulfillment statuses. Full payment card data should not be transferred as ordinary migration content; payment tokens and gateway settings normally need a separate, secure process.

What May Need Conversion

A direct file import is rarely enough when the destination is Magento, WooCommerce, or another commerce platform. Each system uses its own field names, category structures, product types, tax logic, and status values. A migration script may convert an NCR export into the destination platform’s required CSV schema or API payload.

For example, a source value such as “Active” may need to become “Enabled,” “Published,” or a numeric status code. A single category path may need to be split into a hierarchy. Product options may have to be transformed into configurable products, variable products, or separate SKUs.

Retailers with specialist catalogs should examine the data model early. Automotive merchants can review automotive retail workflows when identifying fitment details, part numbers, vehicle attributes, and location-based stock. Those fields may require custom mapping because standard ecommerce imports do not always support them.

Exporting Safely After Discontinuation

The first step is to establish what access remains available. Depending on the merchant’s configuration, data may be accessible through administrative exports, connected NCR Counterpoint records, scheduled reports, partner tools, or a custom extraction. The NCR Retail Online resource should be treated as background information about the discontinued product and transition context, while the active export procedure should be confirmed with the responsible partner.

Create a complete backup before transforming anything. Keep the original files unchanged, record the export date, and preserve the folder structure for images and documents. Use a working copy for cleansing, deduplication, formatting, and field conversion.

Sensitive data deserves additional safeguards. Restrict access to customer files, transfer them through encrypted channels, remove unnecessary fields, and set retention rules for temporary exports. Maintain an audit record showing which files were created, who handled them, and when they were imported.

Validate Before the Final Import

A successful upload does not prove that a migration is accurate. Run reconciliation checks between the source and destination: compare product counts, SKU counts, inventory totals, customer totals, order totals, tax values, and image associations. Investigate differences instead of assuming that missing records are harmless.

Test a small sample first. Select simple products, products with variants, discounted items, out-of-stock items, customers with multiple addresses, and orders with refunds or shipping charges. Review how each record appears on the new storefront and in the back office.

Use a staged migration when possible. Import the catalog, verify it, then process customers, orders, inventory, and redirects in controlled batches. Keep the original identifiers in the destination system so that future updates can be traced back to the source.

Practical Controls for a Cleaner Transfer

• Request a written inventory of every available NCR export, report, API feed, and connected data source.
• Keep original CSV, XML, JSON, SQL, and media files separate from cleaned migration files.
• Build a field-mapping document covering identifiers, dates, prices, tax codes, statuses, and relationships.
• Test representative records in a staging environment before importing the full dataset.
• Reconcile counts and monetary totals, then retain an auditable migration log.

A migration partner should confirm the available formats for the specific NCR Retail Online account rather than relying on assumptions about a standard export package. Ask for sample files, field definitions, character encoding, delimiter settings, date conventions, and rules for incremental exports. These details determine whether a file can be imported directly or needs transformation.

Begin by securing the source data, documenting the required business records, and selecting a destination-compatible mapping process. With controlled exports, careful conversion, and repeatable validation, retailers can move their ecommerce catalog and operational history without losing the relationships that keep daily selling accurate.