Moving from NetSuite to Business Central: a migration without lost history

What a NetSuite to Business Central migration involves

Both products are cloud ERPs for growing companies. However, they organize data in different ways. NetSuite uses subsidiaries inside one account. It adds departments, classes and locations as segments. Business Central uses separate companies inside an environment. It uses dimensions for analysis and locations for stock. The words differ too.

So the first task of a NetSuite to Business Central migration is translation, not transfer. We map each NetSuite record type to its Business Central match. We also examine each custom piece. A SuiteScript, workflow or custom record may map to a standard feature. It may need an add-on or an AL extension. Or it may not be needed at all.

When the move makes sense

Companies consider the switch for different reasons. Some already run Microsoft 365, Teams and Power BI. They want their ERP to work with those tools. Some were bought by a group that standardized on Dynamics. Others are rethinking their systems at a contract renewal. Each is a fair reason, and each leads to a different plan.

However, it is not the right move for everyone. NetSuite is a capable product. If you lean on one of its built-in features, compare with care. Our comparison page sets out where each product fits. And we say so plainly when staying put is the sensible choice.

How we run the migration from NetSuite to Business Central

Microsoft's cloud migration tool is built for Dynamics GP and NAV, not for NetSuite. So data moves by extract and load. We export from NetSuite with saved searches and CSV files. We clean and reshape the data. Finally, we import it with configuration packages and journals in Business Central.

First, master data goes in. That means the chart of accounts, customers, vendors, items and bills of material. Next, open items follow. These are unpaid invoices, open orders and stock on hand at cost. We normally bring ledger history in as period balances by account and dimension. That keeps comparative reports intact.

What you receive at cutover

You receive a configured Business Central environment with your companies. You also get a mapping workbook that shows where every NetSuite field went. Reconciliation sheets prove that receivables, payables, stock value and the trial balance match on the cutover date. Finance signs them off.

We run at least one full trial migration in a sandbox before the real one. Your users test their daily work on that copy. We also agree how you will reach older NetSuite detail afterward. That is typically an export archive, since read access ends when the subscription does.

Pitfalls specific to leaving NetSuite

Intercompany and consolidation logic needs early attention. NetSuite handles multi-subsidiary eliminations inside one account. In Business Central, intercompany postings and a consolidation company do the same job. We settle that design before balances load. It shapes the chart of accounts, the dimensions and the opening entries.

Also, scripts are the hidden work. Many NetSuite accounts hold automation written long ago. Staff no longer notice it. Examples are a field that fills itself or an email that sends on approval. We list every script and workflow at the start. So nothing quietly disappears on the first day in the new system.

NetSuite to Business Central migration questions

Is there an automatic tool for a NetSuite to Business Central migration?

Not from Microsoft. The built-in cloud migration tool supports Dynamics GP and NAV sources. We export NetSuite data to files. Then we load it with configuration packages and journals. For large volumes, we use API-based imports. Some third-party tools exist and can help with extraction. We pick the route that fits your data size and your plan.

How much transaction history should we bring across?

Most companies load open items in detail. They load ledger history as period balances. Then they keep an archive of NetSuite exports for older detail. Loading every past document is possible. But it is rarely worth the effort and the clutter it creates. We agree the line with your controller and your outside accountant before we map any data.

What happens to our NetSuite customizations?

We assess each one. Standard Business Central features or personalization cover many of them. An existing add-on meets others. We rebuild the rest as AL extensions. A fair number turn out to be unused. We simply retire those. You get a written list that shows the outcome for every script, workflow and custom record.

How do NetSuite subsidiaries map to Business Central?

Each legal entity normally becomes a company in the same Business Central environment. They share one set of user licenses. Intercompany features handle trade between them. A consolidation company combines their results for group reporting, with currency translation where needed. We design this structure before any balances load, so the books tie out from day one.

Can we move at any point in the financial period?

You can. A period boundary is easier. Balances are clean, and auditors see a clear line. We plan the cutover date with your finance team. Then we work backward to schedule trial migrations and user testing. A NetSuite to Business Central migration runs best when everyone knows the date early.

Related migration pages

Leaving NetSuite raises questions about data, structure and fit. These pages compare the two products. They also explain data migration, multi-company design and the general migration approach our consultants follow. Read them next if your NetSuite to Business Central migration needs a closer look at any of those areas. For the product detail, see Business Central documentation on Microsoft Learn.