Go-live

Go-live is the moment a Dynamics 365 implementation stops being a project and becomes a production system. It is when migrated master data and opening balances are loaded, integrations are switched to live endpoints, the previous system is frozen or decommissioned, and users start posting real transactions. Go-live is preceded by user acceptance testing, a final data migration rehearsal, and a cutover plan that maps every step over a defined window. Most go-lives run with extra partner support for two to four weeks afterwards — known as hypercare — to handle questions and fixes before transitioning to steady-state support.

In practice, the cutover window is the highest-risk few days of an entire implementation, because it's the one point where the old and new systems are both, briefly, in an inconsistent state — data has been extracted from the old system but not yet fully validated in the new one, and users are typically locked out of both for some hours. A well-run cutover plan lists every step with an owner and a rollback trigger (a specific, pre-agreed condition that means "stop and revert to the old system") rather than hoping the migration works and figuring out a rollback plan only if it doesn't.

Where confusion shows up: go-live is not the same milestone as "project complete" — hypercare, a stabilisation period, and often a formal post-go-live support handover all follow it, and treating go-live weekend itself as the finish line is what leads teams to under-resource exactly the weeks when users are least confident and most likely to hit an edge case nobody tested for.