Legacy ERP data archiving: keep it live, archive it read-only, export it or delete it?

Which legacy ERP archiving option fits after a migration?

After go-live, the history left in the old ERP has four possible homes: the old system kept running, a read-only archive, an export to a warehouse or open files, or deletion once retention duties end. Most mid-sized companies end up mixing them, with a different answer for each class of records, rather than forcing one option onto everything.

Deletion is not always the cheapest outcome. A well-documented export can cost less than another year of legacy licenses and keeps the history usable for auditors, analysts and, potentially, a licensing deal.

What should you settle before choosing?

• What did not migrate. Many projects move balances and open items and leave transaction detail behind; the explainer on how much historical data to bring into a new ERP covers that scoping call.
• The retention schedule. Tax, payroll, contract and industry rules decide how long each class of record must stay retrievable. Take the periods from the company's tax adviser and counsel, not from a vendor brochure.
• Personal data. Customer, employee and vendor master files hold personal information. California's privacy law (the CCPA), for example, requires a business to tell people how long it keeps each category of personal information and limits retention to what is reasonably necessary and proportionate to the disclosed purpose (California Civil Code § 1798.100 et seq.). Other states and countries have their own rules.
• The vendor's dates. License end, support end and the last date full exports are possible.
• One owner. Name the person who signs off on the archive and on deletion dates, normally the CFO or controller.

This is general information, not legal, tax or financial advice. Confirm with your own counsel, tax adviser or professional body before acting.

How do you archive a legacy ERP without losing value?

1. Close and reconcile the old books. Produce a final trial balance and tie it to the opening balances in the new system. File the reconciliation workpapers with the archive.
2. Map what stayed behind. List modules, entities and years: general ledger detail, AP and AR subledgers, purchase orders, inventory movements, fixed asset registers, payroll history and attached documents.
3. Classify each record set twice. Once by retention class (how long it must be kept) and once by value class (who might want it: auditors, analysts, an acquirer, a data licensee).
4. Choose an option per record set. For example, export AP invoices with their approval history to searchable tables, keep payroll in a read-only vendor archive and delete obsolete test companies.
5. Export at transaction level with relationships intact. Keep journal IDs, document numbers, approval logs and attachments linked to their transactions. PDF reports are not an archive.
6. Write a data dictionary. Table names, field meanings, code lists and the date range of each extract. Without it, the export becomes unreadable once the last person who knew the old system leaves.
7. Test retrieval. Ask someone outside the project to find a specific vendor invoice from several years back, with its approval trail. If they cannot, the archive is not finished.
8. Record the decision and the deletion dates. A one-page memo signed by the archive owner, filed with the retention schedule.

Why might the archive be worth more than its storage bill?

ERP history records how a business actually runs: purchase requests and approvals, three-way match exceptions, credit holds, variance explanations and vendor disputes, each with timestamps and outcomes. That is the multi-step, outcome-labelled record of real work that AI developers need to train and evaluate agents, and it is scarce on the public web. Researchers at Epoch AI project that, if current trends continue, language models will fully use the stock of public human-generated text sometime between 2026 and 2032, a forecast with wide uncertainty that raises the value of non-public data (Epoch AI).

That does not make every archive licensable. Licensing interest depends on the wider record set: ERP history connected to email, CRM, support and project records is far more useful than a ledger alone. It does mean the keep-or-delete decision deserves one more question: could this history be licensed, and do we want to find out before it is gone? The explainer on whether licensing company data is worth it for a mid-sized company helps the owner decide, and the Sage 100 and Sage 300 legacy accounting history note shows what one common legacy platform tends to hold.

Common mistakes in ERP decommissioning

Example (Illustrative)

A fictional distributor, Harbor Lane Supply, has 190 full-time employees and an on-premises ERP it adopted in 2011. In 2026 it moves to a cloud ERP, migrating balances, open items and two years of monthly summaries. Fourteen years of transaction detail stay behind.

The company's fractional CFO sets a 12-month read-only overlap that covers the first year-end close, then exports purchasing, AP, inventory and customer service history to the company's warehouse with a data dictionary and a retrieval test. Before any deletion is signed off, the CFO asks the owner whether that history, together with the company's email and support archives, might be licensable. The owner runs the company fit checker, reads about what exclusivity would cost the company and agrees to an introduction. Whether a license follows is decided later, on the company's own terms.

Where does a fractional CFO fit as a referral partner?

You sit in the meeting where the archive decision is made, so you are one of the few people who can raise the licensing question before records are deleted. You introduce, and the company handles qualification, the data inventory, pricing and delivery directly with SourceX; you never export or describe confidential records yourself. SourceX looks for US companies that had 50+ full-time employees at peak (contractors excluded), have operated and kept records for several years, hold the rights to what they would license and have a sponsor with authority to sign; see who qualifies.

Partners earn 25% of the eligible platform fees SourceX actually collects from the referred company's licensing deals, capped at $100,000 per referred company, paid only after the buyer pays and SourceX receives its fee. It is paid from SourceX's share, never from the company's proceeds. The fractional CFO partner page explains the role.

Next step

Add one line to your next decommissioning checklist: confirm a complete, documented export exists before anything is deleted. If the client's history could be licensable, register as a partner and introduce the owner, or have them apply at sourcex.si/apply.