# AX 2012 Table to D365 Finance and Operations Data Entity Reference

> Source: https://netray.co/tools/ax-2012-table-to-d365-data-entity-reference
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Look up the D365 F&O data entity and OData collection that corresponds to a Dynamics AX 2012 table when planning data migration.

## Category

microsoft-dynamics

## Erp

Dynamics AX 2012 / D365 Finance and Operations

## Audience

- AX developer
- D365 consultant
- Data migration lead

## Tool

**Kind:** worksheet

**Mode:** reference

**Columns:**

#### AX 2012 table

**Key:** ax_table

**Type:** text

#### Area

**Key:** area

**Type:** text

#### D365 OData entity

**Key:** entity

**Type:** text

#### Migration note

**Key:** note

**Type:** text

**Rows:**

**Ax table:** CustTable

**Area:** Accounts receivable

**Entity:** CustomersV3

**Note:** Party data (DirPartyTable) is created with the customer

**Ax table:** CustGroup

**Area:** Accounts receivable

**Entity:** CustomerGroups

**Note:** Load before customers

**Ax table:** VendTable

**Area:** Accounts payable

**Entity:** VendorsV2

**Note:** Load vendor groups and payment terms first

**Ax table:** VendGroup

**Area:** Accounts payable

**Entity:** VendorGroups

**Note:** Load before vendors

**Ax table:** InventTable

**Area:** Product

**Entity:** ReleasedProductsV2

**Note:** Product master (EcoResProduct) must exist; check product dimensions

**Ax table:** EcoResProduct

**Area:** Product

**Entity:** ProductsV2

**Note:** Shared product, released per legal entity

**Ax table:** InventLocation

**Area:** Inventory

**Entity:** Warehouses

**Note:** Sites must exist first

**Ax table:** InventSite

**Area:** Inventory

**Entity:** OperationalSites

**Note:** Load before warehouses

**Ax table:** SalesTable

**Area:** Sales

**Entity:** SalesOrderHeadersV2

**Note:** Open orders only; history is usually archived

**Ax table:** SalesLine

**Area:** Sales

**Entity:** SalesOrderLinesV2

**Note:** Load with or after header

**Ax table:** PurchTable

**Area:** Procurement

**Entity:** PurchaseOrderHeadersV2

**Note:** Open orders only

**Ax table:** PurchLine

**Area:** Procurement

**Entity:** PurchaseOrderLinesV2

**Note:** Received quantities need separate handling

**Ax table:** MainAccount

**Area:** General ledger

**Entity:** MainAccounts

**Note:** Chart of accounts is shared across legal entities

**Ax table:** CompanyInfo

**Area:** Organization

**Entity:** LegalEntities

**Note:** Each AX company maps to a D365 legal entity

**Ax table:** LedgerJournalTable

**Area:** General ledger

**Entity:** GeneralJournalHeaders

**Note:** Use journal import for opening balances

**Ax table:** ProdTable

**Area:** Production

**Entity:** ProductionOrderHeaders

**Note:** Usually migrate only released and in-process orders

**Ax table:** HcmWorker

**Area:** Human resources

**Entity:** Workers

**Note:** Worker and position data

**Ax table:** CustPaymTermsHeader

**Area:** Terms

**Entity:** PaymentTerms

**Note:** AX payment terms table name differs, check the AX table in your build

**Ax table:** InventItemGroup

**Area:** Inventory

**Entity:** ItemGroups

**Note:** Used for posting profiles

**Ax table:** NumberSequenceTable

**Area:** Organization

**Entity:** NumberSequences

**Note:** Recreate sequences, do not copy blindly

**Notes:** 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.

## Content

**Intro:** 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.

**Sections:**

#### How to use the reference

**Body:** 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.

**Bullets:**

- 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

**Body:** 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

**Body:** 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

**Body:** 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.

**Cta:** 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.

**Faq:**

#### Is this the official Microsoft mapping?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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.

## Search terms

ax 2012 to d365 data migration, CustTable d365 data entity, ax table to data entity, d365 f&o data entities list, VendTable VendorsV2, SalesTable SalesOrderHeadersV2, ax 2012 upgrade data entities, data management framework entity names

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json