How NetSuite's Subsidiary hierarchy, OneWorld intercompany rules, and Class / Department / Location segments translate into D365 legal entities, consolidation companies, operating units and financial dimensions — and why every collapse and split is a business decision with reporting consequences.
NetSuite's organisational model is deceptively simple. In a single-Subsidiary tenant, the entire ERP runs inside one entity with no boundaries. Add OneWorld and the model scales gracefully: each Subsidiary has its own base currency, its own default account ranges, its own period-close status and its own intercompany relationships to…
The mapping from NetSuite Subsidiary to D365 legal entity is the starting point for everything else in the programme.
NetSuite carries three built-in analytical segments on every transaction — Class, Department and Location — plus any number of Custom Segments. In D365 F&O the equivalent is the financial dimension: a named, configured dimension whose values can be set at the transaction header or line level, defaulted from master records, or derived…
NetSuite's Location segment serves two conceptually distinct purposes. In some tenants it is purely analytical — tagging transactions with the organisational unit that owns them. In other tenants it also represents a physical facility where inventory is stored, shipped from or received at.
One of the most significant operational differences between the two systems is how they handle the boundary between entities.
A NetSuite practitioner can understand the target design faster if the core D365 constructs are separated before they are combined. These five concepts are the ones the migration engine consumes on almost every record family.
NetSuite's Subsidiary hierarchy and segment model translate cleanly to D365 legal entities and financial dimensions — once the right business decisions have been made.