Business Central go-live: how do I know whether we are ready?

Readiness is more than a green test report. You are ready when three things are proven rather than assumed, and all three are demonstrable rather than a matter of judgement. First, at least two complete migration test runs: the first uncovers the coarse problems, the second shows whether you actually solved them. Test the migration only once and you are migrating for real for the first time on go-live day. Second, a cutover dress rehearsal, meaning you play the switch through once in full, with a schedule, roles and a fallback point. Only then do you know whether the window is realistic and who does what if things go wrong. Third, measurable go/no-go criteria instead of gut feeling in the steering committee: data reconciles, critical processes run end to end, key users are trained, the fallback plan exists. A green report without a real rehearsal is an assumption, not readiness.

What makes real go-live readiness?

A green test report is an assumption, not readiness. You are ready only once three things are evidenced rather than merely assumed. And all three are demonstrable rather than a matter of judgement:

1. Two or more migration test runs: the first run uncovers the coarse problems, the second shows whether you have really solved them. Whoever tests the migration only once migrates for real for the first time on go-live day.
2. Cutover dress rehearsal: play through the switch once completely, with schedule, roles and a fallback point. Only then do you know whether the cutover window is realistic and who does what in an emergency.
3. Measurable go/no-go criteria: clearly defined conditions instead of gut feeling in the steering committee. The data reconciliation adds up, critical processes run end to end, key users are trained, and the fallback plan is in place.

Source: Microsoft Learn: Set up company configuration packages

Why do you need business sign-off and the courage for a no-go?

A technical test alone is not enough. The critical processes belong walked through by the business departments on real data, not merely ticked off by the project team. Only the business sign-off shows whether operations actually run on day one.

The difference is greater than it sounds. The project team checks whether the system does what was once specified. The business checks whether it does what the working day demands, and those two questions regularly diverge, because by no means every requirement was documented.

An honest no-go is a senior decision, not a failure. A postponed go-live costs less than a go-live that collapses in day-to-day operations. Control stays on your side. If you are facing go-live and are unsure whether green really means ready here, we examine your criteria together in a conversation.