How AX 2012's companies, DataAreaId, partitions, virtual companies, organisation hierarchies, operating units, sites and warehouses map onto D365 — and why devirtualisation is mandatory pre-upgrade remediation with real business consequences.
What you will be able to do
Explain why DataAreaId is the one organisational field that maps with zero change
Describe the AX 2012 partition model and articulate why partitions are not an upgrade target
Evaluate the three devirtualisation options for virtual companies and select the appropriate one
Map organisation hierarchies, operating units, departments, cost centres, business units and value streams to their D365 equivalents
Distinguish where AX organisational constructs are identity-mapped from where they must be re-projected
Introduction
The Conceptual Foundations chapter established that AX 2012 and D365 F&O share a lineage, and that the programme's effort sits almost entirely on code and platform surfaces rather than data translation.
Companies and DataAreaId: the identity-mapped root
The company account in AX 2012 is the root organisational node — the statutory financial-reporting boundary. Every company-scoped table row carries a DataAreaId column discriminating which legal entity owns the data. This column, and the CompanyInfo table behind it, is the same field in D365.
The partition model: why partitions are not an upgrade target
AX 2012 introduced data partitions to isolate independent datasets within a single AX instance. A partition creates a logical boundary: users log into a specific partition and see only the companies, master data, and configuration within it.
Virtual companies and devirtualisation
Virtual companies are AX 2012's mechanism for sharing reference and master data across company boundaries. A virtual company account is created (for example, VIR), table collections are assigned to it (for example, PaymTerm, TaxGroupHeading, DlvMode), and multiple real companies are linked to that virtual company.
Organisation hierarchies and purposes
AX 2012 uses organisation hierarchies to model reporting relationships, budget control, centralised purchasing, and other structured relationships between organisational units. Each hierarchy is assigned one or more purposes (for example, Reporting, Security, Centralised purchasing, Retail assortment).
Operating units: departments, cost centres, business units, value streams
AX 2012 defines several types of operating unit, all backed by the OMOperatingUnit table:
Sites and warehouses
Sites (InventSite) and warehouses (InventLocation) are the logistical building blocks beneath the legal entity. Both tables carry forward with the same name, same key structure, and same semantics.
Where identity-mapping stops and re-projection begins
The following table summarises the full organisation-model scope, flagging where the mapping is genuinely direct and where work is required:
Knowledge check
Summary
The AX 2012 organisation model is the area of the programme where same-lineage identity mapping is most visible and most valuable. Companies, hierarchies, operating units, sites, and warehouses carry forward with the same tables, the same keys, and the same semantics. This is not a projection exercise — it is a validation exercise.