The hour-by-hour cutover mechanics for a Maconomy-to-D365 migration — source freeze sequence, final delta processing, four-corner reconciliation with control totals, WIP and unbilled-revenue reconciliation, the T-minus timeline, go/no-go criteria, rollback and source reactivation, and the hypercare model through to handover.
Cutover is the period when the programme's design decisions become operational facts. The dimension rationalisation, the project-archetype classification, the WIP recognition method, the billing-rule mapping — 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 Maconomy? Is D365 accepting data? Which wave is running? The cutover-state matrix provides this in a single printable table.
The timeline below is a reference for a professional-services firm with two legal entities across three countries. Actual durations are validated by Mock 3.
Before a single record is extracted for the production cutover, the finance controller must confirm that Maconomy's own books are in balance.
After all eight waves complete and before the go/no-go decision, the target-side check validates that D365's own books are internally consistent.
This is the hardest control in a professional-services migration. WIP is not a stored balance — it is an accounting position derived from the relationship between costs incurred, revenue recognised, and amounts billed.
The opening-position reconciliation is the formal artefact that the finance controller signs to confirm the migrated balances are correct. It is the single most important sign-off in the cutover window.
The go/no-go decision at T+23h is binary: proceed to open D365 for business, or invoke rollback. The decision is made by the programme board against pre-agreed criteria.
The rollback procedure must be tested in pre-production as part of Mock 2 or Mock 3. The test validates:
Hypercare is the period between go-live and formal handover to steady-state operations. For a Maconomy migration, it covers:
Cutover for a Maconomy programme centres on the project-to-cash lifecycle: the WIP and unbilled-revenue reconciliation is the hardest single control, and the billing cycle is the critical hypercare validation.