Getting started
Is it worth keeping an old system running just for its data?
By SourceX Editorial · Updated
Short answer
Keeping a legacy system running just for its data is rarely worth it beyond a defined period, but retiring it before you hold a complete, tested export is the costlier mistake. Rule: keep native access only while a legal hold, audit, dispute or migration reconciliation needs it; otherwise export, document, review the history for value, then retire.
Key takeaways
- The license or maintenance fee is only one cost of a read-only system; hosting, patching, access reviews and the people who can still query it count too.
- Keep a legacy system only for a named reason with an end date, such as a legal hold, an audit or a migration reconciliation.
- An export is complete only when it includes history, attachments, audit logs and lookup tables, and has been test-restored.
- Review a retiring archive for reuse or licensing before deletion, within your retention schedule and privacy obligations.
What does a read-only legacy system really cost?#
A read-only legacy system costs more than its renewal invoice because it still needs a server or hosted instance, security attention and someone who knows how to get answers out of it. Finance usually sees the maintenance contract and misses the rest.
Unsupported software deserves particular weight. Once a vendor stops issuing security patches, every month the system stays on your network carries risk that does not appear in the budget until something goes wrong.
- Vendor maintenance or subscription fees, sometimes priced for full use even when nobody writes to the system.
- Hosting: an on-premises server, a virtual machine or a vendor-hosted tenant, plus its backups.
- Security: operating system and database patches, and the exposure of software the vendor no longer supports.
- Access management: user accounts, periodic access reviews and auditor questions about who can still log in.
- Expertise: the analyst or former administrator who understands the old report writer, schema and custom fields.
- Opportunity cost: IT time spent keeping an old platform alive instead of improving current systems.
Keep, archive, export or review: the four options compared#
The four options differ in what you keep, what you keep paying for and what can go wrong. Most retirements combine them in sequence rather than picking one.
A common sequence is to keep the system briefly while you export and test, move retention-critical records into an archive, hold a full export in storage you control, and run the value review before anything is deleted.
| Option | What you keep | Ongoing cost profile | Main risk | Best when |
|---|---|---|---|---|
| Keep running read-only | Full native access, screens and reports | Highest: fees, hosting, patching and expertise | Unpatched software and fading know-how | A hold, audit or reconciliation needs native views for a defined period |
| Archive to a retention platform | Searchable records and documents under retention rules | Moderate: archive license and storage | The archive omits fields or attachments the old system held | Records must stay retrievable for retention or eDiscovery |
| Export to company-controlled storage | Database extracts, files and schema documents | Low: storage and documentation | Data without context that nobody can interpret later | History is needed for analysis, reference or future reuse |
| Review for value before retiring | A decision on reuse or licensing, plus the export | One-time review effort | Reviewing too late, after the export was trimmed | Years of decisions and outcomes sit in the system |
When is keeping the old system justified?#
Keeping the old system is justified when someone needs native access for a specific, time-bound reason that an export cannot meet. Write the reason down with an owner and an end date, so each renewal is a decision rather than a default.
Typical reasons include a litigation hold that requires preserving data in its original form, a tax or financial audit covering periods in the old ERP, open warranty claims that depend on old service history, and the first year-end close after a migration, when finance may need to reconcile opening balances against the old ledger.
Tax retention is often the strongest of these, and it usually argues for a good export rather than a running system. IRS Rev. Proc. 98-25 treats machine-sensible records in a taxpayer's data processing system as records that must be retained while their contents may become material to tax administration, at a minimum until the limitation period for assessment expires for each tax year. Ask your tax advisor whether an export with the posting detail and documentation meets that need for your old ERP.
Reasons that rarely justify another renewal: someone might need a report one day, nobody is sure what the system holds, or the export looks hard. Those are arguments for doing the export properly, not for paying to postpone it.
What a complete export must include#
A complete export contains enough history and context that someone who never used the old system can read and trust it. Exporting only the current state of each record, such as open balances or final ticket status, is the most frequent and least reversible mistake.
For an old ERP, that means order lines, item masters, bills of materials, customer and vendor histories and the posting detail behind the general ledger. For a help desk, it means tickets, every comment, internal notes, macros and the links to issues in other systems.
- Full transaction and status history, not only current values.
- Attachments, scanned documents and email threads stored inside records.
- Audit logs showing who changed what and when.
- Lookup and master tables that turn codes and IDs into names, items, customers and users.
- Custom field definitions, report logic and a schema guide in plain language.
- A test restore or sample queries proving the export can answer real questions.
Does the history have value beyond retention?#
The history in a retiring system often has value beyond retention because it records years of decisions and outcomes: orders and the exceptions around them, service calls and callbacks, quotes won and lost. AI developers license that kind of operational record to train and test models on real work.
A value review asks what record families exist, how many years are intact, whether records link requests to outcomes, and what rights and privacy limits apply. It is far cheaper while the system and its experts are still available than after the export has been trimmed or the administrator has moved on.
Retention and privacy limits still apply. Your retention schedule and privacy laws may require deleting some personal information once its purpose ends, so a value review works within those rules, assessed with counsel, rather than becoming a reason to keep everything.
Illustrative: a distributor decides what to do with its old ERP#
Illustrative: a fictional industrial distributor moved to NetSuite but kept its previous on-premises ERP running on an aging server, under a maintenance contract that renews each year. The CFO asks whether to renew again.
The team lists every reason for native access and finds only one with a real end date: reconciling opening balances through the first year-end close and tax filing on the new system. Everything else is covered by a full export of orders, item masters, returns and the free-text exception notes that buyers and warehouse leads wrote on problem orders, plus lookup tables and a schema guide written by the last administrator before she moves to another role.
The CFO approves one final renewal with a written retirement date. Before the server is switched off, the order exception history goes through a metadata-only fit check, and the company keeps the export in its own storage while it considers licensing.
Questions to answer before the next renewal#
The questions to answer before the next renewal turn a vague worry into a dated decision. A CFO can ask IT, legal and the system's business owner to answer them in one short memo.
SourceX's role starts at the last question. Its fit check runs on metadata such as system names, years of history and record families, with no files shared, and if a license proceeds through the SourceX five-step transaction, large archives stay in your own storage or ship on encrypted drives.
| Question | Who answers | What a good answer looks like |
|---|---|---|
| What specific need requires native access? | Legal, finance and the business owner | A named hold, audit or reconciliation with an end date |
| Is a complete export done and tested? | IT | An export inventory plus successful test queries |
| What does the system cost in total? | Finance with IT | Fees, hosting, patching and staff time listed together |
| What must be retained, and for how long? | Legal and the records owner | A retention schedule mapped to record types |
| Has the history been reviewed for reuse or licensing? | Executive sponsor | A recorded decision, made before deletion |
Frequently asked questions
Is read-only mode enough to make an old system safe?
No. Read-only mode stops new transactions, but the application, operating system and database can still have security flaws, and accounts with access still need reviewing. If the vendor no longer patches the product, isolating the system from the network or moving its records to an archive is usually safer than leaving it running.
Can we keep the database and switch off the application?
Often, yes. A database backup or extract keeps the data without the application license, but you lose the screens and reports that interpreted it. Pair the extract with lookup tables and a schema guide, and confirm your license terms allow retaining and using the database after the application contract ends.
Who should own the decision to retire a legacy system?
The CFO usually owns the economics, IT owns the export and security, legal or the records owner sets retention, and the business owner confirms which history matters. Writing those roles down prevents the common outcome where everyone assumes someone else will decide and the system quietly renews again.
Does a vendor's end-of-support notice change the math?
Yes. End of support removes patches and help, which raises the risk of keeping the system and often its cost if extended support is offered. Treat the notice as a deadline for a tested export and a retention plan rather than as a reason to buy more time.
Can licensing the old records pay for the migration?
It sometimes contributes, but that depends on a buyer engaging with your specific records, which cannot be predicted in advance. Treat licensing as an option to evaluate during the retirement, not as a budget line. A metadata-only fit check tells you whether the archive deserves a closer look.
Sources
- Rev. Proc. 98-25 treats machine-sensible records in a taxpayer's automatic data processing system as records under IRC 6001 that must be retained so long as their contents may become material to tax administration, at a minimum until the period of limitation for assessment expires for each tax year. Source
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.