---
title: "NetSuite to Business Central Migration | FlitStack AI"
description: "Migrate NetSuite to Business Central with FlitStack AI: field-level mapping, a sample run you approve, full history and one-click rollback."
url: "https://flitstack.ai/migrations/erp/netsuite/to/microsoft-dynamics-365-business-central"
---

# NetSuite to Business Central migration

We migrate Chart of Accounts, Customers, Vendors, Items, and historical Transactions from NetSuite into Microsoft Dynamics 365 Business Central or Finance and Operations, resolving the subsidiary-to-company structural split, preserving journal posting dates and exchange rates, and mapping NetSuite's custom field registry to Dynamics extensions before cutover.

Short answer

FlitStack AI migrates chart of master datas, companies, customers, vendors and items from NetSuite to Business Central, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 6-10 weeks.

![](https://flitstack.ai/images/authors/aditya-kumar.webp)By [Aditya Kumar](https://flitstack.ai/about/aditya-kumar) Updated November 5, 2026

[Get a quote ](https://flitstack.ai/contact) [See what moves →](https://flitstack.ai/migrations/erp/netsuite/to/microsoft-dynamics-365-business-central#what-moves)

![](https://flitstack.ai/images/illustrations/pair-stage.webp)

Source NetSuite ![](https://flitstack.ai/platforms-trim/netsuite.webp)

Destination Business Central ![](https://flitstack.ai/platforms-trim/microsoft-dynamics-365-business-central.webp)

Chart of Master Data Company Customer Vendor Item

Mapped field by field · sample run · one-click rollback

## What moves from NetSuite to Business Central?

Moving from NetSuite to Microsoft Dynamics 365 is a structural migration, not a record copy.

Read the full summary

NetSuite's unified multi-entity database represents subsidiaries as intra-account entities with native intercompany eliminations; Dynamics 365 requires a separate Company database per legal entity with explicit posting group configuration. We resolve that split during discovery, map each NetSuite subsidiary to a distinct Dynamics 365 Company with mandatory VAT or posting groups, and sequence open AR/AP as fresh journal entries rather than historical invoice replay. Custom fields (custbody\_\*, custrecord\_\*, custentity\_\*) are discovered via SuiteQL against the NetSuite metadata endpoint and mapped to Dynamics extension fields before migration. Historical journal entries require either prior-period balance carry-forward or full replay with original exchange rates preserved. SuiteBuilder workflows and SuiteScripts do not migrate; we deliver a written inventory of every active automation for your Dynamics partner or admin to rebuild in Power Automate or AL-based workflows post-migration.

1:1

### Chart of Accounts (Accounts) → Chart of Master Data (G/L Account)

NetSuite Accounts (account type codes 0-24: Bank, AR, Inventory, Fixed Assets, AP, Income, COGS, Expense) map to Dynamics G/L Entries.

How it maps

NetSuite account numbers (acctNumber) become Dynamics G/L Account numbers; account names become posted descriptions. Exchange gains/losses accounts require separate mapping for currency revaluation rows. We validate that Dynamics posting groups are assigned for each account before import to avoid rejection at first posting.

1:N split

### Subsidiary → Company (Legal Entity)

NetSuite's subsidiary model is the central complexity in this migration.

How it maps

One NetSuite account with N subsidiaries must split into N separate Dynamics 365 Companies (each a legal entity with its own fiscal calendar, VAT registration, and chart of accounts). Each subsidiary maps to a distinct Company with mandatory Business Central posting groups or F\&O legal entities. Intercompany accounts in NetSuite (elimination subsidiaries) require explicit Dynamics intercompany posting group configuration during setup. The subsidiary-to-company map is built during discovery and validated against the destination's legal entity requirements before any transaction data moves.

1:1

### Customer → Customer

NetSuite Customers map to Dynamics Customers with address, contact, payment terms, and tax registration fields preserved.

How it maps

Customer currency assignments in NetSuite become Dynamics Customer posting groups. Credit limits migrate as-is but require reconfiguration of Dynamics credit management workflows. Customer-specific pricing matrices map to Dynamics Customer Price Groups if the customer uses tiered or volume pricing.

1:1

### Vendor → Vendor

NetSuite Vendors map to Dynamics Vendors with the same address, contact, and payment term fields.

How it maps

Tax ID and VAT registration from NetSuite become Dynamics Tax Registration numbers. 1099 vendor flags migrate to the corresponding Dynamics tax document settings. Vendor-specific discounts require mapping to Vendor Price Groups in Dynamics.

1:1

### Item (Inventory Assembly, Non-Inventory, Service, Description) → Item (Inventory Item, Service Item, Non-Stock Item)

NetSuite item types (Inventory Assembly, Non-Inventory, Service, Description Only) map directly to Dynamics item types.

How it maps

BOM/assembly relationships in NetSuite become Dynamics bill of materials entries. Lot/serial number tracking, location assignments, and landed cost fields migrate to Dynamics warehouse configuration. Pricing matrices become Dynamics Sales Prices linked to Customer Price Groups. We resolve the item-company relationship (multi-subsidiary items must be created per Dynamics legal entity).

mapping

### Sales Order / Invoice → Sales Order / Sales Invoice

Open NetSuite Sales Orders migrate as Dynamics Sales Orders with the original order date and customer price group preserved.

How it maps

Closed or fulfilled orders migrate as Sales Invoices for AR aging purposes. Invoice PDFs attach as document attachments. Historical paid invoices do not migrate as closed records; the customer's choice (carry forward open AR only, or replay full history) determines whether we create posted Sales Invoice records or carry-forward balance journal entries.

******What moves 18 objects

NetSuite Business Central

- Chart of Accounts Chart of Master Data 1:1
- Subsidiary Company split
- Customer Customer 1:1
- Vendor Vendor 1:1
- Item Item 1:1
- Sales Order Sales Order transformed

\+ 12 more in the mapping below

## How NetSuite and Business Central differ

The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.

| Dimension                  | NetSuite                                                                                         | Business Central                                                                                                                           |
| -------------------------- | ------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------ |
| Architecture model         | Multi-tenant cloud-native, one database with intra-account subsidiaries                          | Separate Company database per legal entity; intercompany requires explicit posting groups or consolidation tools                           |
| Multi-entity consolidation | NetSuite OneWorld: intercompany eliminations natively within one account                         | Business Central: consolidation via Consolidation Management; F\&O: up to 40 legal entities per partition with intercompany posting groups |
| Custom field model         | custbody\_\*, custcol\_\*, custentity\_\*, custrecord\_\* prefix registry discovered via SuiteQL | AL extension fields added to table extensions; requires developer environment or partner involvement to provision                          |
| Transaction naming         | Sales Order, Vendor Bill, Journal Entry, Inventory Transfer                                      | Sales Document, Purchase Invoice, General Journal, Warehouse Shipment (different terminology throughout)                                   |
| Automation engine          | SuiteBuilder workflows + SuiteScript 2.x (SOAP/REST)                                             | Power Automate (cloud) + AL-based workflows (on-prem); no direct migration path                                                            |
| E-invoicing maturity       | Immature; requires external portals or workarounds per jurisdiction                              | PEPPOL-ready in EU; Electronic Document Service in F\&O; localization varies by country/region                                             |
| Update cadence             | Automatic biannual updates; all customers on same version                                        | Microsoft-managed releases twice yearly; optional early access; extension compatibility must be validated                                  |
| API rate limits            | 15-55 concurrent requests depending on SuiteCloud Plus licenses and service tier                 | Business Central: OData throttle \~2,000 requests/min per app; F\&O: Data Management Framework with batch sizing controls                  |

## What to watch for in a NetSuite to Business Central migration

The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.

high

### Subsidiary-to-company split is structural, not cosmetic

NetSuite OneWorld lets one account represent multiple legal entities with native intercompany eliminations and consolidated reporting without separate databases.

How we handle it

Dynamics 365 requires a separate Company (Business Central) or legal entity (F\&O) per legal entity. Each NetSuite subsidiary must map to a distinct Dynamics company with its own fiscal calendar, posting groups, and VAT registration. Intercompany accounts in NetSuite require explicit Dynamics intercompany posting group configuration. Getting the subsidiary-to-company map wrong causes posting rejections at import time. We build and validate this map during discovery before any transaction data moves.

high

### NetSuite SuiteQL rate limits gate extraction throughput

NetSuite enforces concurrent API request limits (15 for default tier, up to 55 with SuiteCloud Plus licenses).

How we handle it

Large extractions—particularly transaction history spanning multiple years with line-level detail—must be chunked by date ranges and record count. We monitor concurrency headers, implement exponential backoff, and batch to 1,000 records per request. If we exceed concurrency during extraction, NetSuite returns 429/403 errors. We scope each migration within the account's tier ceiling and flag early if the migration scope will approach the tier ceiling, requiring a temporary SuiteCloud Plus license or tier upgrade before proceeding.

high

### Historical journal entries require a carry-forward strategy before migration begins

NetSuite journals include prior-period adjustments, intercompany eliminations, and currency revaluation rows with original posting dates and exchange rates.

How we handle it

Two strategies exist: (1) Full replay: migrate each historical journal with its original posting date and exchange rate, preserving a complete audit trail; (2) Balance carry-forward: create a single opening-balance journal per subsidiary at the go-live date, carrying forward net balances rather than replaying history. The choice has significant downstream implications for period reporting, tax filing, and audit readiness. We present both options during discovery and capture the decision in the migration contract before sequencing begins.

medium

### NetSuite custom field registry is account-unique and not publicly documented

Every NetSuite environment has a unique set of custom record types and custom fields using custbody\_\*, custrecord\_\*, custentity\_\*, and custitem\_\* prefixes.

How we handle it

These cannot be discovered from public documentation; we must enumerate them via a metadata discovery pass against the account's SuiteQL endpoint before building the migration map. Custom fields on transaction lines (custcol\_\*) require special handling in SOAP/REST export payloads. If the account has SuiteScript workflows that write to these custom fields, the migration map must account for any transformation logic embedded in the script.

medium

### NetSuite workflows and scripts do not migrate to Dynamics Power Automate or AL

NetSuite SuiteBuilder workflows (visual workflow builder) and SuiteScript 2.x automations (SOAP/REST scripts) have no direct migration path to Dynamics Power Automate or AL-based workflows.

How we handle it

They are different automation models with different trigger types, action sets, and execution contexts. We do not migrate them as code. We deliver a written inventory of every active SuiteBuilder workflow and scheduled SuiteScript with its trigger, conditions, actions, and a recommended Dynamics equivalent. The customer's Dynamics partner or admin rebuilds them post-migration.

## How the migration runs

1. ### Discovery and migration strategy workshop

   We audit the NetSuite account across service tier (Standard through Ultimate), subsidiary count, custom record types, custom field registry, transaction history depth, SuiteBuilder workflow inventory, and SuiteScript count.

   What this step covers

   We pair this with a Dynamics 365 edition decision: Business Central (Essentials or Premium) for companies under \~200 users with straightforward multi-company structures; Finance and Operations for large enterprises with discrete or process manufacturing, advanced warehouse management, or 40+ legal entities. The discovery output is a written migration scope, subsidiary-to-company map draft, and a journal carry-forward strategy recommendation.

2. ### Custom field and custom record schema discovery

   We run a metadata discovery pass against the NetSuite account's SuiteQL endpoint to enumerate every active custom record type, custom field, and custom list.

   What this step covers

   We also extract the custom field usage matrix (which fields appear on which record types, including transaction line-level custcol\_\* fields). This discovery data drives the Dynamics AL extension schema creation in step 3. Without this step, custom fields are invisible to the migration map and either get dropped or require emergency post-discovery remediation.

3. ### Dynamics schema provisioning and subsidiary-to-company mapping validation

   We provision the Dynamics 365 environment with the target schema: Companies per subsidiary, G/L Account structure per company, Tax Groups, Item types, Customer and Vendor posting groups, and AL extension fields for every custom field discovered in step 2.

   What this step covers

   The subsidiary-to-company map is validated by a Dynamics-functional consultant before any data import. We run a sandbox migration (Full Copy or Partial Copy Sandbox in F\&O; Sandbox in Business Central) to validate the schema and posting group assignments against a representative data sample before production migration begins.

4. ### Master data migration in dependency order

   We migrate master data in strict dependency order: (1) G/L Accounts and fiscal calendars, (2) Tax codes and posting groups, (3) Items and price lists, (4) Customers and Vendors, (5) Employees (if HR in scope).

   What this step covers

   Each phase emits a row-count reconciliation report. Any NetSuite record with a missing required Dynamics field (e.g., a subsidiary that wasn't mapped to a Company) is held in a remediation queue and resolved before the next phase begins.

5. ### Transaction migration with journal carry-forward or full replay

   We migrate open AR and AP as ledger entries with original document dates and aging buckets.

   What this step covers

   Closed transactions follow the agreed carry-forward strategy. Journal entries are migrated either as full historical replay (with original posting dates and exchange rates) or as opening-balance carry-forward entries per subsidiary, depending on the strategy selected in discovery. Transaction migration uses the Dynamics OData v4 API (Business Central) or Data Management Framework (F\&O) with batch sizing tuned to avoid throttling. We monitor API responses and apply exponential backoff if throttling headers appear.

6. ### Custom record and custom field migration

   After master data and transactions are validated, we migrate custom record types (NetSuite Custom Records to Dynamics extension tables) and custom field values (attached to standard objects as AL extension fields).

   What this step covers

   Custom record lookups are resolved at migration time by matching NetSuite internalId references to the Dynamics GUIDs of the imported parent records. We validate custom field completeness by comparing record counts between source and destination for each custom record type.

7. ### Cutover, delta migration, and automation rebuild handoff

   We freeze NetSuite writes during the cutover window, run a final delta migration of any records modified during the migration period, then enable Dynamics 365 as the system of record.

   What this step covers

   We deliver the SuiteBuilder Workflow and SuiteScript inventory document to the customer's admin and Dynamics partner. We provide a two-week hypercare window to resolve reconciliation issues. We do not rebuild NetSuite automations as Power Automate or AL workflows inside the migration scope; that is a separate engagement.

![](https://flitstack.ai/platforms/netsuite.svg) NetSuite ![](https://flitstack.ai/platforms/microsoft-dynamics-365-business-central.svg) Business Central

1. Connect
2. Map
3. Sample
4. Migrate
5. Verify

- **Contacts** 48,210 / 48,210 Done
- **Companies** 9,134 / 9,134 Done
- **Deals** 6,377 / 11,920 In progress

Example run

******Restore points · Business Central Rollback ready

1. Before sample run Restore point 01 Restore
2. Before full migration Restore point 02 Restore
3. After verification Restore point 03 Current

Example

## How long it takes, and what drives the quote

**6-10 weeks** Typical, smaller accounts

**14-24 weeks** Large or heavily customised accounts

A quote scales with subsidiary count, custom field registry size, transaction history depth, and journal carry-forward strategy. Every quote is scoped with you; there is no self-serve pricing.

[Get a quote for NetSuite to Business Central →](https://flitstack.ai/contact)

## Why teams move from NetSuite to Business Central

- NetSuite renewal pricing has become a consistent pain point. Reddit threads in r/Netsuite document double-digit uplift percentages at renewal, no downgrade path, and edition upgrades triggered by user or transaction growth that lock in higher tiers without warning. Dynamics 365 Business Central undercuts NetSuite by 20-30 percent in the first fifty users with predictable per-user pricing, making the subscription economics more transparent for finance teams managing annual budgets.
- Companies already running Microsoft 365, Teams, Azure, and Power BI choose Dynamics 365 because the native integration layer is deeper than what NetSuite can offer without middleware. Excel workflows for finance teams, Power BI for reporting, and Azure Active Directory for identity management connect without third-party iPaaS tools, reducing the total integration cost of ownership.
- NetSuite's HelpDesk module is widely described as inadequate for serious customer service operations. Organizations requiring a dedicated ticketing platform with SLA tracking, case routing, and knowledge base capabilities move to Dynamics 365 Customer Service or Field Service, which integrate natively with the ERP layer without the integration overhead that NetSuite's HelpDesk requires.
- NetSuite's single-codebase multi-tenant architecture, while reliable for updates, limits customization flexibility and can produce page load times of 30-60 seconds for routine transactions. Dynamics 365 Finance and Operations supports richer manufacturing (discrete and process), field service, and warehouse management capabilities that mid-market companies with complex supply chain operations find more suitable at comparable price points.
- NetSuite's e-invoicing capabilities require external portals or third-party workarounds in many jurisdictions, frustrating finance teams that need PEPPOL-compliant electronic document delivery. Dynamics 365 Finance and Operations ships with Electronic Document Service and PEPPOL support for EU jurisdictions, and Business Central supports localization packs across 40+ countries, reducing compliance engineering overhead.

Questions, answered

## NetSuite to Business Central migration questions

How long does a NetSuite to Microsoft Dynamics 365 migration take?

Migrations with 1-3 subsidiaries, under 50 custom fields, and balance-carry-forward open periods land between six and ten weeks. Migrations with 4+ subsidiaries (each requiring a separate Dynamics Company), a large custom record schema, full historical journal replay, or multi-currency complexity across multiple fiscal years move to fourteen to twenty-four weeks. The journal carry-forward strategy decision (full replay vs. balance forward) is the single largest timeline variable because full replay requires sequencing every historical row with its original exchange rates.

Do NetSuite SuiteBuilder workflows and SuiteScripts migrate to Dynamics Power Automate?

No. SuiteBuilder workflows and SuiteScript 2.x automations are architecturally incompatible with Dynamics 365's automation model. We do not migrate them as code. We deliver a written inventory of every active workflow and scheduled script with its trigger, conditions, actions, and a recommended Dynamics Power Automate or AL equivalent. Your Dynamics partner or admin rebuilds them post-migration. This inventory is included in standard migration deliverables.

How do we handle NetSuite OneWorld subsidiaries in Dynamics 365?

NetSuite OneWorld subsidiaries do not map to a single Dynamics 365 entity. Each NetSuite subsidiary must become a separate Dynamics 365 Company (Business Central) or legal entity (F\&O) with its own chart of accounts, fiscal calendar, and VAT/tax registration. Intercompany accounts in NetSuite require explicit Dynamics intercompany posting group configuration. We build the subsidiary-to-company map during discovery, validate it in a sandbox migration, and apply it to production migration. This is the highest-risk structural decision in the migration and must be resolved before any transaction data moves.

Can we keep NetSuite for some entities while moving others to Dynamics 365?

A split-platform configuration is technically possible but introduces reconciliation complexity and is not recommended as a long-term architecture. If the customer's timeline requires a phased approach (moving one subsidiary first, others later), we can scope the migration to a subset of subsidiaries and leave the remainder in NetSuite with an intercompany bridge planned for a later phase. The subsidiary-to-company map is built for the full scope even if only Phase 1 migrates, to avoid structural rework in Phase 2.

Do we lose historical journal entries during migration?

No data is lost. We offer two strategies: (1) Full replay: every NetSuite journal entry migrates with its original posting date, exchange rate, and line-level detail, preserving a complete audit trail. This is the more time-intensive path. (2) Balance carry-forward: we create opening-balance journal entries per subsidiary at the go-live date, carrying forward net balances rather than replaying each historical row. This is faster but sacrifices the period-by-period audit trail. We present both strategies during discovery and capture the decision in the migration contract before sequencing begins.

How does NetSuite's API rate limiting affect migration timeline?

NetSuite enforces concurrent API request limits (15 per default account, up to 55 with SuiteCloud Plus licenses on Tier 5). Large transaction history extractions must be chunked by date range and record count to avoid 429/403 errors. We implement exponential backoff, batch to 1,000 records per request, and monitor concurrency headers throughout extraction. If the migration scope approaches the tier ceiling, we flag this early and recommend a temporary SuiteCloud Plus license addition or tier upgrade before proceeding, so that the account's tier ceiling does not become a migration blocker mid-flight.

Can FlitStack AI migrate NetSuite SuiteProjects Pro project data to Dynamics Projects?

Yes. NetSuite SuiteProjects Pro records (project billing, time entries, resource allocations, milestones, and project financials) migrate to Dynamics 365 Project Service Automation or Business Central Projects depending on the destination edition. Project financial transactions are separated from standard G/L transactions and mapped to the appropriate project dimensions. Time entries migrate as project journal lines with original dates preserved. Fixed-price project milestones map to Dynamics contract lines with billing schedules. We do not migrate PSA resource planning as code; the resource management and capacity planning setup is configured by the customer's Dynamics functional consultant post-migration.

## Related migrations

[![](https://flitstack.ai/platforms-trim/microsoft-dynamics-365-business-central.webp) Migrate to **Business Central** Every source we move into Business Central, native options and the checklist. Guide, checklist & sources ](https://flitstack.ai/migrations/erp/microsoft-dynamics-365-business-central) [**ERPNext to Business Central** Mapping · history · rollback](https://flitstack.ai/migrations/erp/erpnext/to/microsoft-dynamics-365-business-central) [**Encompass Production Cloud to Business Central** Mapping · history · rollback](https://flitstack.ai/migrations/erp/encompass-production-cloud/to/microsoft-dynamics-365-business-central) [**Odoo ERP to Business Central** Mapping · history · rollback](https://flitstack.ai/migrations/erp/odoo-erp/to/microsoft-dynamics-365-business-central) [**Sage Intacct to Business Central** Mapping · history · rollback](https://flitstack.ai/migrations/erp/sage-intacct/to/microsoft-dynamics-365-business-central) [**NetSuite to Odoo ERP** Mapping · history · rollback](https://flitstack.ai/migrations/erp/netsuite/to/odoo-erp) [**NetSuite to Acumatica** Mapping · history · rollback](https://flitstack.ai/migrations/erp/netsuite/to/acumatica) [**NetSuite to Epicor Prophet 21** Mapping · history · rollback](https://flitstack.ai/migrations/erp/netsuite/to/epicor-prophet-21)

## Sources: official documentation

1. [Business Central on-premises to online migration — Microsoft Learn](https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/migrate-business-central-on-premises)
2. [Update currency exchange rates — Business Central | Microsoft Learn](https://learn.microsoft.com/en-us/dynamics365/business-central/finance-how-update-currencies)
3. [Custom Defined Fields by EOS Solutions — Microsoft AppSource](https://appsource.microsoft.com/en-us/product/dynamics-365-business-central/PUBID.eos_solutions%7CAID.ex067customdefinedfields%7CPAPPID.5d2c2370-931f-423b-bfb5-2128499f89ff)
4. [Object Specifications and Limitations — Business Central | Microsoft Learn](https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-object-specifications-limitations)
5. [Migrate Dynamics GP data to the cloud — Business Central | Microsoft Learn](https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/migrate-dynamics-gp)
6. [Complete cloud migration — Business Central | Microsoft Learn](https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/migration-finish)
7. [Data sovereignty in Dynamics 365 Business Central — Microsoft Learn](https://learn.microsoft.com/en-us/azure/azure-sovereign-clouds/public/sovereign-controls-d365-business-central)

Get a quote

## Moving from NetSuite to Business Central?

Tell us roughly how many records and objects you have. We scope the mapping and the Business Central setup with you, then send a quote.

[Get a quote](https://flitstack.ai/contact)
