The same-lineage upgrade and what it does not buy you
Understand why AX 2012's shared lineage with D365 F&O makes the data and finance core identity-mapped — and why programme effort concentrates almost entirely on code, platform surfaces and upgrade blockers.
What you will be able to do
Explain what same-vendor lineage actually buys and where it stops
Describe the AOT, model store and layer architecture as AX 2012's defining technical primitive
Distinguish in-place upgrade (Mode A) from reshape/re-implementation (Mode B) and articulate how a customer chooses
Name the four defining AX 2012 challenges that absorb the bulk of programme effort
Trace the event → intent → voucher → ledger pipeline both systems share
Identify the blockers and decisions a programme must resolve before configuration begins
Introduction
Every ERP migration starts with a question the programme must answer honestly: how much of the source system's architecture survives in the target? For most paths on this site — SAP, Oracle, Workday, Infor — the answer is "almost nothing structural." The source and target are unrelated systems, and the programme's dominant effort is…
The AOT, model store and layer architecture
AX 2012's defining technical primitive is the Application Object Tree (AOT) — the hierarchical container for every piece of metadata the system uses: tables, extended data types (EDTs), enums, classes, forms, queries, menus, reports, and workflows.
Two programme modes: how a customer chooses
Microsoft documents, and the programme must commit to, one of two migration modes — or a deliberate hybrid of both.
The four defining AX 2012 challenges
Each of these concentrates programme effort on a surface that is not the data or finance core. Together they are the honest answer to "where does the money go?"
The shared pipeline: event → intent → voucher → ledger
Both AX 2012 and D365 F&O run the same accounting pipeline, and understanding it makes the reconciliation workstream tractable:
What must be resolved before configuration begins
The following decisions and remediations sit on the critical path. None can be deferred without blocking downstream workstreams:
Knowledge check
Summary
AX 2012 and D365 F&O share a lineage. The financial core — companies, posting profiles, dimensions, security — is identity-mapped, and Microsoft ships tooling to bring it forward. This is a genuine structural advantage that no other source system on this site enjoys.