Migrating from NetSuite to Business Central
By Emil Björk · Microsoft business apps consultant, Gothenburg
Moving from NetSuite to Business Central — the data and customisation challenges, the cost angle, and what to expect from the project.
On this page (8)
NetSuite-to-Business-Central migrations are not as common as QuickBooks or SAP B1 migrations, but they do happen — typically driven by cost (NetSuite per-user pricing scales aggressively), by Microsoft 365 integration preferences, or by partner ecosystem in specific countries. The migration is doable but not trivial; both products are real ERPs and the data and customisation footprints are usually substantial.
Why customers consider it
Common triggers:
- Total cost of ownership. NetSuite list pricing tends to escalate as user count and module footprint grow. Business Central licence costs are usually meaningfully lower for the same headcount.
- Microsoft 365 alignment. Customers heavily invested in Microsoft 365 (Teams, SharePoint, Power BI) often find BC's tighter integration more productive than NetSuite's connectors.
- Partner ecosystem. In some markets (DACH, Nordics, parts of Asia), the Microsoft partner base is broader and more accessible than the NetSuite consulting base.
Why customers stay on NetSuite
Equally common: deep customisation already in place, industry-specific NetSuite modules (SuiteCommerce, advanced revenue management) without direct BC equivalents, or established global multi-entity consolidations.
Data migration
NetSuite exports cleanly via its SuiteAnalytics API or Saved Searches exports. Standard approach:
- Inventory the NetSuite data model — standard objects, custom records, custom fields.
- Map to BC equivalents — chart of accounts, dimensions (NetSuite classes, departments, locations map to BC dimensions), items, customers, vendors.
- Pull data via the API, transform with Azure Data Factory or Power Query, load to BC via Configuration Packages or REST API.
Open transactions, balances, and the master data migrate; historical detail typically stays in NetSuite read-only.
Customisation
NetSuite customisations live in SuiteScript (JavaScript), SuiteFlow, and SuiteBuilder. None of this ports directly. The rebuild path:
- Standard fields and forms → BC's table extensions and page extensions in AL.
- SuiteFlow workflows → BC's built-in workflows or Power Automate flows.
- SuiteScript business logic → AL codeunits with event subscribers.
- SuiteAnalytics reports → Power BI.
- SuiteCommerce e-commerce → typically Shopify, Sana, or a custom Power Pages + headless front end.
Many customisations turn out to be workarounds for NetSuite features BC implements differently — re-do the fit-gap honestly before committing to rebuild.
Multi-entity and consolidations
NetSuite OneWorld is strong at multi-subsidiary consolidations. BC's multi-company is real but less feature-rich. Customers running 20+ legal entities with complex consolidations should evaluate whether Dynamics 365 Finance is the right step rather than BC. For 5–15 entities with moderate complexity, BC is usually sufficient.
Integration rebuild
NetSuite's connector library is wide; BC's is wide too but the specific connectors differ. Audit every NetSuite integration and budget the rebuild.
Time to live
Substantial. Typical NetSuite-to-BC migrations are 6 to 18 months for a mid-sized customer, dominated by configuration, customisation rebuild, and parallel running.
Where to go next
The decision itself is Business Central vs NetSuite; running both during the move is integrating with NetSuite during migration. Design the target with dimensions design and multi-company setup — and if the entity count is high, read growing from Business Central to Finance and SCM before committing.
Frequently asked questions
Why do companies move from NetSuite to Business Central?
- Total cost of ownership as NetSuite per-user pricing escalates, tighter Microsoft 365 integration, and broader Microsoft partner coverage in markets such as DACH, the Nordics, and parts of Asia. Companies with deep SuiteScript customisation or SuiteCommerce dependencies often stay.
How does NetSuite data map to Business Central?
- Classes, departments, and locations become Business Central dimensions; the chart of accounts, items, customers, and vendors map directly. Data comes out through SuiteAnalytics or saved searches, is transformed in Data Factory or Power Query, and loads through configuration packages or the REST API. Historical detail usually stays in NetSuite read-only.
What happens to SuiteScript and SuiteFlow customisations?
- Nothing ports. SuiteScript logic becomes AL codeunits with event subscribers, SuiteFlow becomes BC workflows or Power Automate, SuiteAnalytics reports become Power BI, and SuiteCommerce is typically replaced by Shopify, Sana, or a headless front end.
Is Business Central the right target for a large NetSuite OneWorld group?
- For 5–15 entities with moderate consolidation complexity, yes. For 20+ legal entities with complex consolidations, evaluate Dynamics 365 Finance instead.
Further reading
Related guides
- Migrating from QuickBooks to Business CentralMoving from QuickBooks to Business Central — the data migration wizard, scope decisions, parallel running, and the gotchas that catch people out.
- Migrating from SAP Business One to Business CentralMoving from SAP Business One to Business Central — the practical mapping, data migration approach, and the choices that decide the project's complexity.
- Business Central vs Dynamics NAVWhat changed in the move from Dynamics NAV to Business Central, and what that means for organisations still running NAV.
- Business Central vs Finance and OperationsWhen Business Central is the right ERP, when you've outgrown it, and how the move to Dynamics 365 Finance and Supply Chain Management actually goes.
- Growing from Business Central to Finance and SCMWhen and how to move from Business Central up to Dynamics 365 Finance and Supply Chain Management — signals, scope, and the migration path.
Browse every guide in Migrations.
Was this helpful?
Signals which guides land and which need work. No account, no comment box — corrections go through the contact page.
Spot something wrong or want a topic covered? Send a correction or a topic request — both are welcome.