The hour-by-hour mechanics of go-live weekend for a Sage X3 migration — what freezes and when, the reconciliation gate that closes each wave, four-corner financial reconciliation with the actual reports and tolerances, X3-specific validation scenarios including analytical-balance and stock-status reconciliation, go/no-go criteria, what rollback means once the first invoice posts, and the hypercare model that carries the programme to handover.
Cutover is the twenty-four hours when the programme's design decisions become operational facts. The Folder projection, the Automatic Journal crosswalk, the dimension rationalisation, the per-item-class tracking policy — all of these are still reversible until the cutover window opens.
At any point during the cutover window, every stakeholder needs to know: can I still post in X3? Is D365 accepting data? Which wave is running? The cutover-state matrix provides this in a single table.
The timeline below is a reference design for a mid-size manufacturing organisation with a single Folder containing two Companies across three Sites. Actual timings must be validated by Mock 3 at production volume.
The reconciliation compares corners 1 and 4 primarily (did the X3 starting position arrive correctly in D365?), with corners 2 and 3 available for root-cause analysis when corners 1 and 4 diverge.
Beyond the standard four-corner reconciliation, X3 migrations require additional validation scenarios that address X3-specific data structures:
The go/no-go decision is made by the Project Board at T+22h, after the final four-corner reconciliation completes. It is a binary decision — Go or No-Go — based on the following gate checklist:
Rollback is trivial: do nothing. X3 continues operating normally. D365 production has no data loaded beyond initial configuration (which can be wiped via environment restore).
Hypercare is a time-boxed period of elevated support between go-live and return to steady-state operations. It exists because defect volume and severity are both elevated in the weeks immediately after cutover — users encountering new processes, integrations running at production volume for the first time, and period-end processes…
Cutover is where the programme's accumulated design, testing, and rehearsal either succeeds or fails visibly. The blackout window is volume-dependent, not fixed. Reconciliation gates are hard blocks, not advisory. Rollback is available until the first real transaction posts, after which only forward-fix applies.