The constraint nobody writes down
Every ERP migration plan opens with the target architecture. Almost none open with the sentence that actually governs the project: the business does not pause. Orders keep arriving, payroll runs, and the month still closes on the last working day.
Plan from that constraint and most of the hard decisions make themselves.
Move in slices, not at once
A single cutover weekend is a bet that everything works on the first attempt, with no way back and an audience. We move one process at a time — usually procurement first, because it is self-contained and its failures show up within days rather than at quarter end.
Each slice runs in the new system while the old one stays authoritative, until the numbers agree for a full cycle.
Reconcile in public
- Pick the handful of figures the finance team already checks daily.
- Report both systems' answers side by side, every day, where everyone can see them.
- Treat any gap as a blocker for the next slice, not a note for later.
Data is the project
Extraction is a week. Cleaning is a quarter. Duplicated suppliers, three spellings of the same customer, a unit of measure that means something different in one plant — this is where the schedule actually goes, and it is not a technical problem you can solve without the people who own the data.
Train on the real thing
Training on a demo dataset teaches the buttons. Training on last month's real transactions teaches the job. The second is harder to arrange and the only one that survives contact with go-live week.
Part of the team building and running the products behind these posts at Hedaya Global Solutions.
