Migrate from NetSuite to Microsoft Dynamics 365 Business Central

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

NetSuite's subsidiary model is the central complexity in this migration. 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.

NetSuite Customers map to Dynamics Customers with address, contact, payment terms, and tax registration fields preserved. 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.

NetSuite Vendors map to Dynamics Vendors with the same address, contact, and payment term fields. 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.

NetSuite item types (Inventory Assembly, Non-Inventory, Service, Description Only) map directly to Dynamics item types. 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).

Open NetSuite Sales Orders migrate as Dynamics Sales Orders with the original order date and customer price group preserved. 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.

Open NetSuite Vendor Bills migrate as Dynamics Purchase Invoices with original posting dates preserved for aging. Closed and paid vendor bills similarly follow the carry-forward or replay strategy agreed upon during scoping. PO matching (NetSuite's built-in 2- or 3-way match) becomes Dynamics invoice approval workflows configured post-migration.

Historical journal entries are the highest-risk migration object. NetSuite journals carry prior-period adjustments, intercompany eliminations, and currency revaluation rows with original posting dates and exchange rates. We offer two strategies: (1) Full replay: create Dynamics General Journal lines with original posting dates and rates preserved, maintaining audit trail; (2) Balance carry-forward: create a single opening-balance journal per subsidiary at a designated go-live date, carrying forward net balances rather than replaying each historical row. The choice is captured in the migration contract before sequencing begins.

Outstanding receivables and payables migrate as open ledger entries in Dynamics, not as recreated invoice records. We extract open invoice amounts, due dates, aging bucket assignments, payment terms, and currency from NetSuite, then create Customer or Vendor Ledger Entries with the original document dates. Reminder levels and finance charge settings require post-migration configuration in Dynamics.

NetSuite Custom Records are user-defined record types with custom fields (custrecord_*, custcol_*). Every NetSuite environment has a unique custom record schema discovered via SuiteQL. We export the full custom record registry, map each custom record type to a Dynamics extension table, and create the destination schema in the Dynamics development environment before migration. Lookup relationships between custom records and standard objects require careful resolution of the internalId-to-GUID mapping during import.

NetSuite attaches custom fields to nearly every standard object using prefix conventions (custbody_*, custcol_*, custentity_*, custitem_*). We run a metadata discovery pass via SuiteQL to enumerate all active custom fields per account, then create equivalent Dynamics AL extension fields. Custom fields on transaction lines (custcol_*) require special handling in Dynamics OData or API payloads. Field types (text, date, checkbox, list, currency) are mapped to their Dynamics equivalents before schema deployment.

NetSuite tax codes define nexus, rates, and filing jurisdictions referenced by internalId on transaction lines. We preserve the full tax code registry and map each code to Dynamics Tax Groups and Tax Business Posting Groups. Nexus assignments in NetSuite become Tax Area configurations in Dynamics. E-invoicing compliance settings (PEPPOL, EU EN 16931) are documented separately for F&O and BC EU localization packs.

NetSuite Employee records (from the HR module) include compensation history, PTO balances, and benefits enrollment. We map employees to Dynamics 365 Human Resources Worker records. Effective-dated compensation rows require careful sequencing to maintain correct historical pay records. Benefits enrollment migrates as Worker Benefit records if the HR module is included in scope; otherwise it is flagged as a manual post-migration task.

NetSuite SuiteProjects Pro records (project billing, time entries, resource allocations, milestones) map to Dynamics Projects. Project financials must be separated from standard G/L transactions. We map project status, billing method, and cost prices from NetSuite to Dynamics Project dimensions and pricing structures. Time entries migrate as project journal lines. Fixed-price project milestones map to Dynamics contract lines with billing schedules.

NetSuite Saved Searches are reporting objects that do not have a direct Dynamics equivalent. We do not migrate Saved Searches as functional objects. Instead, we deliver a written inventory of every active Saved Search with its criteria, columns, filters, and recipient list, so the customer's Dynamics admin or partner can rebuild them as Dynamics Views, Power BI reports, or RDL-based SQL Server Reporting Services reports. This inventory is included in the standard migration deliverables.

NetSuite SuiteBuilder workflows and SuiteScript 2.x automations do not migrate. They are structurally incompatible with Dynamics 365's automation model (Power Automate for cloud flows, AL-based workflows for server-side events). We deliver a written inventory of every active workflow and scheduled script with its trigger conditions, actions, and recommended Power Automate or AL equivalent. The customer's Dynamics partner or admin rebuilds these post-migration as a separate engagement.

NetSuite File Cabinet documents attached to records are extracted as file content with metadata (file name, created date, attached record type and ID). We deliver them as a file package with a manifest mapping each file to its source record. The customer's admin uploads to SharePoint (connected to Dynamics via native SharePoint integration) or attaches directly to Dynamics records post-migration. Large binary files (BDC, images) are chunked and retried under export rate limits.

NetSuite role-based permissions (where one employee can have multiple active roles) map to Dynamics Security Groups and Permission Sets. We extract role assignments from NetSuite, map each role to the nearest Dynamics security group equivalent, and flag any elevated-role assignments (OneWorld roles, SuiteCloud Plus access) that require additional permission set configuration. Active NetSuite users map to active Dynamics users provisioned by the customer's admin before migration.