The software is rarely the problem.
In ERP migrations, projects stall on data nobody has checked, on rules only the business knows,
and on a cutover weekend without a runbook.
Data quality only shows up in the test migration.
Duplicate suppliers, missing purchasing info records, assets in the wrong class: what worked in the legacy
system for years breaks during migration. Cleanup that starts only in the third test migration
(mock migration) pushes back the go-live.
Business teams are brought in too late.
Materials planning, purchasing, and the warehouse run on rules that are not written down anywhere. If the new
system lacks them, you notice on the first Monday after cutover: at the loading dock and in the MRP list.
The cutover is improvised.
On the cutover weekend, inventory, open purchase orders, and asset values move to the new system. That
requires a cutover runbook with owners, time windows, and abort criteria.
Every month of delay has a cost.
The project team stays tied up, and day-to-day business runs short of key users. If you still need fixes for
SAP ECC after 2027, you pay a premium for extended maintenance.
We start with the causes: the data, the rules of the business, and the weekend when you switch over.