How a Sage X3–to–D365 F&O programme is structured across seven stages — from Orient through Stabilise — including what to inventory in the X3 estate, how the Folder projection and Automatic Journal translation gate everything downstream, how data migration waves are sequenced with X3-specific dependencies, and where X3-specific assumptions cause the most expensive failures.
A Sage X3–to–D365 Finance and Operations programme is not a like-for-like conversion. There is no same-vendor upgrade tooling, no configuration export that imports into D365, and no transpiler that converts L4G code to X++.
The following stages apply to a Sage X3–to–D365 programme regardless of methodology. The names are descriptive rather than framework-specific.
Before fit-gap workshops begin, the team needs a factual picture of what the source X3 system is actually doing. This inventory has eight components, each requiring specific extraction or analysis work.
The Folder projection determines how many D365 legal entities the programme creates, how configuration is shared or separated, and how every downstream migration object is scoped. It is the structural foundation.
The data migration is sequenced by dependency. An object cannot be loaded until all objects it references are present. The canonical model defines eight dependency-ordered waves, each with X3-specific content and dependencies.
The key role specific to an X3 programme is the Customer Sage X3 Application Owner — the person who authoritatively knows the current X3 state: Folder topology, Automatic Journal configuration, active analytical dimensions, customisation inventory (including ACTLSPE output), and freeze coordination.
Sage X3 v12 is a recurring release train — 2025 R2 (V12.0.38), 2026 R1 (V12.0.39), and subsequent sub-releases — with materially different supported-database, supported-OS, Syracuse, and Crystal Reports matrices between sub-releases. SQL Server 2016 and Oracle 12c were both dropped at 2026 R1.
A mock cutover is a full dress rehearsal of the go-live cutover sequence run against production-volume data in a sandbox environment. It measures actual data load times per wave, reconciliation results, manual corrections required, and total blackout duration.
A Sage X3–to–D365 programme succeeds or fails on the quality of two early decisions — the Folder projection and the Automatic Journal crosswalk — and on the completeness of the estate inventory that feeds them.