ERP Migration

ERP migration describes the process of moving from a current ERP system to a different ERP product or major version. Migration projects are typically the largest single IT initiatives in their organisations: 12-36 months in duration, 1-50+ million EUR in cost, with operational disruption and strategic transformation potential. For DACH mid-market, ERP migration drivers cluster around SAP ECC end-of-mainstream-maintenance (2027), cloud-ERP adoption pressure, and legacy-system technical debt that exceeds maintenance economics.

Common migration drivers

End-of-maintenance — vendor ends support for the current version (SAP ECC, Microsoft Dynamics AX, Oracle JDE legacy)
Cloud adoption — strategic shift from on-premises to cloud ERP
Functional gaps — current ERP cannot support new business requirements without extensive customisation
Technical debt — accumulated customisations make upgrades increasingly expensive
M&A integration — harmonising acquired operations onto a common platform
Industry transformation — shift from heritage business model (e.g., product sales) to new model (e.g., subscription, service)
Regulatory pressure — compliance requirements not addressable in legacy system (CSRD reporting, e-invoicing, NIS-2)

Migration strategies

Three main approaches. Greenfield (see greenfield implementation): fresh deployment, processes redesigned, master data plus open transactions migrated. Highest transformation value, highest cost and risk. Brownfield (see brownfield implementation): technical conversion preserving customisations and history. Lower transformation value, lower cost and risk. Bluefield / selective data transition: hybrid — new installation populated with selected legacy data, allowing process redesign while preserving critical history. Specialist tools (SNP CrystalBridge, Cbs Enterprise Transformer, SAP DataServices) support the bluefield pattern. Choice depends on transformation ambition, change-management capacity and risk tolerance.

Standard migration phases

Preparation — vendor selection, scope definition, implementation-partner selection, project setup. 3-9 months
Design — process design, fit-to-standard analysis, customisation specification, data-migration mapping. 3-9 months
Build — configuration, customisation, integration development, data migration. 3-12 months
Testing — unit, integration, user acceptance, performance, security testing. 2-6 months overlapping with build
Training and change management — user training, change-management workshops, process documentation. 2-4 months
Cutover — final migration, go-live weekend, hyper-care immediate-support phase. 1-4 weeks
Stabilisation — post-go-live issue resolution, performance tuning, secondary phase deployments. 3-6 months

Typical migration risks

ERP migrations carry well-documented risks. (1) Scope creep: incremental scope additions during the project compound to budget overrun and timeline slippage. Rigorous scope control is the single most important risk mitigation. (2) Data-quality surprises: legacy data is rarely as clean as the team assumes. Allow time and effort for cleansing, deduplication and master-data harmonisation. (3) Change-management deficit: business users underprepared for new processes resist adoption post-go-live; productivity drops can persist for months. Investing 15-25% of project budget in change management is the operational threshold for serious projects. (4) Customisation accumulation: every accepted custom requirement adds to long-term maintenance cost. Disciplined fit-to-standard governance is essential. (5) Cutover failure: go-live weekends with inadequate rehearsal, backup-and-restore procedures or rollback plans produce extended downtime and operational chaos. Multiple dress-rehearsals are the standard mitigation.

Frequently Asked Questions

How long does ERP migration take for mid-market DACH?

Typical durations: 12-24 months for SMB-and-lower-mid-market (under 100 employees), 18-30 months for mid-market (100-500 employees), 30-48 months for upper mid-market and enterprise. Compressed timelines (under the typical range) increase risk significantly; extended timelines often reflect scope or change-management problems.

What is the typical cost of ERP migration?

For DACH mid-market: 500,000 EUR (small operations) to 5 million EUR (mid-market). Upper mid-market and enterprise: 5-50+ million EUR. Cost components typically: 35-50% implementation services, 15-25% software licences or subscriptions, 5-15% customisation, 5-15% infrastructure, 10-20% internal effort (often unbudgeted but very real).

How do we handle parallel run during cutover?

Most migrations operate the legacy system in read-only mode for 6-24 months after cutover, providing audit access and reference for the new system. True parallel operation (transactions in both systems simultaneously) is technically very difficult, rarely justified, and almost always abandoned. Plan for legacy retention rather than parallel run.