A Workday migration is built around one hard constraint no relational-source migration shares: there is no database to query, only governed web services. This module covers the extractor-to-reconciler reference architecture, the canonical lookup registry that carries the Worktag-to-dimension translation, the loader's DMF sequencing, and the fifteen-dimension operational hardening register that makes the engine trustworthy under load.
Chapter 1 of this domain, Programme shape, waves and sequencing, described the seven-stage programme and the eight data-migration waves at the level a programme manager needs.
The migration engine is a Medallion Migration Engine with Reconciliation Gates. It does not try to load Workday objects directly into F&O. It first lands immutable Bronze extracts, resolves Workday semantics into a Silver canonical model, projects F&O-shaped Gold packages, then loads through DMF and measures the result against source and…
A Workday Financial Management source landscape is not a database schema with a few integration tables around it. It has a UI layer (Workday UI and Touch App), integration routes (Workday EIB, Workday Studio Integration, REST projections, SOAP endpoints, file routes and any message bus), the Workday Application Framework, and tenant…
The registry is wider than Worktags. Two distinct things in this chapter are both called "canonical": the six structural entities of the intermediate model (OperationalEvent, AccountingIntent, DimensionAssignment, SourceTrace, CutoverState, PostingResult) are the shapes data flows through, while the 37 canonical concepts are the…
A transformation matrix row is the smallest unit of design authority. It states the canonical concept, the Workday object name, the Workday attribute name for the installed Workday version, the extraction mechanism, the D365 entity name, the D365 field name, the transform rule, nullable flag, default policy, validation rule and…
Where EIB moves data into Workday one business object type at a time, the D365 loader works through the Data Management Framework (DMF): data entities (often composite entities spanning several underlying tables in one import unit), grouped by entity category (reference data, parameters, master data, transactional data, document data),…
The engine's eight architectural principles are design constraints, not slogans. It must be idempotent, resumable, observable, reconcilable, immutable at Bronze, composable at Silver and Gold, configurable rather than code-embedded, and fail loud. Every run should produce the same result for the same input; every wave should checkpoint;
Operational hardening is the difference between a migration script and a cutover system. The fifteen dimensions are:
A Workday migration engine is shaped by one fact that has no relational-source parallel: there is no database to query, only governed, paginated, throttled web services. Every stage of the reference architecture — and every dimension of the hardening register — exists partly to compensate for that constraint.