How much history to migrate to a new ERP, and what to do with the rest

What should move into the new ERP?#

The new ERP should receive whatever the business needs to operate on day one: open transactions, active master data and opening balances. Everything else is a choice, and the default for closed detail should be the archive rather than the new system.

Distributors and 3PLs often add a band of closed history so sales reps can see what a customer bought recently and finance can run year-over-year comparisons. Keep that band as narrow as the reports that depend on it, and load it as summaries where detail is not used. A practical test: if no report, process or user will read a closed record in the first year after go-live, it belongs in the archive.

• 1Open sales orders, backorders and quotes still in negotiation.
• 2Open purchase orders, receipts not yet invoiced and vendor returns in progress.
• 3Open receivables and payables at the invoice level, so payments can be applied.
• 4On-hand inventory by warehouse and bin, with lot and serial numbers where tracked.
• 5Active customers, ship-to addresses, vendors, items, price lists and customer-specific contracts.
• 6Opening general ledger balances and, if reporting needs them, prior-period summaries.

Migrate, summarize or archive: a decision table#

A record-by-record decision table keeps the migration debate short. The project team agrees once, then applies the same rule to every module instead of arguing over each report request.

The table below reflects the open-versus-closed principle. Adjust the summary column to match the reports your finance and sales teams actually run, not the reports someone might want later.

Why full-history migration usually backfires#

Full-history migration forces every old record through the new system's rules, and old records rarely fit them. Item numbers were renumbered, units of measure changed, warehouses closed, customers merged and tax codes were redefined, so each conversion needs a mapping, an exception list and a test.

The cost shows up late. Loading years of posted transactions lengthens every trial conversion and every reconciliation, and a single mismatch between migrated history and opening balances can hold up cutover. Teams that start with full history often cut it back during testing, after the mapping work is already spent.

There is also a quality cost. Converted history looks native in the new ERP, so users trust it, even where old codes were forced into new fields that do not mean the same thing.

What a good ERP archive looks like#

A good ERP archive can be read and queried without the legacy software, and it keeps the links that make each record meaningful. A stack of PDF reports or a database backup that only the old version can restore does not meet that bar.

Most teams combine two forms: a full database backup for completeness, and structured exports of the main tables in an open format with a data dictionary. The second form is the one people will actually use for audits, disputes and analysis.

• 1Structured exports of headers and lines for orders, shipments, invoices, credits, POs and inventory transactions.
• 2Original document numbers and the keys that join them, including the invoice a credit memo reverses.
• 3Code tables for reason codes, order types, warehouses and units of measure, so values can be decoded.
• 4Free-text notes from order lines, customer service logs and returns, kept with their parent documents.
• 5An attachment index that maps scanned bills of lading, PODs and packing lists to document numbers.
• 6A data dictionary, a named owner, access controls and a written retention schedule.

Settle retention and access before the old system goes dark#

Retention and access questions must be settled before the legacy subscription ends or the server is retired, because they are hard to answer afterward. Finance and counsel should confirm tax and audit retention needs, any legal holds, and customer contracts that require records to be kept or returned.

Check the legacy vendor agreement too. Some vendors offer read-only access or a full data export at the end of a subscription, others do not, and hosted systems may delete data after termination. Windows can be short: one sample SaaS agreement that names Acumatica makes subscriber data available for 60 days after termination, and after that only for a servicing and handling fee, while a variant of the clause uses 30 days. Your signed agreement, often through a reseller, sets the real period.

Pull the complete export while you still have the access, open it on a machine that never had the legacy software installed, and check row counts against the source before anyone signs off. Record the export date, the tables included and who verified it.

The archive has a second use#

An ERP archive is also a record of how the business ran: which orders shipped late, which returns were approved and why, which customers disputed which charges. Years of linked orders, exceptions and resolution notes are the kind of operational history AI developers license for training and evaluation.

That use depends on the same choices that make an archive good for audits. Linked documents, decoded reason codes and preserved notes keep the history useful; flattened reports and dropped notes destroy it. A license would also need a rights review of customer and supplier contracts and removal of personal and confidential details, and the company keeps ownership because the data is licensed, not sold.

Illustrative: a distributor splits its history#

Illustrative: a fictional industrial distributor is leaving an on-premise ERP it has run since its founding and moving to Acumatica. The original plan was to load every invoice line ever posted, and the first trial conversion stalled on retired item numbers and merged customer accounts.

The team resets the scope. Open documents, active masters and on-hand inventory migrate in detail. The current and prior fiscal year load as sales history summaries for rep dashboards. Everything else goes to structured exports on company storage with a data dictionary, and credit memo reasons and return notes stay attached to the original invoices.

The cutover holds its date. After the first year-end close on the new system, leadership runs a metadata-only fit check on the archive to see whether the returns and credit history could support a license, without moving any files.

How SourceX looks at a migration archive#

SourceX starts with a fit check that asks only for metadata: which systems the archive came from, which record families it holds, roughly how many years each covers and whether notes and links survived. No exports are requested at that stage.

The SourceX Enterprise Data Value Framework then gives a common language for value drivers such as human-generated signal, data cleanliness, scale and rights. If the supplier proceeds, the SourceX five-step transaction carries the archive through Supply, Rights, Preparation, Approval and Delivery, and large archives stay in the supplier's own storage.