Upgrade tooling end to end and the medallion migration engine
The two migration routes in full technical detail — Route A: the Upgrade analyzer, model-store preparation, code upgrade service, data upgrade process, and LCS lifecycle; Route B: the medallion reshape engine from extractor through Bronze, Silver, Gold to DMF loader and reconciler — plus the operational-hardening controls that separate a production-grade engine from a pile of ad-hoc scripts, and the honest comparison of when each route wins.
What you will be able to do
Trace the in-place upgrade route end to end: Upgrade analyzer → model-store export → code upgrade service → data upgrade → validation
Explain what each Microsoft tool produces and what it leaves for a human
Name the operational-hardening controls and the specific risk each one closes
Decide, for a given engagement, whether Route A, Route B, or a hybrid applies
Explain the idempotency, restartability, and reconciliation design that makes either route production-grade
Introduction
The programme shape chapter established the mode decision — in-place upgrade (Route A) versus medallion reshape (Route B) — as the defining structural choice for an AX 2012 to D365 migration.
Route A: Microsoft's in-place upgrade tooling
Route A follows three phases — Analyse, Execute, Validate — using Microsoft's first-party tooling delivered through Lifecycle Services.
Route B: the medallion reshape engine
Route B applies when the programme requires data cleansing, operating-model change, or selective data carry that the in-place upgrade cannot provide. It loads a fresh D365 environment through DMF after reshaping data in a structured pipeline.
Operational-hardening controls
Both routes require hardening controls that separate a trustworthy migration system from an ad-hoc collection of scripts. The following controls apply to the reshape engine (Route B) and, where applicable, to the upgrade validation harness (Route A).
When each route wins: the honest comparison
Code and configuration via Route A (code upgrade service converts code; data upgrade carries configuration and history) Selected data domains via Route B (party/address data cleansed and deduplicated; inventory rebalanced; deprecated modules retired) Reconciliation proves consistency at every join point between the two routes
Knowledge check
Summary
Both upgrade routes — Microsoft's in-place tooling and the medallion reshape engine — are legitimate, technically sound approaches to moving an AX 2012 estate to D365 Finance and Operations. The choice between them, or the boundary of a hybrid, depends on the estate's condition and the programme's ambitions.