The 60+ item dynamics ax migration checklist. AOS environment audit, AOT object inventory across 16 X++ layers, SQL Server row counts per LE, EDT inheritance map, Financial Dimension activity, AIF integration ports, report library, attachment volumetrics, 2026 cliff status, sign-off owners.
Sixty checklist items sounds excessive until you discover at week 14 that no one profiled InventDim and the InventTrans-to-Fusion load is now blocked.
Microsoft Dynamics AX is large. AX 2012 ships with over fifteen hundred standard tables. Customer-extended layers commonly add several hundred more. Multi-LE deployments multiply that by the number of legal entities. EDTs (Extended Data Types) provide inheritance-based typing where a custom EDT can silently affect hundreds of tables. AIF integration ports are wired to upstream and downstream systems with long-tail customer-specific business logic embedded in document classes. Financial Dimensions provide an analytical posting axis with potentially millions of active combinations across LedgerJournalTrans. Number Sequences carry statutory significance per region.
The dynamics ax migration checklist is the systematic way to make sure nothing in any of that complexity gets missed during assessment. Each of the 60+ items is a check-and-attest with hard evidence — an export, a screenshot, a query output, an AOT extract, a SQL row count — and a named sign-off owner who confirms the item has been verified. Items range from infrastructure (AOS version, SQL Server version, Windows Server version, .NET framework version) through technical inventory (AOT object catalogue across all 16 layers, EDT inheritance map, AIF integration port list, Financial Dimension activity) to business context (statutory retention per legal entity, Number Sequence statutory significance, report library catalogue, sign-off ownership per data domain).
Completing the dynamics ax migration checklist is the deliverable that ends the assessment phase and triggers the design phase. Typical mid-sized AX customer (3–8 LEs, AX 2012 R3, moderate customization, 7–10 years history) completes in 3–4 weeks. Larger customers (>15 LEs, heavy customization) commonly take 5–6 weeks. Either way the checklist becomes the controlled-document baseline that the rest of the programme references — every design decision, every transformation rule, every reconciliation gate, every cutover-weekend activity traces back to a verified checklist item.
High-leverage checklist sections that catch the most common late-stage surprises.
Version, CU level, resource utilisation, backup config, peak user-session count. Catches: late-stage discovery that AOS is below required CU level and needs upgrade pre-cutover.
Every X++ object walked across SYS/SYP/GLS/GLP/FPK/FPP/SLN/SLP/ISV/ISP/VAR/VAP/CUS/CUP/USR/USP. Catches: customizations no one remembered existed in the VAR or ISV layers.
Every EDT resolved through its inheritance chain. Catches: custom EDT extending CustGroup silently affecting 40 tables — discovered before it causes failed FBDI loads.
Every active dimension combination from LedgerJournalTrans enumerated. Catches: orphaned dimensions no one remembered configuring that have to route somewhere in the Fusion COA.
Per-table per-DataAreaId row counts for LedgerJournalTrans, InventTrans, SalesLine, PurchLine, VendInvoiceJour, CustInvoiceJour. Catches: anomalous volumes flagging operational complexity differences.
Current CU level, extended support contract status, planned completion date relative to 2026. Catches: programmes inadvertently planned to complete after 2026 cliff with no contingency.
Typical 3–4 week sequence. Larger customers extend to 5–6 weeks.
AOS audit run (version, CU level, resource utilisation, backup config, peak user-session count). AOT crawler walks all 16 X++ layers and produces base-vs-overlay classification. SQL row counts per LE per table. AIF integration port catalogue extracted. Attachment volumetrics from DocuRef/DocuValue.
Financial Dimension combinations from LedgerJournalTrans enumerated. Number Sequence catalogue with statutory-significance flag per sequence. Report library catalogued across SSRS, MorphX, Management Reporter. Statutory retention requirements documented per LE.
Every X++ overlay from the AOT inventory classified retire / replace / rebuild. EDT inheritance map walked. Custom Table / EDT / field catalogue completed. Workflow definitions inventoried. The customization budget that drives the rest of the programme.
Per-domain sign-off owners named (finance lead, supply chain lead, procurement lead, HR lead, IT lead, internal audit lead, statutory audit liaison). Each owner attests the relevant checklist sections.
Hard evidence (exports, screenshots, query outputs, AOT extracts, SQL row counts) curated per item. Controlled-document baseline established. Stakeholder review meeting per domain.
Final review by programme sponsor and statutory audit liaison. Checklist signed. Baseline locked under change control. Assessment phase closes. Design phase triggers — dynamics ax to oracle fusion mapping starts.
The checklist is week 1–4 work that pays back every subsequent week of the programme.
Dynamics ax to oracle fusion mapping starts in week 5 with the customization inventory, EDT map and FD activity already locked. No three months of consultant-interview-driven discovery.
FBDI batch sizing, transformation pipeline sizing, cutover-weekend timing all derived from SQL row counts. No surprise mid-project on data-volume-driven complexity.
X++ rebuild budget known by week 3. Replan or descope happens at week 4 rather than week 14. Programme timeline derives from a verified customization triage.
Per-LE retention requirements documented. Country-statutory variants flagged. Migration plan accommodates HGB 10yr, HMRC 6yr, SOX 7yr, PCG compliance without late-stage retrofit.
AIF integration port catalogue drives the integration rewiring plan from week 5 onward. Every upstream/downstream system identified. No surprise integration discoveries at cutover Sunday.
Named sign-off owners per domain own the verified items through to cutover. No 'no one signed off on that' moments at sign-off Sunday.
The dynamics ax migration checklist is a 60+ item pre-migration audit covering AOS environment health, AOT object inventory, SQL Server row counts per legal entity, X++ customization layer profile, EDT inheritance map, Financial Dimension activity, Number Sequence catalogue, AIF integration port list, SSRS / MorphX / Management Reporter report inventory, attachment storage volumetrics, statutory retention requirements per legal entity, current 2026-extended-support status, infrastructure decommissioning prerequisites and stakeholder sign-off owner per domain. Each item is a check-and-attest with hard evidence (export, screenshot, query output) — not a verbal answer. The dynamics ax migration checklist drives the assessment phase and becomes the controlled-document baseline that the rest of the programme references.
Because AX is large. AX 2012 ships with over fifteen hundred standard tables. Customer-extended layers commonly add several hundred more. Multi-LE deployments multiply that by the number of legal entities. The dynamics ax migration checklist is the systematic way to make sure nothing is missed during assessment — every relevant table is profiled, every X++ overlay is catalogued, every EDT is resolved, every Financial Dimension combination is enumerated, every AIF port is inventoried, every report is catalogued, every statutory retention requirement is documented. Sixty items sounds excessive until you discover at week 14 that no one profiled the InventDim table and the InventTrans-to-Fusion load is now blocked. The checklist front-loads the rigour that consultant-led projects discover painfully mid-stream.
AOS audit covers the runtime environment: AOS version (RTM, R1, R2, R3 CU level), Windows Server version, .NET Framework version, SQL Server version, current user-session count, current batch-server job count, current AIF inbound/outbound message volume, AOS resource utilisation patterns (peak CPU, peak memory, peak SQL connections), backup and recovery configuration, security model (Active Directory integration, role-based-access model). Each item gets a check-and-attest. The audit identifies pre-cutover housekeeping (apply latest CU if behind, clean up orphaned batch jobs, drain stale AIF messages) that improves cutover-weekend reliability. The dynamics ax migration checklist's AOS audit section is typically a 12-item subsection of the larger checklist.
AOT inventory walks the Application Object Tree to enumerate every X++ object — Tables, Classes, Forms, Reports, Jobs, Maps, Macros, Views, Queries, Extended Data Types, Enum Types, Number Sequences, Workflow definitions, Web Services, Service Groups — across all 16 layers (SYS, SYP, GLS, GLP, FPK, FPP, SLN, SLP, ISV, ISP, VAR, VAP, CUS, CUP, USR, USP). Each object is identified as base (matches the layer below) or overlay (modified relative to the layer below). Overlays are flagged for the customization-inventory step where retire/replace/rebuild classification happens. The dynamics ax migration checklist's AOT inventory section produces the X++ overlay catalogue that drives the migration timeline — more overlays means more rebuild work, which extends the programme.
Row counts per table per legal entity (DataAreaId) profile the data volume that has to extract, transform and load. LedgerJournalTrans, VendInvoiceJour, CustInvoiceJour, SalesTable, SalesLine, PurchTable, PurchLine, InventTrans, InventSum, CustTable, VendTable, InventTable — every transactional and master-data table that matters in the migration. Row counts plus average row size give the load-volume estimate that drives FBDI batch sizing and cutover-weekend timing. They also flag tables with anomalous volumes (one LE has 50M rows in InventTrans, another has 5M — different operational profile, different complexity). The dynamics ax migration checklist's SQL row-count section is the foundation for sizing the entire programme.
The 2026 cliff item flags where you sit relative to Microsoft's extended support timeline for AX 2012. Microsoft ended mainstream support October 2021. Extended Support runs through 2026 at premium pricing without new features. The dynamics ax migration checklist captures: current cumulative update level (R3 CU13 is end-of-line), Microsoft extended support contract status (current renewal cost, renewal date, vendor lock-in implications), risk register entry for the 2026 cliff exposure, planned migration completion date relative to the 2026 deadline. The cliff item drives the urgency of the programme — customers with 2027 completion plans need to either accelerate or accept paying for extended support beyond 2026 (which Microsoft will price punitively to push customers to D365 F&O).
Each domain in the dynamics ax migration checklist has a named sign-off owner who attests that the item has been verified and the result is correct. Finance lead signs off the ledger / chart-of-accounts / Financial Dimension sections. Supply chain lead signs off the inventory / sales / purchase sections. Procurement lead signs off the vendor / purchase order sections. HR lead signs off the workforce sections if HR is in scope. IT lead signs off the AOS / AOT / AIF / SQL infrastructure sections. Internal audit lead signs off the data-conversion-controls / SOX sections. Statutory audit liaison signs off the country-specific retention sections. The sign-off-owner column is what turns the dynamics ax migration checklist from a working document into a controlled-document baseline.
Three to four weeks for a typical mid-sized AX customer (3–8 legal entities, AX 2012 R3 environment, moderate X++ customization, 7–10 years of transactional history). The first week is technical inventory — AOS audit, AOT crawler runs, SQL row counts, AIF port catalogue, attachment volumetrics. The second week is business inventory — Financial Dimension combinations, Number Sequence statutory significance, report library catalogue, statutory retention requirements per LE. The third week is sign-off owner assignment, evidence-pack curation, stakeholder review and attestation. The fourth week (if needed) is iteration on the items that surfaced gaps. Larger customers (>15 LEs, heavy customization, 15+ years of history) commonly take 5–6 weeks. The dynamics ax migration checklist completion is the deliverable that ends the assessment phase and triggers the design phase.
We will run the AOT crawler, SQL row-count profiler, AIF port catalogue extractor and Financial Dimension enumerator on your AX environment and return your specialised dynamics ax migration checklist with hard evidence — typically within 10 working days.