Cutover

Cutover is the structured sequence of activities that transitions a customer from legacy systems to Dynamics 365 at go-live. A typical cutover plan covers: final data extract from the legacy system, transformation, load into Dynamics 365, reconciliation to the penny against expected balances, integration endpoint switchover from test to live, user account activation, and the formal cut moment where the legacy system goes read-only and the new system starts accepting production transactions. Every one of those steps has to happen in order, within a fixed window, usually while the business is closed or running on a skeleton crew — which is exactly why cutover planning gets treated as its own project workstream rather than an afterthought at the end of the implementation.

In practice, the hardest part of cutover isn't any single step but the timing between them — how long the final data extract takes, how long transformation and load take against that specific data volume, how long reconciliation takes once someone actually checks the numbers, and whether all of that fits inside the go-live window before the business needs the system back. Mature implementations run a mock cutover — a complete dry-run of the entire sequence, often a month before the real one — specifically to measure those durations against a realistic data set and surface anything that would blow the window on the day. A mock cutover that reveals the data load alone takes fourteen hours is a much cheaper discovery a month early than during the actual event.

Where confusion shows up: cutover is sometimes treated as synonymous with go-live, but go-live is the moment users start working in the new system, while cutover is the mechanical sequence that gets the data and integrations to that point — a go-live can happen cleanly on a bad cutover if the team just gets lucky, and a well-executed cutover still needs a hypercare plan for the days after. A detailed minute-by-minute cutover runbook, with named owners and go/no-go decision points at each step, is one of the most important pre-go-live deliverables precisely because it turns a high-stress weekend into a checklist rather than an improvisation.