The end-to-end programme structure for an Oracle Fusion Cloud ERP to Dynamics 365 F&O migration — from source-estate inventory through seven programme stages, eight data-migration waves, cutover choreography, and hypercare — with the Fusion-specific traps that catch unprepared programmes.
A Fusion-to-D365 programme is not a simple lift-and-shift. Fusion is a strong, modern, cloud-native ERP. The migration is a deliberate portfolio decision — typically driven by M&A consolidation, Microsoft Cloud platform alignment, or operational estate simplification.
A Fusion-to-D365 programme runs through seven named stages. Each stage has a defined set of deliverables that the next stage depends on.
The estate inventory, produced in the Discover phase, is the dependency map for the entire programme. It covers eight categories.
The SLA translation does not fit neatly into the Build phase. It is a pre-wave workstream that must begin at the end of the Discover phase and complete before Wave 1 design is locked, because D365 posting profiles are a prerequisite for every functional test in every wave.
The migration engine executes eight dependency-ordered waves inside the cutover window — a target of roughly 24 hours, legitimately extending to 48 or 72 for a larger estate. The ordering is driven by foreign-key dependencies: each wave's targets reference objects loaded in prior waves.
The cutover window runs from T-0 (Fusion transaction freeze and final GL Transfer) to the point F&O opens and hypercare begins. The T-offsets below assume the ~24-hour target; stretch them proportionally if the estate justifies a 48- or 72-hour window. The sequence:
Hypercare runs for a defined period — the Stabilise stage budgets 8–12 weeks, though programmes with a narrow scope sometimes close it earlier. The hypercare team covers:
The Fusion-to-D365 programme is not only an application replacement. It is an identity, data, integration, analytics and operations shift from Oracle-managed SaaS boundaries to a Microsoft-centred estate. Fusion identity commonly sits behind Oracle IDCS or a federated identity provider;
A Fusion-to-D365 programme succeeds when the Fusion estate is fully inventoried, the SLA translation is treated as a pre-wave workstream rather than a Build phase task, and the three Fusion-specific traps are explicitly mitigated from the Discover phase onwards.