Legal considerations when decommissioning an ecommerce platform

When a platform like NCR Retail Online reaches end of life, Australian retailers often focus on the technical lift: replicating catalogues, syncing stock, rerouting orders through a replacement such as Magento or WooCommerce via NCR Counterpoint partners. The legal workload slips into the background until a complaint lands or an auditor asks for a record that no longer exists.

A platform switch is more than a software project. It involves the lawful movement of personal information, the controlled termination of commercial agreements, and the ongoing duty to keep tax records for years after the storefront goes quiet. Each obligation has a regulator attached.

For operators in Sydney, Melbourne, Brisbane and the regional centres, the compliance backdrop is layered. Federal statutes such as the Privacy Act 1988 sit alongside the Australian Consumer Law, while industry-specific rules govern anything from card data to GST records. Treating the migration as a legal project, not just a deployment, separates a clean exit from a costly one.

This piece walks through the legal landscape around an ecommerce platform retirement, with practical attention to how Australian retailers usually approach the work and where the common pitfalls tend to hide.

Privacy Act obligations when customer data moves

The Privacy Act 1988 and the thirteen Australian Privacy Principles sit at the centre of any data migration involving Australian customers. Personal information collected during a storefront's life does not become less personal because the system holding it is being switched off. The retailer remains the APP entity responsible throughout the transition.

APP 6 limits the use and disclosure of personal information to its collection purpose, while APP 8 requires cross-border disclosure to be reasonable. If historical customer data is exported to a new overseas-hosted platform, documenting the transfer decision and updating the privacy policy before the data moves keeps the retailer on solid ground.

A practical step is to map every category of personal information held in the legacy system: customer names, delivery addresses, order history, marketing consents and payment tokens. That inventory supports both the legal analysis and any future access request from a customer asking what happened to their details.

For retailers worried about losing track of records during the cutover, putting a backup routine in place pays off long after the new platform is live.

Tax records, GST evidence and ATO retention

The Australian Taxation Office expects trading businesses to keep records for at least five years from preparation or acquisition, and longer for some circumstances such as capital gains claims. Ecommerce sales records, supplier invoices, GST reconciliations and import declarations all fall inside that window, even when the platform is retired.

Under the GST system, a sale through the old platform remains a sale made, and the ATO does not care which database holds the receipt. Exporting transactional history into a read-only archive, or retaining the legacy system frozen, are both accepted approaches. A gap in which tax invoices cannot be produced is not.

If the store sells across state borders, evidence of origin and destination for each shipment supports correct application of GST. Confirming that the new platform's reporting aligns with the old calculation of taxable value avoids reconciliation gaps that are difficult to explain two years into a BAS cycle.

Wind-down clauses in vendor and partner contracts

Software licences, payment gateway agreements, hosting arrangements and integrator statements of work all contain termination clauses that quietly govern how an exit unfolds. Reviewing each one before announcing a cutover date prevents the awkward surprise of an auto-renewal triggered while migration is still underway.

Notice periods vary widely. Some agreements require ninety days written notice, others allow termination at the next billing anniversary, and a few demand certification that customer data has been destroyed. A contract calendar listing every counterparty, deadline and data deletion obligation keeps teams aligned.

For retailers transitioning through an NCR Counterpoint partner, the partner arrangement usually carries its own termination mechanics. Confirming in writing that the legacy licence will not accrue fees after the cutover, and that any prepaid credit is documented, removes a common source of post-migration disputes.

Notifiable data breaches during the handover

The Notifiable Data Breaches scheme, embedded in Part IIIC of the Privacy Act, applies to most retailers with annual turnover above AUD 3 million and several smaller organisations that handle particular categories of data. A migration window, with data flowing between systems and credentials held by multiple parties, is precisely when an eligible breach can occur.

If personal information is lost or accessed without authorisation during the cutover, and a reasonable person would conclude serious harm is likely, an assessment must be undertaken quickly. Notifications to the Office of the Australian Information Commissioner and affected individuals follow a documented process with statutory timeframes.

Reducing that exposure means restricting production export access, using encrypted transfers, and revoking legacy API keys as soon as the new platform is live. Retailers in regional centres, where in-house security expertise is thinner, often find external penetration testing during migration useful.

Consumer law and customer-facing communication

The Australian Consumer Law, enforced by the ACCC, sets the floor for how a retailer treats customers, including during a platform change. A customer with an outstanding order, unresolved refund or open warranty claim at the moment the old system is decommissioned retains those rights under the new system.

Customer-facing communication should explain where to find order history, how to make a return, and who to contact if something goes wrong. Email templates, FAQ updates and on-site banners carry the same message: the business is still operating, and consumer guarantees continue to apply regardless of the platform.

Gift cards, store credit and loyalty balances deserve particular care. A balance that disappears during migration is a balance the retailer will be asked to honour. Carrying them into the new platform with an auditable trail protects both customer and business from a complaint that otherwise escalates quickly.

Payment data, PCI DSS and the handover window

Card data, even when tokenised, lives inside an ecosystem governed by the Payment Card Industry Data Security Standard. The platform that took the original authorisation may not be the one taking the next, but the merchant's PCI obligations do not pause during the handover.

Token migration requires coordination with the acquiring bank and the new gateway. Retiring old credentials at the right moment, and confirming stored cards have been tokenised into the new environment or securely purged, prevents duplicate charges and the lingering of unencrypted card numbers in forgotten databases.

A useful check is to keep the legacy payment integration dormant rather than deleted for a defined cooling-off period. If a chargeback or refund request arrives referencing an old order, looking up the original transaction keeps response times short and the merchant record clean.

Intellectual property, domains and customer databases

When an ecommerce platform is decommissioned, ownership questions surface around product imagery, brand assets, customer lists and custom code built on top of the legacy system. Trademark and copyright rules under Australian law determine who may use what, and any contractor should have signed assignment clauses that travel with the work product.

Domain names, often held through a different registrar than the platform, are easy to overlook. Confirming renewal is current, registrant details match the legal entity, and DNS changes during cutover do not create an unreachable window, protects both revenue and reputation.

Inventory accuracy during the switch also carries a legal flavour, particularly where consumer guarantees depend on what was advertised as available. Tools such as barcode stock counts provide a defensible record of stock on hand at the moment trading moved, which matters if a sale-of-goods dispute later arises.

Practical record-keeping habits for the cutover

• Lock a single calendar date on which the legacy system becomes read-only, and document it in writing to all internal stakeholders.
• Export full customer, order and product data into a versioned archive with checksums, stored in a jurisdiction that meets APP 8 obligations.
• File every vendor termination notice, signed acknowledgement and data deletion certificate in a single transition folder that survives staff changes.
• Run a sample reconciliation between the legacy platform and the new one for the same trading week, and keep the report.
• Review the privacy policy, terms of service and refund policy before the new platform goes live, and keep archived copies of the previous versions.
• Notify the payment gateway and acquiring bank in advance, and retain the confirmation in the transition folder.
• Schedule a quarterly reminder to confirm that archived records remain readable, encrypted and recoverable for the full retention period.

The cleanest platform decommissionings are those where legal and operational teams plan the exit as deliberately as the launch. Treating the paperwork as part of the build, rather than a separate stream finished afterwards, is the habit that keeps Australian retailers compliant long after the old platform is powered down.