AX 2012 Table to D365 Finance and Operations Data Entity Reference
Moving from Dynamics AX 2012 to Dynamics 365 Finance and Operations means replacing direct table reads with data entities. This lookup pairs common AX 2012 tables with the D365 entity and OData collection name you would use to load or read the same data.
| AX 2012 table | Area | D365 OData entity | Migration note |
|---|---|---|---|
CustTable | Accounts receivable | CustomersV3 | Party data (DirPartyTable) is created with the customer |
CustGroup | Accounts receivable | CustomerGroups | Load before customers |
VendTable | Accounts payable | VendorsV2 | Load vendor groups and payment terms first |
VendGroup | Accounts payable | VendorGroups | Load before vendors |
InventTable | Product | ReleasedProductsV2 | Product master (EcoResProduct) must exist; check product dimensions |
EcoResProduct | Product | ProductsV2 | Shared product, released per legal entity |
InventLocation | Inventory | Warehouses | Sites must exist first |
InventSite | Inventory | OperationalSites | Load before warehouses |
SalesTable | Sales | SalesOrderHeadersV2 | Open orders only; history is usually archived |
SalesLine | Sales | SalesOrderLinesV2 | Load with or after header |
PurchTable | Procurement | PurchaseOrderHeadersV2 | Open orders only |
PurchLine | Procurement | PurchaseOrderLinesV2 | Received quantities need separate handling |
MainAccount | General ledger | MainAccounts | Chart of accounts is shared across legal entities |
CompanyInfo | Organization | LegalEntities | Each AX company maps to a D365 legal entity |
LedgerJournalTable | General ledger | GeneralJournalHeaders | Use journal import for opening balances |
ProdTable | Production | ProductionOrderHeaders | Usually migrate only released and in-process orders |
HcmWorker | Human resources | Workers | Worker and position data |
CustPaymTermsHeader | Terms | PaymentTerms | AX payment terms table name differs, check the AX table in your build |
InventItemGroup | Inventory | ItemGroups | Used for posting profiles |
NumberSequenceTable | Organization | NumberSequences | Recreate sequences, do not copy blindly |
Entity names change between D365 releases and V2/V3 suffixes appear as entities are versioned. Always confirm in Data management, Framework parameters, Data entities, and in your environment's metadata at /data/$metadata.
Want help with an AX entity mapping?
An optional review of your AX to D365 data scope and entity mapping.
Optional. The tool and every export work without this. No spam.
How to use the reference
Search for the AX table you already extract from. The OData entity column is the name you use in a URL such as /data/CustomersV3 and in the Data management workspace. The migration note flags the dependency or trap that usually bites first. Use the load order implied by the notes: organization and sites, then groups and terms, then masters, then open transactions.
- Export the table and add your own row counts per legal entity
- Mark entities you will retire instead of migrate
- Share the sheet with the functional team to agree the scope
Why AX tables do not map one to one
D365 normalised some data AX kept together. Customers and vendors now sit on a global address book, products are shared and released per legal entity, and dimensions are financial dimension frameworks instead of fixed fields. A single data entity can write several underlying tables, and a single AX table can feed several entities. Treat this list as the starting point of a mapping, not the mapping itself.
Typical scoping decision
Most upgrade projects migrate master data, open balances and open orders, and archive the rest. Moving ten years of settled transactions into a new system rarely pays for itself. Decide per entity: migrate, load as opening balance, or archive and report from outside. Customisations in AX 2012 that wrote their own tables need new custom entities, so list those early.
Common mistakes
Teams often load transactions before the setup data they depend on, then chase mysterious validation errors. Others rely on an entity name from a blog written for an older release. Verify names against your own environment metadata, and run every entity import in a sandbox with production-sized data before the real cutover.
Frequently Asked Questions
Is this the official Microsoft mapping?
No. It is a working guide built from common AX 2012 and D365 F&O structures. Microsoft's data entity documentation and your environment's /data/$metadata endpoint are the authoritative sources for names and fields in your release.
Why do some entities end in V2 or V3?
Microsoft versions data entities when it makes breaking changes. CustomersV3 replaced earlier customer entities. Use the latest version your environment exposes, and avoid hard coding names in scripts without a check at upgrade time.
Do I need entities for every AX table?
No. Many AX tables are internal, log or temporary tables and have no entity. Focus on masters, setup, open transactions and opening balances. Everything else is usually archived or recreated by the system.
How do customisations fit in?
Custom AX tables need a custom data entity built in Visual Studio in D365, plus a mapping for any extension fields on standard tables. Inventory these early because they drive both effort and timeline.
If you are mapping AX customisations and data to D365, we can help generate extraction and reconciliation tooling that reads your AX database without writing to it.
Related Tools
D365 Finance and Operations OData URL and Token Request Builder
Generate the OData request and OAuth token call to read data entities from D365 F&O during an AX migration or validation.
Microsoft DynamicsDynamics GP Work, Open and History Table Map
A searchable list of Dynamics GP tables grouped by lifecycle: master, work, open and history, so you know where a transaction lives at each stage.
Microsoft DynamicsDynamics GP Third-Party Add-On Dependency Assessment
Answer ten questions to score how much ISV add-ons, custom code and integrations will complicate a move off GP or AX.
More Microsoft Dynamics tools
See all- D365 F&O Manufacturing Data Entities Reference
- D365 F&O OData URL Builder
- D365 Production Order Status Reference
- D365 Data Management Import Worksheet Template
- D365 Batch Job Checklist
- D365 Security Role Design Worksheet
- D365 Master Planning Setup Checklist
- D365 One Version Update Test Checklist
- D365 Finance and Supply Chain Functional Design Document Template
New to Microsoft Dynamics AX 2012? Start with the Microsoft Dynamics AX 2012 guide and toolkit.
Keep exploring
Free tools
- AX 2012 to D365 Data Entity Mapping WorksheetPlan each AX 2012 data object, its D365 data entity, load sequence, record count and owner in one editable migration sheet.
- AX 2012 to D365 Finance and Operations Upgrade Effort EstimatorBottom-up hours, cost and duration estimate for an AX 2012 to Dynamics 365 Finance and Operations upgrade.
- Dynamics AX 2012 X++ Table Methods ReferenceThe xRecord methods you override or call on an AX 2012 table, when the kernel calls each one, and the find/exist conventions, with tips that keep set-based operations fast.
ERP fixes and how-tos
- Planning an AX 2012 to Dynamics 365 Finance and Operations upgradeHow an AX 2012 to Dynamics 365 Finance and Operations upgrade actually runs: LCS upgrade project, code upgrade of customizations, and data migration, with the main risks.
- Adding a Private AI Layer to Dynamics AX 2012 On-PremAdd AI to Dynamics AX 2012 on-prem without moving data: SQL replica, AIF services, retrieval index, local LLM, mirrored AX roles, approved write-back.
- Dynamics 365 Supply Chain Management API: OData, Custom Services and Data PackagesD365 Supply Chain / F&O APIs explained: OData data entities, custom services, the data management package API, Entra ID authentication and when to use each.
AI on your ERP
- AI for Dynamics AX 2012, Without the Forced MigrationDynamics AX 2012 R3 left mainstream support in 2021. Add a private LLM over AX data now, use it to de-risk a future migration, without a forced move to D365.
- AI for Dynamics 365 Finance and Supply Chain beyond CopilotAI for D365 Finance and Supply Chain beyond Microsoft Copilot: private LLM grounded on data entities and OData, on-prem-capable via Local Business Data.
Integrations
- How to add AI agents to Microsoft Dynamics AX 2012How to add AI agents to Dynamics AX 2012 using AIF services, SQL read paths and approval gates, without a forced move to Dynamics 365 first.
- How to use ChatGPT with Microsoft Dynamics AX 2012How to use ChatGPT with Dynamics AX 2012: exports versus live access, custom GPT actions over AIF, enterprise data controls and when to go private.