Migrate your NetSuite data

NetSuite Accounts are identified by account type codes (0=Bank, 1=AR, 2=Inventory, 5=Fixed Assets, 10=AP, 21=Income, 23=COGS, 24=Expense, etc.) and optionally by acctNumber. We preserve the full account hierarchy including contra and parent-child relationships. Accounts can only be set on Add, so we map historical account assignments at the transaction level.

NetSuite Entities include Customers, Vendors, Partners, and Employees as distinct record types. We migrate Entity records with all standard address, contact, and tax-registration fields. Custom fields on Entity records are handled via custentity_* script IDs.

Items include inventory assembly, non-inventory, service, and description-only types. We preserve build assemblies, BOM relationships, landed cost fields, and pricing matrices. Lot/serial number settings and preferred bin locations are migrated as Item fields.

NetSuite transactions carry rich line-level detail including item fulfillment data, tax lines, and exchange rates. Historical transaction migration requires careful sequencing because open vs. closed status affects posting groups in destination systems. We chunk by date ranges to respect API concurrency ceilings.

Outstanding receivables and payables must be migrated as open balances rather than recreated as historical transactions. We extract open invoice amounts, due dates, aging buckets, and payment terms. Some customers prefer to close open AR/AP in NetSuite and create fresh open balances at the destination.

NetSuite's subsidiary model is unique — one database can represent multiple legal entities with intercompany eliminations. When migrating out of NetSuite to a system like Business Central that requires separate company databases, we split subsidiary data and map it to destination company records with mandatory posting groups.

Employee records include compensation history, PTO balances, and benefits enrollment. NetSuite's HR module is less mature than its financials module. Effective-dated compensation rows require careful sequencing. We flag which fields require HR-specific role permissions to access.

NetSuite Custom Records are user-defined record types accessed via custrecord_* script IDs. They can have custom fields, custom lists, and sublists. Every customer environment has a different schema of custom records. We discover the full custom record registry during scoping and map each to the destination equivalent.

NetSuite attaches custom fields to nearly every standard object using custbody_*, custcol_*, custentity_*, and custitem_* prefixes. These must be discovered per-entity, mapped to destination custom fields, and written via the customFieldList in SuiteQL/SOAP payloads.

NetSuite's File Cabinet stores documents attached to records. We extract file metadata and content URLs where accessible via REST. Large file transfers are chunked and retried under rate limit constraints.

NetSuite Projects (PSA) include billing records, time entries, resource allocations, and milestones. Project financials must be separated from standard G/L transactions. We map project status and billing rates to the destination project management module.

NetSuite uses a role-based permission model where one employee can have multiple roles. User migration involves mapping role assignments to destination role equivalents and flagging users with elevated SuiteCloud access.

NetSuite tax codes define nexus, rates, and filing jurisdictions. Tax codes are referenced by internalId on transaction lines. We preserve the full tax code registry and map nexus assignments to destination tax configuration.