AX 2012 to D365 Data Entity Mapping Worksheet
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.
| Load order | AX 2012 table | D365 data entity | Records | Records per load batch | Load batches | Cleansing needed | Owner | Status | |
|---|---|---|---|---|---|---|---|---|---|
2 | |||||||||
5 | |||||||||
2 | |||||||||
9 | |||||||||
2 | |||||||||
1 |
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.
AX data profiling
Optional: ask us about profiling AX data volume and quality before you commit to scope.
Optional. The tool and every export work without this. No spam.
How to fill it in
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.
- Parents before children
- Count records per legal entity
- Mark heavy cleansing early
- Test load each entity at least twice
Batch sizing
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
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.
Frequently Asked Questions
Where do I find D365 data entities?
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?
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?
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?
Plan at least two full rehearsals before cutover. The first finds mapping errors, the second proves timing and reconciliation.
If you want AX tables, row counts and custom fields extracted into this layout automatically, we can discuss tooling for it.
Related Tools
Dynamics AX 2012 Retirement Project Charter Template
A one-to-two page charter for getting executive approval to retire or replace Dynamics AX 2012, with scope, drivers, risks and sign-offs.
Microsoft DynamicsGP Cutover Open Balances Reconciliation Worksheet
Compare GP and target-system balances for AR, AP, inventory, GL and open orders, calculate variance and track who signed off each line.
Microsoft DynamicsGP and AX User Role to Business Central Permission Mapping Worksheet
List each legacy security role, the tasks it covers, how many users hold it and the target permission set, with a segregation-of-duties check.
Microsoft DynamicsGP to Business Central Cutover Runbook Template
A fill-in cutover runbook for moving a Dynamics GP company to Business Central: freeze window, final extracts, opening balances, go/no-go and rollback.
More Microsoft Dynamics tools
See all- AX 2012 to D365 Finance and Operations Upgrade Effort Estimator
- Dynamics AX Customization Inventory Worksheet
- AX 2012 Customization Remediation Effort Calculator
- 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