The migration engine, from extractor to reconciler
The medallion engine architecture for a Sage X3-to-D365 data migration — extractor, Bronze, Silver, Gold, DMF loader, reconciler — with X3 specifics at each tier: how Folder-scoped and company-scoped data is disambiguated, how the analytical-axis decomposition feeds the transformer, how DMF packages are built and tracked, and the operational-hardening controls that separate a production-grade engine from a pile of scripts.
What you will be able to do
Explain why a canonical lookup layer is required for an X3 migration rather than point-to-point field mapping
Describe the X3-specific extraction pathways and when each applies
Trace a value from the X3 source through Bronze, Silver, Gold and into DMF with X3-specific transformations at each tier
Explain how Folder-scoped and company-scoped data is disambiguated in the Silver tier
Describe how the analytical-axis decomposition is applied in the transformer
Name the operational-hardening controls and the specific risk each one closes
Introduction
A Sage X3-to-D365 data migration moves tens of millions of rows across eight dependency-ordered waves, through a pipeline that must transform X3's Folder-scoped, analytically-dimensioned, Automatic-Journal-derived data into D365's legal-entity-scoped, dimension-combination-referenced, posting-profile-governed shape.
Engine architecture overview
The engine follows the medallion pattern — Bronze, Silver, Gold — with X3-specific adapters at the extraction edge and DMF at the load edge.
Extraction: getting data out of Sage X3
The extraction strategy is volume-driven, not technology-driven. Each pathway serves a specific purpose:
Silver tier: resolution and conformation
Silver is where X3-specific interpretation begins. The Silver tier performs four transformations that are specific to X3's data model:
Gold tier: D365 entity shaping
Gold reshapes Silver's canonical records into the exact format that DMF data entities expect. This is where column names change to D365 entity field names, enumerations are mapped to D365 values, and composite-entity grouping is applied.
The transformation-rule registry, lookup resolver and DMF loader
At migration scale — thousands of master records, millions of transactions — the same X3 concept appears in dozens of different entity transforms. A Company code, a Site code, an Analytical Dimension value, a Unit of Measure, an Accounting Code — each must be translated the same way everywhere it appears.
Reconciliation and gate enforcement
At every wave boundary, the reconciler compares four data points for each canonical concept:
Operational hardening
The following controls separate a production-grade migration engine from a pile of scripts. Each closes a specific risk.
Knowledge check
Summary
The migration engine is the mechanism that converts the programme's design decisions — Folder projection, Automatic Journal crosswalk, dimension rationalisation, item-class tracking policy — into actual data movement. Without it, those decisions remain documents.