# Legacy ERP Data Archive Checklist

> Source: https://netray.co/tools/legacy-erp-data-archive-checklist
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Twenty-eight checks to decide what history to keep, where to keep it and how to decommission a legacy ERP safely.

## Category

erp-migration

## Audience

- Controller
- IT manager
- Compliance officer
- ERP project manager

## Tool

**Kind:** checklist

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

**Groups:**

#### Retention and scope

**Items:**

**Text:** List retention periods by record type with finance, tax and legal sign off

**Critical:** true

**Text:** Identify records with legal hold, litigation or audit requests

**Critical:** true

Classify data: master, open, transactional history, documents and attachments

Decide what migrates to the new ERP and what goes only to the archive

Identify personal data and agree deletion or minimization rules with privacy

Record the size of each database, table group and attachment store

Check contracts for customer or government record keeping obligations

#### Access and usability

**Items:**

**Text:** List who needs historical access and for what questions: audit, warranty, returns, tax

**Critical:** true

Choose the access method: read-only database, reporting layer, data warehouse or archive product

Keep key reports such as trial balance, aging and inventory valuation reproducible

Preserve document links, such as invoices, PO PDFs and attachments

Define the response time expected for an audit request

Decide if natural language or search access to history is needed

Set role-based access and log who reads archived data

#### Technical preservation

**Items:**

**Text:** Take full database backups and verify they restore on a clean server

**Critical:** true

Export key tables to open formats such as CSV or Parquet with a data dictionary

Capture the schema, stored procedures and custom code for later reference

Record software versions, operating system and licensing needed to restore

**Text:** Store encryption keys and credentials securely, with a named owner

**Critical:** true

Keep at least two copies on different media, one offsite

Hash exported files and record checksums

#### Validation and decommission

**Items:**

**Text:** Reconcile archive row counts and control totals to the source

**Critical:** true

**Text:** Have finance verify balances from the archive match closing reports

**Critical:** true

Test an audit request end to end using only the archive

Set a review date for the retention schedule and for deleting expired data

Document the archive for new staff, including where it lives and who owns it

Cancel unneeded licences, hosting and support only after sign off

Record the decommission decision with approvals

## Content

**Intro:** When a legacy ERP is retired, the hard question is rarely the new system, it is what happens to ten years of history. This checklist helps you decide, preserve and prove it before you switch the old system off.

**Sections:**

#### How to use this checklist

**Body:** 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

**Body:** 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.

**Bullets:**

- 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

**Body:** 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

**Body:** 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.

**Cta:** 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.

**Faq:**

#### How long should we keep legacy ERP data?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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.

## Search terms

legacy erp data archive checklist, erp decommissioning checklist, erp data retention after migration, archive old erp data, read only erp archive, retire legacy erp, erp archival strategy, gp data archive

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json