Systems and records
ERP migration: convert historical transactions or archive them?
By SourceX Editorial · Updated
Short answer
In an ERP migration, convert open items and balances into the new system and archive the full transaction history in a queryable form outside it, with a map of old IDs to new ones. Converting years of closed transactions rarely pays for itself, but deleting them costs traceability, audit support and future options.
Key takeaways
- Convert what the plant needs to run on day one: open orders, open receivables and payables, inventory on hand and balances.
- Archive closed history in a queryable form, such as a company-owned database, not only as printed reports.
- Keep crosswalks from old item, customer, vendor and account codes to new ones; they cannot be rebuilt later.
- Audit, tax, quality and customer contract obligations set how long the archive must stay readable.
- Archived quality, production and exception history often answers customer audits and traceability questions long after go-live.
What should a manufacturer convert into the new ERP?#
A manufacturer should convert the records it needs to run from the first day on the new ERP: open transactions, current balances and active master data. Everything else, the closed history, belongs in an archive that stays queryable but sits outside the new system.
Converting open items is unavoidable work; converting closed history is a choice. Each extra year means more code mapping, more validation and more old data quality problems carried into a clean system. The table shows a common split for discrete and process manufacturers.
| Data | Convert | Archive | Note |
|---|---|---|---|
| General ledger | Opening balances, plus prior-period summaries if needed for comparisons | Full journal detail | Agree comparison needs with finance before cutover |
| Receivables and payables | Open invoices and open credits | Paid and closed items | Tie open balances to the subledger at cutover |
| Sales and purchase orders | Open and partly shipped or received lines | Closed orders and their change history | Close stale orders before conversion |
| Work orders | Open work orders, or close them first | Completed work orders with labor and material actuals | Closing first is often simpler |
| Inventory | On-hand quantities by location, lot and serial | Transaction history and cost layers | Count and reconcile before cutover |
| Items, BOMs and routings | Active items and current revisions | Obsolete items and earlier revisions | Keep revision history in the archive |
| Quality records | Open NCRs and CAPAs | Closed NCRs, CAPAs and inspection results | Check customer quality agreement terms |
| Lot and serial genealogy | Genealogy for stock still on hand | Full genealogy for shipped product | Needed for recalls and customer audits |
Why not convert the whole history?#
Converting the whole history usually costs more than it returns, because old transactions must be forced into new structures. A new chart of accounts, new item numbering, new units of measure or a new costing method means every historical record has to be remapped, and remapped history no longer matches the documents sent to customers and suppliers.
Conversion also brings old problems forward. Duplicate customers, retired items and inconsistent codes that the migration was meant to clean up return with the history. Validation work grows with every year converted, and the go-live date carries that risk.
The opposite risk is real too. Teams that skip history and archive it poorly lose traceability: a customer audit, a warranty claim or a tax question arrives and nobody can query the old records. The fix is not more conversion but a better archive.
Archive options compared#
The best ERP archive option is the one that keeps history queryable by people who were not part of the migration. Printed reports and spreadsheet dumps preserve values but not relationships, so any question that crosses orders, shipments and quality records becomes a manual hunt.
Whichever option you choose, export from the legacy database at the most detailed level available, not from screen reports. Detailed tables keep the keys that connect a sales order to its shipments, invoices, returns and quality events.
| Option | Strengths | Weaknesses | Fits when |
|---|---|---|---|
| Keep the legacy ERP read-only | Familiar screens and reports, nothing to rebuild | Ongoing license, aging servers, fewer people who remember how to use it | A transition while the real archive is built |
| Export to a company database or warehouse | Queryable, inexpensive to keep, works with common reporting tools | Needs a data model, documentation and an owner | Most mid-market manufacturers |
| Specialist archive tool | Built-in viewers, retention rules and access controls | Another vendor and contract, possible lock-in | Several legacy systems or strict retention needs |
| Flat files and PDF reports | Simple and readable without software | Relationships lost, hard to search | A supplement, such as signed documents |
The ID map is the file you cannot rebuild later#
The ID map is the set of crosswalks from every old code to its new equivalent, and it is the one artifact of an ERP migration that becomes impossible to reconstruct once the project team disbands. Without it, archived history and live data describe the same customers and parts in two languages nobody can translate.
Store the crosswalks with the archive, in the same format, with a readme that names the migration date and who approved each map.
- Customers and ship-to addresses: old customer number to new customer ID.
- Vendors and remit-to records: old vendor code to new vendor ID.
- Items: old part number and revision to new item and revision.
- General ledger: old account and segment structure to the new chart of accounts.
- Units of measure, warehouses, locations, cost centers and departments.
- Documents converted at cutover: old document number to new document number.
How long must archived ERP history stay readable?#
Archived ERP history must stay readable for as long as your longest obligation runs: tax and audit retention, customer quality agreements, product liability exposure, warranty terms and any industry rules that apply to your products. Those periods vary by company, customer and jurisdiction, so set them with your tax advisor, auditors, quality lead and counsel rather than by habit.
Readable means more than retained. A backup that only the old ERP can open stops being readable once that ERP is gone. Test the archive by having someone outside the project answer a real question with it, such as which lots of a component went into a given customer's shipments.
Illustrative: a precision machining company moves to a cloud ERP#
Illustrative: a fictional precision machining and assembly company replaces the on-premise ERP it has run for many years with a cloud ERP. The project team's first plan converts every closed order to keep reporting consistent. The CFO and COO change course after the first mapping workshop shows how many retired part numbers and duplicate customers the history carries.
The final plan converts open orders, open work orders, inventory with lot numbers and opening balances, plus monthly account summaries for comparison reporting. The full history, including closed NCRs, CAPAs, inspection results and lot genealogy, goes to a company-owned database with a simple reporting layer. The ID map sits beside it, and the old server is retired only after finance and quality sign off.
Later, a customer's supplier audit asks for traceability on parts shipped before the migration, and the quality manager answers from the archive without reopening the old system. When the company considers licensing operational history, it starts from the same archive and excludes customer-owned drawings and any export-controlled work.
Where archived ERP history earns its keep#
Archived ERP history is useful beyond compliance when it records decisions and outcomes, not just postings. Quote-to-order sequences, schedule changes, supplier exceptions, nonconformance dispositions and corrective actions show how a plant actually solves problems, and that pattern is what AI developers building tools for operations study.
The finance view of an ERP, balances and postings, is rarely the interesting part. The operational view, such as how a late material receipt changed the schedule and what the planner did about it, is the part worth protecting. Keeping free-text fields, hold reasons and attached documents during the export preserves that view.
SourceX assesses legacy ERP history with the SourceX Enterprise Data Value Framework, a SourceX methodology whose drivers include uniqueness, domain expertise, human-generated signal, recency, data cleanliness, rights and AI utility, weighed against preparation cost and privacy burden. The first fit check uses a description of the archive, not the archive itself.
Where a package proceeds, the Rights and Preparation steps of the SourceX five-step transaction carve out customer-owned designs, export-controlled work and confidential pricing, and remove personal details before you approve anything. Records stay in your storage until you authorize delivery.
Frequently asked questions
Should we close open work orders instead of converting them?
Often, yes. Completing or closing work orders before cutover avoids converting partial labor and material postings, which are hard to validate. Work orders that must run across the cutover need a plan agreed with production and cost accounting, usually converting remaining quantities and keeping the earlier postings in the archive.
When can we switch off the old ERP server?
Only after the archive has passed reconciliation, people outside the project have answered real questions with it, and finance, quality and IT have signed off. Check first whether any legal hold, open audit or customer request needs the original system, and confirm your legacy license terms for read-only use.
Do auditors accept an archive instead of the original system?
Auditors generally need complete, reliable records and evidence of how they were produced, not a particular system. Discuss the archive approach with your auditors before cutover, keep the export log and reconciliation results, and preserve the original reports used at each year end.
Who should own the ERP archive after go-live?
Name one owner, usually in finance or IT, with a deputy. The owner controls access, keeps the readme and crosswalks current, handles retention decisions with counsel and answers requests from quality, tax and customers. An archive without an owner tends to become unreadable quietly.
Is it worth archiving free-text notes and attachments?
Yes, when they record why things happened: hold reasons, nonconformance dispositions, supplier correspondence and engineering change notes. They make the archive useful for root-cause work, disputes and any later licensing review. Check them for personal and confidential details and restrict access accordingly.
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.