ERP Pilot
Guide

ERP Migration: The Complete Guide for Mid-Market Companies

Last updated: November 2026

Not sure which ERP fits your company?

Take our free 10-minute quiz. Knockout scoring eliminates the wrong systems instantly.

Start Quiz
Illustration of an old stacked system connected by a narrow bridge to a modern modular cube, with small data blocks crossing over and a short column of empty checklist boxes below

An ERP migration moves your master data, open transactions and a defined slice of history from the system you run today into a new one, and changes the processes around it. For most mid-market buyers this is the real job: 78% of the 218 quiz runs on ERP Pilot that named their current system replace an existing ERP. The path, the tools and the risks depend first on which system you leave, so start there, not with a generic project plan.

This guide shows the vendor-documented route for the systems buyers most often leave (Dynamics NAV, Dynamics AX, SAP ECC, SAP Business One, spreadsheets and accounting packages), what you should move and what can stay behind, how long it takes, and a checklist by phase. Vendor and legal statements were checked on the vendors' own documentation and in the statute texts on 3 November 2026, and are linked where they appear.

💡 Key Takeaway

Decide what you migrate before you decide how. Master data, open items and opening balances move; most history stays readable in the old system or an archive. That one decision sets the scope, the cost and the cutover plan.

What is an ERP migration, and is yours one?

If you already run an ERP, yes. A migration replaces a working system that holds years of data and habits; a first implementation builds the data from spreadsheets or an accounting package. The two need different plans: a migration carries the risk of moving bad data and old customisations, a first implementation the risk of designing processes that never existed in a system.

Among buyers using the ERP Pilot comparison, migration is the normal case. Of 218 runs from 19 February to 2 November 2026 that answered the question about their current system, 169 replace an existing ERP, most often a system outside the big names, followed by Microsoft Dynamics, SAP ECC and SAP Business One.

What ERP Pilot quiz takers run today
Another ERP system78 (36%)No ERP yet, or spreadsheets49 (22%)Microsoft Dynamics (NAV, Business Central, AX, F&O)47 (22%)SAP ECC / R/323 (11%)SAP Business One21 (10%)
What ERP Pilot quiz takers run today
Runs
Another ERP system78 (36%)
No ERP yet, or spreadsheets49 (22%)
Microsoft Dynamics (NAV, Business Central, AX, F&O)47 (22%)
SAP ECC / R/323 (11%)
SAP Business One21 (10%)

Source: ERP Pilot quiz data, 19 February to 2 November 2026, English and German versions combined, n = 218 runs that answered the current-system question (test hosts and a test address excluded). Microsoft Dynamics combines three answer options, including one retired in March 2026 that mixed NAV, AX and GP.

Which migration path fits your current system?

The vendor of your current system and the target decide the route. Here is what the vendors document for the systems that come up most often.

Dynamics NAV to Business Central

Microsoft routes every NAV version through Business Central 14 on-premises. NAV 2015 to 2018 go to Business Central 14, then to version 25 or later on-premises, then online; older versions need one or two intermediate NAV upgrades first (Microsoft Learn). From Business Central 14 there are two paths: a full migration, which requires converting the old C/AL code to AL extensions, or a reimplementation that moves master data, open orders, opening balances, setup and a defined subset of posted history. Microsoft labels the reimplementation tool a preview that is "not meant for production use" (Microsoft Learn). The cloud migration tool does not move most system tables, users, permissions or record links (Microsoft Learn). Dates and options per NAV version are in our guide to upgrading from Dynamics NAV.

Dynamics AX 2012 to Dynamics 365 Finance & SCM

Microsoft supports the upgrade only from AX 2012 R2 and R3 on their latest cumulative update; AX 2012 RTM is not supported. The data upgrade brings the whole database forward, so the transactional history can come along, while code moves through Lifecycle Services. Installations that use virtual companies or data partitions cannot be upgraded, and attachments only carry over if they sit in the AX database before the upgrade (Microsoft Learn). If your AX runs several companies on virtual companies, plan a new implementation of Finance & SCM instead.

SAP ECC to SAP S/4HANA

SAP names three approaches. A system conversion is an "in-place conversion" in which "the full set of data remains"; a new implementation starts clean; a selective data transition moves chosen organisational units or data and is "an alternative to a System Conversion and New Implementation" (SAP Support). For S/4HANA Cloud Public Edition only one applies: "There is no system conversion or landscape transformation option" (SAP Learning), and a selective data transition into it is not supported either. A conversion to the 2025 release requires a Unicode system and a minimum start release (SAP Conversion Guide 2025, version of 7 October 2026). The maintenance dates that drive the timing are in our guide to SAP ECC end of life.

SAP Business One to another system

SAP documents no dedicated path from SAP Business One to S/4HANA. You extract the data and load it with the target's own tools, for S/4HANA the migration cockpit, which accepts direct transfer only from a compatible SAP ERP system, not from Business One (SAP Learning). In the other direction, SAP's Data Transfer Workbench imports new data into Business One and updates existing records (SAP help).

Another ERP, an accounting package or spreadsheets

Then the target's import tools do the work. The S/4HANA migration cockpit loads data through staging tables at no extra cost. Business Central has built-in migrations from NAV, Dynamics GP and SL from version 2015, plus Microsoft apps for QuickBooks (Microsoft Learn); its configuration packages import Excel data but are meant "only when setting up a company for the first time" (Microsoft Learn). NetSuite's Import Assistant handles "small to medium-sized data sets" with up to 25,000 records per file, and balances come in through a journal entry import (NetSuite help). Odoo imports Excel or CSV files on any object, with an external ID per record and a test step before the real run (Odoo documentation). Leaving an accounting package is covered in our guide to outgrowing QuickBooks.

What do you migrate, and what stays in the old system?

Move what the new system needs to run, and keep the rest readable. In practice that means:

  • Always: customers, suppliers, items and bills of materials, chart of accounts, open receivables and payables, open sales and purchase orders, stock levels, fixed assets with their values, and opening balances per account at the cutover date.
  • Often: one or two years of summarised history, for example monthly balances, so year-on-year reports work in the new system.
  • Rarely: full posted history. It is expensive to map, rarely used and the main source of migration errors. Upgrade paths that bring the whole database forward, such as AX 2012 to Finance & SCM or an S/4HANA system conversion, are the exception.

What stays behind must stay accessible for as long as the law requires. In Germany, books and financial statements are kept for 10 years, booking vouchers for 8 years since 1 January 2025 and other business records for 6 years (section 257 HGB, section 147 AO). The tax authority's guidance allows you to switch the old system off only if all data, including master data, transactions and their links, moved to the new system in the same quantity and quality and can be evaluated the same way; otherwise the old system must stay available (GoBD, Rz. 142 to 144). Other countries have their own periods, so check them per entity.

How does the data cleanup process work?

Clean the data in the old system, before the first extraction, and let the business own the result. If the cleanup happens in migration files or in the new system instead, every test migration starts from dirty data again, and whatever slips through gets corrected on live transactions after go-live. A workable sequence:

  1. Profile the data. Count the records per object and how many of them are inactive, incomplete or duplicated: customers and suppliers without a transaction in recent years, items without stock or movements, addresses and tax IDs in inconsistent formats. These counts set the cleanup effort, so collect them before you compare offers.
  2. Name an owner per data object. Finance for the chart of accounts, suppliers and open items, sales for customers and prices, operations for items and bills of materials. The owner decides what is deleted, merged or kept; the project team carries it out.
  3. Block what you will not move. Mark inactive customers, suppliers and items in the old system so the extraction leaves them out. They stay readable there for the retention period.
  4. Merge duplicates and complete mandatory fields. Decide which record survives, move its open items onto it, and fill the fields the new system requires, such as tax IDs, payment terms or units, before the extraction rather than during the load.
  5. Map and validate against the target. Translate the old codes into the new structures (chart of accounts, units, payment terms, tax codes) and use the target's checks before data goes live: the S/4HANA migration cockpit loads through staging tables (SAP Learning), and Odoo runs a test step before the real import (Odoo documentation).
  6. Reconcile every test migration. Same number of records, same open item totals, same balance per account. Each difference goes back to its owner and is fixed at the source, and the next test run starts from the corrected system.

The cleanup runs alongside the design phase and ends when the business owners sign off a test migration. Ask for it as its own line item in implementation offers: it is the part of the migration most often assumed to be included, as the breakdown of ERP implementation costs shows.

How long does an ERP migration take?

About as long as the implementation of the target system, plus the time for test migrations. In our implementation data, typical projects run Dynamics 365 Business Central 2 to 6 months, Oracle NetSuite 3 to 6 months, SAP S/4HANA Cloud Public Edition 4 to 12 months, Dynamics 365 Finance & SCM 6 to 12 months, SAP S/4HANA Cloud Private Edition 8 to 14 months. Plan at least two full test migrations before the real one; Microsoft's cloud migration, for example, can be rerun, which is exactly what test runs are for. The phase-by-phase breakdown is in our guide to the ERP implementation timeline, and what drives the budget is in ERP implementation costs.

Buyers who already run an ERP seem to know this. In the quiz, 17% of those replacing an ERP want to go live as fast as possible, against 47% of those buying their first one.

Quiz runs that want to go live as fast as possible
Buying a first ERP (n = 49)47%Replacing an existing ERP (n = 169)17%
Quiz runs that want to go live as fast as possible
Share choosing as fast as possible
Buying a first ERP (n = 49)47%
Replacing an existing ERP (n = 169)17%

Source: ERP Pilot quiz data, 19 February to 2 November 2026, n = 218 runs that answered both the current-system and the timeline question.

Big bang, phased or parallel run?

For most mid-market companies with one or a few entities, a big bang at a period end is the safest choice: one cutover, one set of opening balances, no interfaces between old and new. A phased approach, by entity or by country, fits groups with several companies, as long as each phase is a full cutover for that entity rather than a split of processes across two systems.

A full parallel run, entering every transaction in both systems, sounds safe and rarely is: it doubles the workload exactly when the team is learning the new system, and differences between the two are hard to explain. A limited parallel check works better: post one closing period in both, reconcile the balances, then switch. Whatever you choose, run the cutover at a month or year end, and freeze master data changes in the old system during the final load.

Rehearse the cutover, not only the data load

A test migration proves that the data fits. A cutover rehearsal proves that the weekend works: the freeze, the final load, the balance reconciliation, the sign-off and the go or no-go decision, with the people who will do it, in the order they will do it.

What changes when you run several entities?

The migration becomes a consolidation project. Of the quiz runs replacing an ERP that answered the question about legal entities, 51% run two or more. Then intercompany balances have to match at the cutover date in every entity, the chart of accounts is usually harmonised on the way, and the order of entities matters: migrate the one with the cleanest data first and use it as the template. Upgrade tools may not cover every multi-company setup; Microsoft, for example, excludes AX 2012 installations with virtual companies from the upgrade.

The ERP migration checklist

The steps below follow the order in which they decide the project. Each line is a yes or no question you should be able to answer before the next phase.

Before you sign

  • Is the migration path from your current system documented by the target vendor, or is it a manual extract and load?
  • Have you decided what history moves and where the rest stays readable, and for how long?
  • Does the offer list data migration and test migrations as separate line items?

Design

  • Does every data object (customers, items, open items, balances) have a named owner on your side?
  • Is there a mapping from old to new for the chart of accounts, units, payment terms and tax codes?
  • Do you know which customisations of the old system you will drop rather than rebuild?

Data

  • Have duplicates and inactive records been removed in the old system before extraction?
  • Do test migrations reconcile: same number of records, same open item totals, same balances per account?
  • Have the business owners, not only the project team, signed off a test migration?

Cutover

  • Is the cutover at a period end, with a master data freeze and a documented order of steps?
  • Is there a go or no-go decision with named people and a fallback plan?
  • Are opening balances reconciled with the closing balances of the old system before go-live?

After go-live

  • Is the old system read-only, and is it clear how long it must stay available or how its data is archived?
  • Has the first period end closed in the new system before anyone switches the old one off?

What makes ERP migrations fail?

Rarely the software. The recurring causes are decisions taken too late:

  • Migrating everything. Full history multiplies the mapping work and carries old errors into the new system.
  • No owner for the data. If the project team cleans data on the business's behalf, nobody signs off the result.
  • Underestimating customisations. On the NAV route, every C/AL customisation has to become an AL extension or be dropped; deciding that late stops the project.
  • Too few test migrations. One successful load proves little. Two or three full rehearsals with reconciliation find the problems while there is still time.
  • Switching the old system off too early. Retention rules decide when you may, not the project plan.

Choosing the target is the step before all of this. Which systems fit which company profile is in our independent overview of ERP software, and the migration path from your current system is one of the fit criteria worth weighing there.

💡 Key Takeaway

Start from the system you leave: its vendor's documented path, its data quality and its customisations decide the project. Move master data, open items and balances; keep the rest readable for as long as the law requires.

Find Your ERP Match in 10 Minutes

Our knockout scoring algorithm eliminates systems that can't meet your dealbreakers, and ranks the rest by fit.

Start Free Comparison

No registration required · Instant results

Frequently Asked Questions

How long does a typical ERP migration take for a mid-market company?

About as long as implementing the target system plus time for two or three test migrations. In ERP Pilot's implementation data, typical projects run Dynamics 365 Business Central 2 to 6 months, Oracle NetSuite 3 to 6 months, SAP S/4HANA Cloud Public Edition 4 to 12 months, Dynamics 365 Finance & SCM 6 to 12 months, SAP S/4HANA Cloud Private Edition 8 to 14 months. Several entities, full history or heavy customisation extend that.

What does ERP data migration cost?

It depends less on the software than on scope: the number of data objects, how much history you move, the quality of the source data and the number of test migrations. Ask for data migration and test migrations as separate line items in every offer, so you can compare them. What else drives the project budget is broken down in our guide to ERP implementation costs.

Should we do a big bang or phased ERP migration?

For a company with one or a few entities, a big bang at a period end is usually safest: one cutover, one set of opening balances, no interfaces between old and new. Groups with several companies often migrate entity by entity, as long as each entity switches completely. A full parallel run doubles the workload; a parallel check of one closing period is usually enough.

How do we handle German compliance (GoBD, DATEV) during migration?

Keep the retention periods in view: in Germany books and financial statements are kept for 10 years, booking vouchers for 8 years since 1 January 2025 and other business records for 6 years (section 257 HGB, section 147 AO). Under the GoBD (Rz. 142 to 144) the old system may only be switched off if all data moved over completely and stays machine-evaluable; otherwise it must remain available. If you hand data to a tax adviser through DATEV, test the export from the new system before the first period end.

Tobias Trost, Independent SAP S/4HANA Cloud Consultant, Founder of ERP Pilot

About the author

Tobias Trost

Independent SAP S/4HANA Cloud Consultant, Founder of ERP Pilot

Tobias Trost is an independent SAP S/4HANA Cloud consultant specializing in Sales and Distribution and Order-to-Cash, and the founder of ERP Pilot. He writes and reviews the comparisons on this site.

Last updated: November 2026

Ready to find the right ERP for your business?

Take the Free ERP Quiz