Publicité
ERP IMPLEMENTATION
🇫🇷 Lire en français →

Historical Data Migration in ERP: How Many Years Should You Migrate, and Which Ones?

Balances, open items or full history: a decision framework to set ERP data migration scope by domain, without migrating more than you need.

Historical Data Migration in ERP: How Many Years Should You Migrate, and Which Ones?

“Let’s just migrate everything, to be safe.” In ERP migration scoping, that sentence stretches schedules and inflates budgets. Every year of history you carry over has to be extracted, transformed, loaded, reconciled and corrected. And every extra year brings its own legacy anomalies: obsolete codes, duplicate suppliers, retired charts of accounts.

The right question is not “how many years should we migrate?” but “what do users need in the new ERP to do their jobs on go-live day, and where should we keep everything else?”. This article offers a decision framework to answer it, domain by domain, along with a decision template to put in front of your steering committee.

The “migrate everything” fallacy: cost, risk and value of each year of history

Migrating the full history feels reassuring. In practice, three effects add up.

  • Cost grows with every year migrated. It is not limited to loading: it includes structure gap analysis, transformation rules, migration rehearsals, reconciliations and reject handling.
  • Risk grows with age. Old data reflects old business rules. Loading it into a model designed for your target processes produces edge cases nobody can explain.
  • Value decays quickly. Beyond the period needed for day-to-day operations, history mostly answers one-off requests: a dispute, an audit, a trend analysis. Those needs are well served outside the ERP.

The starting rule is simple: migrate what operations need, archive the rest. And quality beats volume: a smaller, clean migration is better than a massive one nobody dares to use. Our ERP data quality playbook (in French) details the controls to put in place before any load.

What users actually ask for

In workshops, requests for history almost always come from three profiles. The accountant wants to justify a balance: they need the trial balance and supporting documents, not necessarily the journal entries inside the ERP. The sales rep wants to see “what this customer bought last year”: history aggregated by customer is enough in the vast majority of cases. The buyer wants to compare prices: a few years of history by supplier and item family, rarely every order line.

Before deciding, ask each department to name three concrete situations in which they consulted data older than two fiscal years over the past twelve months. If the list is empty or very short, detailed history has no place in the migration scope. If it is frequent, dig deeper: the need is often better met by a BI report than by a transactional migration.

Four migration levels

Rather than thinking in number of years, think in levels of granularity. Each level answers a different need.

LevelContentNeed coveredRelative effort
1. Opening balancesGeneral ledger trial balance, customer and supplier balances, valued inventory, net book value of fixed assetsStart accounting and operations on a sound footingLow
2. Open and in-flight itemsUnpaid invoices, open orders, open production orders, active contracts, leave and accrual balancesKeep operations running without disruptionMedium
3. Aggregated historyMonthly totals by account, customer and item family, over the useful periodPrior-year comparisons, budgets, trend analysisMedium
4. Detailed historyJournal entries, invoice lines, stock movements, one by oneTransactional lookups in the new ERPHigh

Levels 1 and 2 are almost always required: without them the new ERP cannot run. Level 3 is a good compromise for comparisons. Level 4 must be justified by a specific use, not by a precautionary reflex.

Decision matrix by domain

The migration level is decided domain by domain. Here is a starting point for discussion, to adapt to your context.

DomainRecommended defaultDetailed history is justified if…
General ledgerOpening balances and trial balance by account, plus the current fiscal year if cutover happens mid-yearYou need to replay matching or cost-center analyses across several fiscal years
Customers and suppliersActive records, balances and open invoices; inactive records left outLong contractual relationship with price history to rely on
InventoryQuantities and valuation at cutover date, lots and serial numbers in stockRegulatory lot traceability (food, pharma)
Fixed assetsFull register with original cost, accumulated depreciation and remaining scheduleAlways migrated in full as long as the assets are on the books
ProductionActive BOMs and routings, open ordersYield history useful for planning
HR and payrollActive employee files, balances, current-year cumulative figuresRarely: payroll history belongs in an archive with strict access control
DocumentsLinks to a document management system or archive, no duplication in the ERPDocuments attached to cases that are still open

Two points call for care. Fixed assets escape the “years” logic: an asset still on the books must be migrated with its entire history. And HR history contains personal data: the more you migrate, the wider you make the GDPR scope of the new system.

One last point on levels: they are not mutually exclusive. A single domain can combine level 1 for the oldest periods, level 3 for the latest years useful for comparisons, and level 4 only for the cutover year. This “staircase” approach is the most common in well-scoped projects: the further back you go, the less detail you carry over.

An obligation to retain is not an obligation to migrate. The law requires that you be able to produce certain data for set periods (accounting entries, supporting documents, audit files such as the French FEC or the German GoBD export on request). It does not require them to live in the active ERP.

What you must guarantee:

  • availability: data stays accessible and exportable in a usable format;
  • integrity: it cannot be modified after archiving;
  • the ability to regenerate statutory audit files for the fiscal years concerned, including those no longer in the new ERP;
  • erasure at expiry, notably for personal data.

Exact retention periods vary by document type and country. Have your legal team or chartered accountant validate them before freezing the scope. Our guide on ERP data archiving and retention covers each country and document type in detail: do not copy figures into your scoping document without that validation.

The special case of a mid-year cutover

Switching mid-year complicates the trade-off: the new ERP’s income statements cover only part of the year. There are two approaches. The first migrates cumulative balances at the cutover date, with a monthly trial balance for the preceding months, so that the year’s financial statements remain readable. The second migrates the current year’s entries in detail, at the price of heavier reconciliation work. Many teams avoid the problem by aiming for cutover at the start of a fiscal year or accounting period, when the business calendar allows.

Alternatives to migration: where to put what you don’t migrate

Three options, which can be combined.

  1. Read-only archive. Data is extracted to dedicated storage that supports search and export. This is the most common option for detailed history of accounts, invoices and stock movements.
  2. Data lake or BI warehouse. If the need is analytical (multi-year trends, historical margins), load aggregated or detailed history into the reporting tool, not the transactional ERP.
  3. Legacy ERP kept for limited consultation. Held in read-only mode for a fixed period, it avoids a complex extraction, but it costs in licenses, infrastructure and security risk. Set an end date at scoping: see our 8-step legacy ERP decommissioning plan.

Questions to ask the vendor or integrator

Migration scope is also a contractual matter. Ask the integrator how many full rehearsals are included in the fixed price, what load times they have observed on a comparable volume, and how additional migration runs are billed. Ask the vendor whether the loading tool preserves original identifiers, so that a document in the old system can be found from the new one. Keeping those source references is what makes the archive usable in practice: without it, finding an old entry turns into a treasure hunt.

Impact on the project: volumes, rehearsals, reconciliation, cleansing

Migration scope drives the schedule directly.

  • Volumes: more data means longer load times, and therefore fewer rehearsals within the project window.
  • Migration rehearsals: each full rehearsal replays extraction, loading and checks. A tighter scope allows more of them, and each rehearsal reduces the risk of the cutover weekend.
  • Reconciliation: every level migrated needs a matching reconciliation check (trial balance, valued inventory, third-party balances). Detailed history multiplies the points to reconcile.
  • Cleansing: you pay for data remediation on what you load. Excluding inactive parties and obsolete items before extraction is the best return on investment in the whole workstream. The ERP data migration methodology details this step.

Three scoping examples

Industrial mid-market company. Cutover at the start of the fiscal year. Migration of balances, open production orders, active BOMs and routings, and valued inventory with lots. Detailed accounting history goes to a read-only archive, and aggregated production history feeds the BI tool. Result: a tighter scope and more migration rehearsals.

Services group. Little inventory, but contracts, recurring billing and projects in progress. Active contracts, project work-in-progress and open invoices are migrated, plus aggregated profitability history by customer for comparisons. HR files of former employees stay in the HRIS archive, outside the new ERP.

Distribution. High volume of small transactions. Migration of balances, open orders, inventory and sales history aggregated by item and by month to feed forecasts. Receipt-level and invoice-line detail is not migrated: it remains available in the archive. The gain is in load duration.

The three scenarios share one thing: scope was decided early and by domain, with the business, not by default at the end of the project. That discipline, more than the number of years retained, is what secures the cutover.

Common mistakes to avoid

  • Deciding scope after writing the migration programs. Scope must come before load design, otherwise you build for data that will end up excluded.
  • Confusing an archive with a backup. A database backup is not a searchable archive: without the original application, nobody can read it. The archive must be usable without the old ERP.
  • Forgetting access rights. An archive containing payroll or personal data requires access control as strict as the ERP itself.
  • Not documenting what was left behind. Users need to know where to look, otherwise they will conclude the data has vanished.

Action plan and decision to validate at the steering committee

  1. List the real uses of history with each business department (who looks up what, and how often).
  2. Classify each domain across the four migration levels.
  3. Have retention constraints validated by legal counsel and your chartered accountant.
  4. Choose how non-migrated history will be consulted (archive, BI, time-boxed legacy ERP).
  5. Build the scope into rehearsal and reconciliation plans.

Decision template to present at the steering committee:

LineDecision to record
1. Migration level by domainLevels 1 to 4 selected, with the usage justification
2. Aggregated history periodNumber of fiscal years and domains concerned
3. Legal validationDate and name of the validator (legal, chartered accountant)
4. Solution for non-migrated historyArchive, BI or legacy ERP, with end date
5. Owner and budgetDecision owner, associated effort and cost

Once this template is signed off, any scope addition goes through an explicit decision, not an ad hoc request along the way.

To secure what comes next, download our ERP evaluation scorecard to frame your migration criteria, and review our data quality guide (in French) before the first load.