Dynamics AX to Dynamics 365 F&O Data Migration
Upgrade from Dynamics AX 2009 or AX 2012 to Dynamics 365 Finance & Operations with AI-powered data migration. Settle handles the data entity mapping, custom table analysis, and financial validation that make AX upgrades so labor-intensive.
Working with enterprise teams on active migration programs
Days
to production-ready mappings
Roughly half
the cost of consulting-led delivery
Every row
validated before go-live
Enterprise migrations routinely run months behind schedule. Yours doesn't have to.
This guide is for VPs of IT, data architects, and migration leads at companies moving data from Microsoft Dynamics AX to Microsoft Dynamics 365 — whether you're scoping, planning, or mid-program.
Dynamics AX 2012 allows direct SQL table access (CustTable, VendTable, InventTable) while D365 Finance & Operations requires data import through data entities (CustCustomerV3Entity, VendVendorV2Entity) that aggregate multiple tables with business logic layers. Settle maps AX's direct table references to the correct D365 data entities automatically — including fields not exposed in standard entities.
Based on the founding team's enterprise migration experience
Last updated July 2026
How Settle automates your Microsoft Dynamics AX to Microsoft Dynamics 365 migration
Settle maps AX direct table references (CustTable, VendTable, InventTable) to their D365 data entity equivalents (CustCustomerV3Entity, VendVendorV2Entity, ReleasedProductV2Entity) — including fields that aren't exposed in standard entities.
Financial dimension values and combinations are automatically profiled and validated against D365's dimension framework — catching invalid combinations and orphaned dimension values before migration.
AOT customizations are detected by comparing your AX schema against the standard AX baseline. Custom fields, extended tables, and modified enums are cataloged with proposed D365 extension mappings.
Settle validates number sequence continuity — ensuring migrated documents retain their original IDs while D365 sequences start from the correct next value with no overlaps.
Get your Microsoft Dynamics AX to Microsoft Dynamics 365 mapping analysis — see results in under an hour
Migration timeline: manual vs. Settle
Traditional approach
Timeline
8–16 months
Estimated cost
$1.5M+
Team size
5–10 consultants
Typically requires
×Manual field mapping in spreadsheets
×Custom ABAP/SQL extraction scripts
×3–5 mock migration cycles
×Dedicated source system consultants
×Manual reconciliation testing
With Settle
Enterprise benchmarksTimeline
Days
Estimated cost
A fraction of consulting cost
Team size
2–3 internal resources
Included
✓Schema profiling & analysis
✓AI-generated field mappings
✓Transformation SQL
✓Validation & readiness reports
✓Production-ready load files
Common challenges migrating from Microsoft Dynamics AX to Microsoft Dynamics 365
AX direct table access vs. D365 data entity framework
AX 2012 allows direct SQL access to tables like CustTable, VendTable, and InventTable. D365 F&O requires data import through data entities (CustCustomerV3Entity, VendVendorV2Entity) that aggregate multiple tables with business logic layers. Mapping AX tables to the correct data entities — and handling fields that don't surface in standard entities — requires deep analysis.
Explore related migrations →Financial dimensions restructuring
AX 2012 R3 introduced a financial dimensions framework that D365 F&O further evolved. Dimension set storage, default dimension combinations, and ledger dimension patterns all changed. Historical transactions must be migrated with their dimension values intact, and the new dimension framework validated against D365's account structure rules.
Explore related migrations →AOT customizations and overlayering removal
AX's Application Object Tree (AOT) allowed direct overlayering of standard objects — tables, forms, classes. D365 F&O eliminated overlayering in favor of extensions. Custom fields added via overlayering must be migrated to extension-based custom fields, and custom tables need equivalent data entities created in D365.
Explore related migrations →Number sequence migration and gap handling
AX and D365 use different number sequence engines. Migrated documents must preserve their original numbers for audit continuity, while new documents in D365 must start from the correct sequence. Gaps between migrated and new number sequences need careful configuration.
Explore related migrations →Microsoft Dynamics AX to Microsoft Dynamics 365 field mapping — what data moves
11 data objects typically migrated
| Source Object | → | Target Object |
|---|---|---|
| CustTable (Customer) | → | CustCustomerV3Entity |
| VendTable (Vendor) | → | VendVendorV2Entity |
| LedgerJournalTable / Trans | → | LedgerJournalEntity |
| InventTable (Item) | → | ReleasedProductV2Entity |
| SalesTable / SalesLine | → | SalesOrderHeaderV2Entity / Lines |
| PurchTable / PurchLine | → | PurchaseOrderHeaderV2Entity / Lines |
| CustTrans (AR Transactions) | → | Customer payment journal |
| VendTrans (AP Transactions) | → | Vendor payment journal |
| BOMTable / BOMLine (BOMs) | → | BillOfMaterialsV3Entity |
| ProjTable (Projects) | → | ProjectEntity |
| HcmWorker (Employees) | → | HcmWorkerEntity |
Typical enterprise migrations include 500K–10M+ records across these objects. Settle handles profiling and mapping at enterprise scale.
The cost of manual Microsoft Dynamics AX to Microsoft Dynamics 365 migration
Dynamics AX to Dynamics 365 Finance & Operations is Microsoft's primary enterprise ERP upgrade path. AX 2009 and AX 2012 customers face end-of-extended-support timelines that make migration urgent. Unlike GP-to-D365 (which is a re-implementation), AX-to-D365 F&O is conceptually an upgrade — the underlying X++ framework is shared — but the data model changes between AX 2012 and D365 F&O are significant enough that it's effectively a migration with transformation requirements.
The key technical challenge is that D365 F&O introduced data entities as the primary interface for data import/export, replacing AX's direct table access. AX customizations (AOT modifications, custom tables, extended data types) must be mapped to D365's data entity framework. Dimensions handling changed substantially — AX 2012's financial dimensions are restructured in D365 F&O with different storage patterns. Number sequences, workflow configurations, and security roles all require migration analysis.
Microsoft provides the Data Migration Toolkit and Lifecycle Services (LCS) for AX-to-D365 upgrades, but these tools handle standard data entities only. Customized AX installations — which represent the majority of enterprise deployments — require significant manual effort to map modified tables, custom fields, and ISV solutions to D365 equivalents.
Consulting-led delivery for migrations in this class typically runs $1.5M+. Settle prices it fixed and scoped — read the full cost breakdown.
Frequently asked questions
Related migration paths
Exceptions surface before the first load, not after the third.
Built by the team that ran Fortune 500 migrations by hand. Currently onboarding enterprise design partners on active migration programs.
Ready to migrate from Microsoft Dynamics AX to Microsoft Dynamics 365?
Tell us about your migration and we'll show you how Settle can help.
No commitment required. We'll review your migration scope and share a preliminary assessment within 48 hours.