+1 480 485 7373%22 d=%22M10.913 53.581h109.15c6.028 0 10.914 4.886 10.914 10.913v109.151c0 6.027-4.886 10.913-10.913 10.913H10.913C4.886 184.558 0 179.672 0 173.645V64.495C0 58.466 4.886 53.58 10.913 53.58%22%3E%3C/path%3E%3Cpath fill=%22%23fff%22 d=%22M94.208 95.125h-21.82v59.416H58.487V95.125H36.769V83.599h57.439z%22%3E%3C/path%3E%3C/svg%3E)
Microsoft Teams
NetSuite to Business Central migration, subsidiary by subsidiary.
A NetSuite to Business Central migration is mostly a job of finding out what your NetSuite account really holds. Years of custom fields, custom records, saved searches, SuiteScript and SuiteFlow workflows sit on top of the standard records. Many of them run business rules nobody wrote down. Once you have that list, mapping it into Business Central companies, dimensions and extensions is plain work.
What to catalog inside NetSuite first
Subsidiaries
Each OneWorld subsidiary with its base currency, tax nexus and parent. Also add any elimination subsidiaries used to roll up the group.
Classes, departments, locations
The standard segments and their levels. Then note which ones are required on each type of transaction.
Custom segments and fields
Custom segments, entity fields, item fields, and body and column fields on transactions. Also note how often users fill in each one.
Custom records
Custom record types and what created them. Check whether any transaction or script depends on them.
Saved searches
Which saved searches drive dashboards, emails or exports. In addition, mark which are one-off lookups nobody opens.
SuiteScript
User event, scheduled, client and map/reduce scripts. Then write down the business rule each one enforces in plain English.
SuiteFlow workflows
Approval routing, field defaults and state changes set in workflows, not code.
SuiteApps and integrations
Installed bundles, plus ecommerce, payment, tax and shipping links. Finally, list every system that calls SuiteTalk or RESTlets.
NetSuite records translated for Business Central
Saved searches, SuiteScript and SuiteFlow: rebuild on purpose
Nothing written in SuiteScript runs in Business Central. Therefore, translating scripts line by line only makes the same tangle in a new language. So we start from the business rule each script enforces. Instead, Business Central does many of them as standard. Credit limit checks, for example, are one. Required dimensions, approval before release and auto numbering are others. We then write the rules that remain as AL extensions. These install on your tenant and survive Microsoft's updates. When the logic is really a notice or a hand-off between people, we use Power Automate flows instead.
Similarly, SuiteFlow workflows map the same way. Business Central has standard approval templates for purchase orders, vendor bills and journals. They can route by amount, dimension or requester. Meanwhile, field defaults move to customer and item templates.
Saved searches split into three groups. Lookups become filtered list views, which any user can save. Searches for analysis get rebuilt in analysis mode or in Power BI. Searches that feed exports to other systems become API queries or timed Power Automate exports. Role centers with cues and Power BI tiles replace dashboards built from saved search portlets.
Which NetSuite transactions come across
Per subsidiary trial balance
Each subsidiary's trial balance posts at cutover into the matching Business Central company. It posts by account and dimension, in that subsidiary's base currency.
- ✓Balance sheet at closing balances
- ✓Year-to-date income statement by month if mid-year
- ✓Intercompany balances agreed between subsidiaries first
Documents still in progress
Anything unfinished comes across as a live document. Your team then completes it as normal in Business Central.
- ✓Open invoices and credit memos with original currency and due dates
- ✓Open vendor bills and unapplied payments
- ✓Open sales orders not yet shipped and purchase orders not yet received
- ✓Item receipts not yet billed, loaded to a receipts-not-invoiced account
What stays archived
We export closed transactions, system notes and attachments to storage you control. We can also load summed prior-year figures for comparison reports.
- ✓Full CSV and saved search exports kept as the audit record
- ✓File cabinet documents downloaded before access ends
- ✓Summed prior-year figures where reports need them
Sequencing the switch around your NetSuite contract
- 1
Check the contract end date
Access to NetSuite ends with the subscription. So the last rehearsal, the final extract and the archive must all fit before that date.
- 2
Extract with repeatable exports
Build saved searches or SuiteAnalytics exports for every entity and open-item set. The same extract then runs for each rehearsal and for the final cutover.
- 3
Rehearse in a sandbox
Load a full trial NetSuite to Business Central migration into a sandbox and check every balance. Fix the mapping until the numbers tie with no manual edits.
- 4
Switch integrations
On cutover day, point ecommerce, tax, shipping and payment links at Business Central. Hold orders in the gap.
- 5
Run the first close on both sides
Close the first Business Central month and compare key balances to where NetSuite would have been. Then sign off the archive.
NetSuite departures: common questions
Why do companies move from NetSuite to Business Central?
Most move for fit with Microsoft 365 or for licensing they can plan around. Others leave because heavy custom work has made NetSuite hard to change. Business Central sits inside the Microsoft stack alongside Excel, Teams, Outlook and Power BI. Its extension model keeps custom code apart from the base product, so upgrades are easy to predict. It is not the right move for every NetSuite customer. We compare both honestly on a first call.
Can a tool convert our SuiteScript code for us?
No. No tool converts SuiteScript on its own, and none should. JavaScript written for NetSuite records means nothing in Business Central. It uses AL and a different data model. We write down the business rule behind each script and check whether Business Central does it as standard. Then we build only what is left as an extension. Most accounts need far less custom code afterwards than they had before.
What happens to our saved searches and dashboards?
We rebuild them as filtered list views, analysis mode views, financial reports or Power BI reports, based on each one's job. First we find out which searches people still open, since many accounts carry hundreds nobody uses. Searches that feed other systems become API queries. Role centers give each user a start page with the counts and tiles they check daily.
More NetSuite to Business Central migration questions
Can Business Central run many subsidiaries like OneWorld?
Yes. You run several companies in one environment. Intercompany postings link them. A consolidation company rolls them up. Each subsidiary keeps its own base currency, chart of accounts and tax setup. Intercompany sales and purchases can create the matching document in the partner company on their own. That company translates foreign subsidiaries and posts the eliminations.
Do we move every NetSuite transaction since we started?
No. We advise moving open items and balances, with summed history only where reports need it. Loading every closed transaction adds cost and risk without helping daily work. We export and archive the full detail for audit and lookup. Monthly totals fill the past-year columns in your reports.
Talk to us about your project.
Tell us what you run today and what has to change. A senior consultant replies with a written next step.