# AX 2012 to D365 Data Entity Mapping Worksheet

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

## Short answer

Plan each AX 2012 data object, its D365 data entity, load sequence, record count and owner in one editable migration sheet.

## Category

microsoft-dynamics

## Erp

Microsoft Dynamics AX 2012

## Audience

- Data migration lead
- AX developer
- D365 consultant

## Tool

**Kind:** worksheet

**Mode:** editable

**Columns:**

#### Load order

**Key:** seq

**Type:** number

#### AX 2012 table

**Key:** ax_table

**Type:** text

#### D365 data entity

**Key:** entity

**Type:** text

#### Records

**Key:** records

**Type:** number

**Format:** integer

#### Records per load batch

**Key:** batch_size

**Type:** number

**Format:** integer

#### Load batches

**Key:** batches

**Type:** number

**Expr:** ceil(records / batch_size)

**Format:** integer

#### Cleansing needed

**Key:** cleanse

**Type:** select

**Options:**

- None
- Light
- Heavy

#### Owner

**Key:** owner

**Type:** text

#### Status

**Key:** status

**Type:** select

**Options:**

- Not started
- Mapped
- Test loaded
- Validated

**Rows:**

**Seq:** 1

**Ax table:** LedgerTable

**Entity:** Main accounts

**Records:** 650

**Batch size:** 500

**Cleanse:** Light

**Owner:** Finance lead

**Status:** Mapped

**Seq:** 2

**Ax table:** CustTable

**Entity:** Customers V3

**Records:** 8400

**Batch size:** 2000

**Cleanse:** Heavy

**Owner:** Sales ops

**Status:** Mapped

**Seq:** 3

**Ax table:** VendTable

**Entity:** Vendors V2

**Records:** 3100

**Batch size:** 2000

**Cleanse:** Light

**Owner:** Procurement

**Status:** Test loaded

**Seq:** 4

**Ax table:** InventTable

**Entity:** Released products V2

**Records:** 41000

**Batch size:** 5000

**Cleanse:** Heavy

**Owner:** Product data

**Status:** Not started

**Seq:** 5

**Ax table:** SalesTable

**Entity:** Sales order headers V2

**Records:** 1250

**Batch size:** 1000

**Cleanse:** None

**Owner:** Sales ops

**Status:** Not started

**Seq:** 6

**Ax table:** PurchTable

**Entity:** Purchase order headers V2

**Records:** 920

**Batch size:** 1000

**Cleanse:** None

**Owner:** Procurement

**Status:** Not started

**Totals:**

#### Total records

**Key:** records

**Agg:** sum

**Format:** integer

#### Total load batches

**Key:** batches

**Agg:** sum

**Format:** integer

**Summary:**

#### Average records per object

**Key:** avg_records

**Expr:** sum_records / count

**Format:** integer

**Notes:** Entity names are examples of standard D365 data entities; confirm names and versions in the Data management workspace of your environment. Load parents (accounts, parties) before dependent records.

## Content

**Intro:** Data migration from AX 2012 to Dynamics 365 Finance and Supply Chain goes wrong when load order and ownership are vague. This sheet lists each AX table, its D365 data entity, volumes and the person responsible.

**Sections:**

#### How to fill it in

**Body:** List each AX table you must migrate, then find the data entity in the D365 Data management workspace. Put load order in the first column so dependencies are visible: main accounts before journals, customers and vendors before orders, products before inventory. Enter record counts from AX with a count query on the table.

**Bullets:**

- Parents before children
- Count records per legal entity
- Mark heavy cleansing early
- Test load each entity at least twice

#### Batch sizing

**Body:** The sheet divides records by your chosen batch size to give a load batch count. Use it to estimate run time, not as a promise. Real throughput depends on entity complexity, change tracking and custom validation, so time a test load of one batch and scale from there.

#### Cleansing and ownership

**Body:** Customer and product masters usually need most of the cleansing: duplicates, inactive records, inconsistent units of measure. Give each object a business owner, not only an IT owner, because only the business can decide which records to drop.

**Cta:** If you want AX tables, row counts and custom fields extracted into this layout automatically, we can discuss tooling for it.

**Faq:**

#### Where do I find D365 data entities?

**Answer:** In the Data management workspace, open the Data entities tile. It lists entity names, target tables and whether the entity supports data management import.

#### Do I migrate history?

**Answer:** Often only open items and summarised balances move, with history archived. Decide this per object, since transaction history multiplies volume and testing effort.

#### What about custom AX fields?

**Answer:** Custom fields need to exist in D365 as extensions before load, and the entity must be extended to expose them. Track them as separate rows.

#### How many test loads are enough?

**Answer:** Plan at least two full rehearsals before cutover. The first finds mapping errors, the second proves timing and reconciliation.

## Search terms

ax 2012 to d365 data migration mapping, d365 data entities list for migration, ax 2012 data migration template excel, d365 data management entity mapping, ax2012 custtable d365 customers v3, dynamics ax data migration plan

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