The most dangerous hour in any system replacement is the one where the old system is switched off.
Most failed deployments don’t fail during the build. They fail on the Monday the business is asked to trust something it has not yet seen work.
One date, every unknown
A single switch-over date concentrates every unknown into one day: data that did not migrate cleanly, a workflow nobody thought to mention. When something breaks there is no way back, only a long afternoon.
Run both
Record real transactions in both systems for an agreed period and compare the outputs every day: stock counts, invoice totals, patient registers. It costs extra effort for a few weeks. It is the cheapest insurance in the whole project.
Nobody should be asked to trust a system they have not already watched give the right answer.
Write down what “matched” means
Which reports must reconcile, and to what tolerance. How many consecutive clean days before cutover. Who signs off, by name. What triggers a rollback, and who decides.
Keep the way back open
The old system stays read-only for a defined period after sign-off. Rollbacks are rarely needed. Knowing they exist is what lets people commit.
Train on real work
Training on a demo environment teaches people a demo. The questions asked at the counter are the ones that reveal what the workflow map got wrong.