Archiving NCR Retail Online Data Before Decommissioning

When an ecommerce platform is retired, the visible storefront is only one part of the system being left behind. Product records, customer profiles, orders, invoices, inventory movements, promotions, delivery details and integration logs may still be needed long after NCR Retail Online is switched off. A careful archive preserves this information in a usable, secure form rather than leaving it scattered across exports, email attachments and old computers.

The aim is to create a reliable historical record while separating data that must be migrated into a replacement platform. Magento and WooCommerce are common destinations through NCR Counterpoint partners, but neither should become a dumping ground for every legacy record. Current trading data belongs in the new system; older material may be better retained in a controlled archive with clear search and retrieval procedures.

Australian retailers also need to consider GST records, Australian Business Numbers, privacy obligations under the Privacy Act and the practical realities of serving customers from Perth to Brisbane. A sound decommissioning project balances operational continuity, tax requirements, customer trust and the cost of storing information that the business may rarely access.

Define what must be retained

Start with a data inventory that lists every NCR Retail Online object and the system connected to it. Include customer accounts, addresses, order history, refunds, gift cards, product catalogues, stock quantities, pricing rules, discount codes, abandoned carts, shipping records, supplier details, tax settings, user accounts and audit trails. Identify related data held in NCR Counterpoint, payment gateways, accounting software, email tools and courier integrations.

Classify each item as migrate, archive, export for reference or securely delete. Active products and open orders will generally need to move to the replacement environment, while old carts and expired promotions may have little operational value. Keep enough context for an historical order to make sense: customer identifier, line items, quantities, prices, GST treatment, payment status, fulfilment status and timestamps should remain connected rather than saved as isolated spreadsheets.

Retention should reflect business and regulatory needs, not guesswork. Australian businesses commonly need transaction records for tax and accounting purposes, including information supporting BAS preparation and GST reporting. Ask the accountant and privacy adviser to confirm the appropriate retention period for the business, particularly where employee records, wholesale accounts or sensitive customer information are involved.

Capture a complete and usable export

Use native exports and database-level reports where available, then compare the results. A CSV export may contain customer or order fields, while a PDF invoice preserves presentation and a system report supplies totals. These formats serve different purposes. Keep a structured, machine-readable copy for analysis and a human-readable copy for staff who may need to inspect a record years later.

Preserve the relationships between records. A product export without historical SKU mappings can make old orders difficult to interpret, while a customer export without consent status can create privacy and marketing problems. Record the original field names, date and time zone, currency, tax configuration, status definitions and export method in a data dictionary. For Australian operations, document whether prices included GST, how delivery charges were treated and whether amounts were stored in AUD.

Take a final snapshot after trading activity has stopped, rather than exporting once and assuming nothing changed. Reconcile order counts, sales totals, refunds, stock quantities and customer totals against accounting and payment systems. Differences are not automatically errors: a marketplace, a physical shop in Melbourne or a manual refund may explain a mismatch. The important point is to investigate and document every material difference before the old service disappears.

Protect personal and payment information

An archive can contain names, email addresses, phone numbers, delivery locations and purchase histories. Treat it as a sensitive business asset. Restrict access to people who need it, use role-based permissions, encrypt files during transfer and at rest, and keep administrative activity in an audit log. Avoid storing passwords, full payment card numbers or other authentication secrets in a historical archive.

Apply data minimisation when preparing old records. If a customer’s full address is not needed to substantiate a transaction, consider retaining only the necessary historical fields. Remove test accounts, duplicate exports and temporary files. Marketing permissions deserve special care: an archive may preserve evidence of an old consent status, but it should not automatically become a mailing list for the new platform.

Australian Privacy Principles require organisations to handle personal information responsibly, including protecting it from misuse, loss and unauthorised access. A breach response plan should cover archived data as well as live systems. Keep encryption keys separately from the archive, use strong administrator authentication and test that access can be revoked when a staff member or contractor leaves.

Prepare customer and business relationships

Customer history often has practical value beyond reporting. It can support warranty claims, returns, loyalty balances and service enquiries. Before migration, map customer identifiers between NCR Retail Online and the replacement store so that duplicate accounts are not created. If the new platform cannot reproduce every field, keep a cross-reference file that explains how an old customer ID relates to the new one.

Loyalty schemes require a separate review because points, tiers, expiry dates and consent records may be held in different systems. If WooCommerce is the destination, the guidance on loyalty programme migration can help frame the questions around balances, customer matching and communications. Do not migrate inactive or invalid balances without deciding how they will be handled and recorded.

Wholesale and trade customers have their own pricing, payment terms, tax details and account contacts. Preserve ABNs, credit limits, purchase orders and negotiated price lists where they are needed for ongoing service, while reviewing who is authorised to view them. Documentation about B2B account management is useful when translating these relationships into a modern ecommerce platform. A café supplier in Adelaide may need very different account controls from a direct-to-consumer shopper in Sydney.

Validate the archive and plan retrieval

Validation should test both completeness and usability. Open sample records from different years, product categories and order statuses. Check that attachments, invoices, refunds and delivery information are readable. Search for a known customer, SKU, order number and date range, then verify the results against the source system and accounting records.

Create checksums for exported files so later changes can be detected. Maintain at least one protected backup separate from the primary archive, with a documented restore test. Cloud storage can be effective for Australian businesses, but confirm where data is hosted, how access is logged and what the provider offers for retention, deletion and recovery. A local NAS in a Brisbane office is not a sufficient backup if it is exposed to the same fire, theft or ransomware event as the production equipment.

Write a short retrieval guide in plain language. It should state who approves access, where the archive is stored, which tool opens each file type, how records are searched and how requests are logged. Include the date of the final export, the responsible staff member, reconciliation results and the planned destruction date. If fulfilment workflows are moving to a new system, document the operational hand-off using resources on automated order fulfilment, while keeping the historical dispatch record separate from future automation settings.

Decommissioning should happen in stages: freeze changes, complete the final export, validate it, retain a read-only period, and then remove access to the old platform. Obtain written approval before deleting production data, integrations, API keys and administrator accounts. Keep evidence of what was deleted, when it was deleted and under whose authority. That record can be as important as the archive itself if a customer, auditor or former business partner later asks what happened.

A well-managed archive is a controlled reference library, not an unlabelled pile of files. It allows staff to answer questions about an old order, substantiate GST records and resolve a warranty issue without reviving a discontinued platform. It also prevents historical information from quietly flowing into a new system where it may be inaccurate, excessive or exposed to the wrong users.

The key principle is simple: preserve the records the business may need, preserve their meaning, protect the people represented in them and prove that the archive can be recovered. Before NCR Retail Online is decommissioned, a tested and documented archive turns a platform shutdown into an orderly handover rather than a scramble for missing data.