Designs the end-to-end migration programme for a NetSuite-origin organisation. Covers the legal-entity re-architecture that makes the transition a genuine re-design rather than a data lift, the eight-wave data migration sequence, the critical release-cadence ownership gap (NetSuite upgrades itself; D365 does not), how to convert saved-search logic into D365 reporting requirements, Power Platform admin center (PPAC) environment and sandbox strategy, and a realistic role-by-role reskilling plan for NetSuite administrators, SuiteScript developers, and NetSuite accountants.
A NetSuite-to-D365 migration is the most architectural of any ERP transition a mid-market organisation undertakes. Unlike an on-premises-to-cloud lift, or an ERP-to-ERP swap of comparable design philosophy, this transition involves two fundamentally different data models: NetSuite's single-database, multi-subsidiary tenant and D365's…
In NetSuite OneWorld, Subsidiaries are a filter in a single database. A transaction line is tagged with a Subsidiary and a set of Classification Segments (Class, Department, Location). Cross-subsidiary reporting is a saved search with no subsidiary filter. Intercompany eliminations are handled by Elimination Subsidiaries.
The transition programme for a NetSuite-origin organisation follows seven stages, each with gated outputs:
Data migration follows a strict dependency order. Loading in the wrong sequence produces foreign-key violations, missing account references, and failed journals:
This is the most underestimated risk for NetSuite-origin organisations and deserves explicit programme attention.
NetSuite customers commonly have 300–1,500 active Saved Searches. These searches are the analytical backbone of the business: they drive dashboards, scheduled exports, inline sublists, and ad-hoc queries. They are also a goldmine of undocumented reporting requirements.
NetSuite uses a single sandbox account (a copy of production) for development and testing. D365 uses a tier-based environment model managed through the Power Platform admin center (PPAC), which is replacing Lifecycle Services (LCS) as the control plane:
Three NetSuite roles require structured reskilling — not just product training, but mindset shifts:
The transition from NetSuite OneWorld to D365 is a genuine legal-entity re-architecture, not a data copy; the subsidiary-to-legal-entity design decisions made in Discover and Decide drive every downstream configuration and migration choice. The eight data migration waves must run in strict dependency order;