How to preserve order history when moving to Magento or WooCommerce

When NCR Retail Online reaches the end of its service life, moving the storefront is only part of the job. Customer accounts, past purchases, payment records, fulfilment details and product relationships also need to travel safely to the replacement platform. A migration that preserves only current stock can leave staff without the information they need to support returning customers.

Magento and WooCommerce can both support a detailed ecommerce archive, but neither platform automatically understands every field from an NCR environment. The source data must be examined, mapped and tested before it is imported. This is especially important for retailers using NCR Counterpoint partners to transition to a new online store.

For Australian businesses, order history can affect refunds, warranties, loyalty activity and customer service across different time zones and delivery networks. A shopper in Perth may need help with a purchase made months earlier from a store in Sydney, while a retailer in Melbourne may need a reliable record for an Australian Consumer Law remedy.

The safest approach is to treat the move as a controlled data project rather than a simple website redesign. Keep the original records available, define what must be migrated, preserve relationships between entities and prove that the new platform produces accurate results before switching customers across.

Audit the old store before exporting

Begin with an inventory of every record connected to an order. This normally includes order numbers, dates, statuses, customer names, email addresses, billing and shipping details, line items, quantities, discounts, freight charges, tax, refunds, notes and payment references. Do not assume that a visible order screen contains all the fields stored in the underlying system.

Separate transactional data from catalogue data. An order may refer to a product that has since been renamed, discontinued or assigned a new SKU. Export the product identifier, product name and variation details as they appeared at the time of sale, while also recording the current catalogue identifier where one exists. This preserves historical accuracy without preventing the new store from using an updated product structure.

The audit should also identify attachments and related records. Gift messages, personalisation instructions and customer-selected options can be commercially important; an order for a personalised present may be impossible to fulfil or support later if those details disappear. Any legacy merchandising content, such as personalised gift options, should be reviewed for links between product choices and order metadata.

Build a migration map for Magento or WooCommerce

Create a field-by-field mapping document before loading anything. The document should state the source field, destination field, data type, transformation rule and treatment of missing values. For example, an NCR order status such as “awaiting fulfilment” may need to become “processing” in WooCommerce or a custom workflow state in Magento.

Preserve the original order number whenever the destination platform permits it. If the new system generates different internal IDs, store the NCR reference in a dedicated legacy-order field or order note. Staff should be able to search by the number printed on an old invoice, included in a customer email or quoted during a support call.

Customer matching requires particular care. Email address is useful, but it is not always unique or stable. Compare names, phone numbers, addresses and existing customer identifiers, then define a rule for duplicates. Combining two people into one account can expose private purchase details, while creating unnecessary duplicate accounts can fragment loyalty and communication history.

Do not copy passwords from the old platform unless the destination supports a secure, documented method. In many cases, customers should receive an account activation or password-reset message. Password hashes must never be exported as plain text, placed in spreadsheets or sent through ordinary email.

Preserve products, variations and tax details

Order history depends on a stable connection between products and line items. Map simple products, configurable products, bundles, size or colour variations and any custom options separately. A historical line should retain the description and price recorded at purchase, even if the product’s current price or description changes after migration.

Retailers selling homewares may have closely related catalogue items that require careful distinction. A tumbler, serving set and accessory can share a broad category while having different SKUs, weights and tax treatment. Existing category references such as drinkware products can help teams recognise how older merchandising groupings were presented, but the migration should rely on verified source exports rather than page names alone.

Australian tax information deserves a dedicated review. Confirm how GST-inclusive prices, GST-free items, discounts, shipping and refunds are represented. The Australian Taxation Office expects business records to be retained for the required period, and invoices should remain intelligible after the platform changes. Keep the original tax amounts where they were calculated, then check that new reports do not reinterpret historical orders using today’s rules.

Currency and dates should be normalised consistently. Store monetary values in Australian dollars where appropriate, retain the original transaction date and document whether timestamps were recorded in Australian Eastern, Central or Western time. This avoids confusing order sequences when staff compare records from Sydney, Adelaide and Perth.

Import in stages and protect the archive

Use a test environment for the first import. Load a representative sample containing completed orders, cancelled purchases, partial refunds, guest checkouts, account orders, discounts, shipping variations and products with custom options. Include records from different years so that older data is tested against recent transactions.

After import, compare source and destination totals. Check the number of orders, customers, products and refunds, then reconcile the total value of orders by month. Investigate every difference rather than accepting a small variance as harmless. A missing refund or duplicated order can distort accounting and create an avoidable customer dispute.

Keep an untouched export of the NCR data in a controlled, access-limited location. Maintain at least one backup that is separate from the migration workspace, record who accessed the files and document the export date. The archive should be readable without relying on the old storefront remaining online.

Security controls matter throughout the process. Australian businesses handling personal information should consider the Privacy Act and the Australian Privacy Principles when transferring names, addresses, phone numbers and purchase histories. Remove unnecessary payment card data, restrict administrator access and use encrypted storage and transfer methods.

Test customer service, fulfilment and reporting

A successful import must work in daily operations, not just in a technical report. Ask staff to locate an old order by customer name, email address and legacy order number. They should be able to view products, delivery details, notes, discounts, taxes, refunds and status changes without opening the retired platform for routine enquiries.

Test the customer-facing experience with a controlled group of accounts. Confirm that order history displays the correct dates, item descriptions, quantities and totals. Verify that guest orders remain available through the intended support process and that account activation messages do not accidentally reveal another customer’s information.

Fulfilment checks should cover shipping addresses, Australian postcodes, freight charges and delivery instructions. A retailer serving customers in regional Queensland or Western Australia may have different freight rules from a business focused on inner-city Sydney. Test these cases against the new checkout and warehouse workflow before accepting live orders.

Reports need equal attention. Compare sales by day, product, channel and tax category, and confirm that refunds reduce revenue correctly. If the business sells sets with separate components, ensure the imported line descriptions still make sense to staff; historical categories such as flatware collections should not be merged in a way that hides what customers actually bought.

Complete the cutover with a reconciliation record

Before launch, freeze changes in the old store or define a short final-capture window. Export all orders created since the test migration, import them into the new platform and run the same reconciliation checks. Keep the old storefront in read-only mode where possible so support staff can verify unusual cases without creating competing records.

Prepare a written migration record containing the export files, field mappings, transformation rules, validation results, exceptions and approval dates. Note which historical data was deliberately excluded, such as obsolete marketing preferences or sensitive payment details. This record gives the retailer a defensible explanation of how customer information was handled.

After launch, monitor order creation, account activation, refunds, stock updates and support searches closely. Preserve redirects or a clear internal lookup path for old order references, and retain the archive for the applicable business and tax recordkeeping period. The new Magento or WooCommerce store should become the operational source, while the preserved export remains the historical safety net.

The next concrete step is to create a read-only export of the NCR order database and a field inventory covering orders, customers, products, refunds, taxes and fulfilment details.