Legacy ERP Data Archive Checklist (Free)

0%

0 of 28 items complete

7 critical items still open - these are the highest-risk gaps.

Download checklist:

Retention and scope

List retention periods by record type with finance, tax and legal sign offCRITICALIdentify records with legal hold, litigation or audit requestsCRITICALClassify data: master, open, transactional history, documents and attachmentsDecide what migrates to the new ERP and what goes only to the archiveIdentify personal data and agree deletion or minimization rules with privacyRecord the size of each database, table group and attachment storeCheck contracts for customer or government record keeping obligations

Access and usability

List who needs historical access and for what questions: audit, warranty, returns, taxCRITICALChoose the access method: read-only database, reporting layer, data warehouse or archive productKeep key reports such as trial balance, aging and inventory valuation reproduciblePreserve document links, such as invoices, PO PDFs and attachmentsDefine the response time expected for an audit requestDecide if natural language or search access to history is neededSet role-based access and log who reads archived data

Technical preservation

Take full database backups and verify they restore on a clean serverCRITICALExport key tables to open formats such as CSV or Parquet with a data dictionaryCapture the schema, stored procedures and custom code for later referenceRecord software versions, operating system and licensing needed to restoreStore encryption keys and credentials securely, with a named ownerCRITICALKeep at least two copies on different media, one offsiteHash exported files and record checksums

Validation and decommission

Reconcile archive row counts and control totals to the sourceCRITICALHave finance verify balances from the archive match closing reportsCRITICALTest an audit request end to end using only the archiveSet a review date for the retention schedule and for deleting expired dataDocument the archive for new staff, including where it lives and who owns itCancel unneeded licences, hosting and support only after sign offRecord the decommission decision with approvals

Do not power off the legacy system until every critical item is complete and a restore from the archive has been tested.

Archive design review

Share your retention list and get an outside view on archive options. Optional.

Optional. The tool and every export work without this. No spam.

How to use this checklist

Go through the four groups with finance, IT and compliance together. Start with retention, since it sets the size of everything else. Tick items only when they are documented. Critical items must be complete before decommission because a missing key or untested restore can make the archive useless. Export the PDF as evidence for auditors and keep it with your archive documentation.

Choosing an archive approach

There are four common options: keep the old database read-only on a small server, export to flat files with a data dictionary, load history into a data warehouse, or use a dedicated archive product. The first is simplest but ties you to old software. The warehouse is more flexible for reporting. Pick based on how often history is queried and how long you must keep it. A rarely used archive for audit only may justify a cheaper approach.

Read-only database: low effort, aging software risk
Flat files: durable, hard to query without tools
Data warehouse: good reporting, needs modelling
Archive product: managed, adds licence cost

Validating the archive

An archive is only as good as its last tested restore. Reconcile row counts per table, control totals such as GL balances by period and AR and AP aging totals. Ask someone who did not build the archive to answer a real audit question from it. If they cannot, the access layer needs work. Record the checksums of exported files and store them separately so future auditors can confirm nothing changed.

Common mistakes

The usual failures are keeping everything out of fear, which makes the archive costly and hard to query, and deleting too much, which creates compliance risk. Teams also forget attachments, document links and encryption keys, or decommission the server before finance has closed the first year on the new system. Treat privacy rules as a requirement, since old personal data does not become safer by being forgotten about.

Frequently Asked Questions

How long should we keep legacy ERP data?

It depends on tax, accounting, contract and industry rules in your country, and on legal holds. Ask your auditors and counsel for periods by record type. This tool helps you list the questions but does not give legal advice.

Should we migrate all history to the new ERP?

Usually not. Most projects migrate balances, open items and a short period of transactions, then keep older history in an archive. Migrating everything adds cost, risk and slower go-live.

Can we just keep the old server running?

Yes for a limited time, but unsupported operating systems, databases and applications become a security and licensing risk. Plan a managed read-only copy with controlled access and a defined end date.

What formats are best for long-term archives?

Open, documented formats such as CSV, Parquet or standard database dumps, plus a data dictionary and checksums. PDFs suit documents like invoices. Avoid formats that depend on a single vendor tool.

If you need to query a retired ERP archive in plain language without keeping the old application alive, we can discuss an on-prem approach.

Talk to an Expert Explore More Free Tools

Related Tools

ERP Migration & Selection

More ERP Migration & Selection tools

See all

Legacy ERP Data Archive Checklist