After you migrate to a new ERP, the old one usually keeps running — and billing — just so you can read history for audits. This guide covers how to decommission a legacy ERP (Oracle EBS, SAP, JD Edwards, PeopleSoft and more) the right way: what to archive, how long to retain it, and how to keep audit-ready access without paying for the legacy license.
You cannot simply turn a legacy ERP off — its data carries legal retention obligations, and the business will need to retrieve records for years. But keeping it running is expensive and risky. Decommissioning resolves both.
Organizations routinely keep a retired ERP on life support — license, hosting, security patching, and a shrinking pool of people who remember how it works — purely to answer the occasional audit, tax or legal request. That is pure cost for a system nobody transacts in, and a growing security liability as it falls out of support (the Oracle EBS and SAP ECC end-of-life timelines make this acute).
Decommissioning replaces the live system with a compliant archive: the data is extracted, validated, and stored in a queryable, access-controlled archive with retention policies, while the application and its infrastructure are retired. The business keeps audit-ready access through a web UI, API and reporting tools, and stops paying for the legacy platform. Done properly, the archive becomes the system of record for history.
The records that carry retention obligations and audit value.
Journals, trial balances, AP/AR detail and control-account history — the core of any financial audit.
VAT/GST, payroll tax, year-end filings and statutory reports kept to jurisdictional retention rules.
POs, invoices, receipts, shipments and attached documents that prove what happened.
Customers, suppliers, items, employees and the reference data needed to interpret transactions.
Who changed what and who approved it — often the first thing an auditor asks for.
Enough hierarchy and metadata that archived data can be reported on meaningfully years later.
A governed sequence from live system to retired application.
Catalogue the data and map each category to its legal retention period (IRS/tax, SOX, industry, jurisdiction). This defines what is archived and for how long.
Open and recent data usually migrates to the new ERP; the long tail of closed history is archived. Draw the line deliberately.
Pull the in-scope data and documents, decompress proprietary structures, and reconcile to the source so the archive is provably complete.
Store in an encrypted, access-controlled archive with per-category retention and immutable audit history.
Enable self-service search, API access and audit reports so users retrieve records without the legacy application.
Shut down the legacy ERP, cancel licenses and hosting, and document the decommissioning and retention plan for auditors.
Avoid the traps that keep legacy systems alive for years.
You can't decide what to archive until you know what you're legally required to keep, and for how long.
Auditors trust archives that can't be silently edited. Preserve audit trails and write-once history.
A GL line without its invoice image is half an answer in an audit. Archive attachments too.
Build the business case on retired license, hosting, support and patching cost — it usually pays for the project quickly.
Prove you can produce a payslip, invoice or journal from the archive before you turn the source off.
Decommission on your timeline, not under the pressure of an Oracle EBS or SAP ECC support cliff.
Both. Migrate the open balances, open transactions and active master data your new ERP needs to operate, plus a few years of history for reporting. Archive the older closed history for compliance instead of loading it all into the new system — that keeps the new ERP lean and lets you retire the legacy platform.
It varies by record and jurisdiction: payroll tax records typically 4+ years (IRS), SOX-driven financial retention commonly 7 years, and some industries and countries require longer. Map each data category to its specific obligation and apply retention per category in the archive.
Yes — by replacing the live system with a compliant archive that preserves the GL, sub-ledgers, tax records, documents and audit trails, with access via UI, API and reporting. Auditors get what they need without the application running.
License or support contracts, infrastructure/hosting, security patching, and the specialist staff needed to operate it — often hundreds of thousands per year for a system nobody transacts in. Decommissioning converts that recurring cost into a one-time archive.
Through a web UI for self-service search, an API for integrations, and reporting outputs (OAC, Power BI, Tableau). Records like invoices, payslips and journals are reproducible on demand.
Yes — encrypted at rest and in transit, role-based access with full logging, and write-once retention so historical records and audit trails cannot be silently altered.
Tell us which legacy ERP you're retiring and your retention requirements. We'll scope the archive — and the recurring cost you'll save by shutting the old system down.