Data migration is the part of a NetSuite implementation that nobody puts on the slide, and the part most likely to decide whether go-live is calm or chaotic. For a manufacturer, it is harder than for most businesses, because the data that matters most is operational: items, bills of materials, routings, inventory by lot and location, and open work orders. Get those wrong and costing, planning and fulfillment are wrong from the first day. This guide covers what to migrate, in what order, how to load it, and how to prove it is right before you switch over.
Start with what the business needs on day one
The goal of NetSuite data migration is not to recreate the old system. It is to give the new one exactly what it needs to run the business from go-live, plus enough history to report and audit. Everything else is archived. Teams that try to move everything spend weeks cleaning records nobody will open again, and usually go live later with worse data.
A practical way to scope it is three buckets:
- Master data: the records transactions depend on. Always migrated, always cleaned first.
- Open balances and transactions: what is in flight at cutover. Always migrated, loaded as close to go-live as possible.
- History: what already happened. Migrated selectively, usually as summaries.
Master data, in load order
NetSuite records reference each other, so the order matters. Load a record before anything that points to it.
- Setup lists. Subsidiaries, locations, departments, classes, units of measure, payment terms, tax codes and currencies.
- Chart of accounts. Usually redesigned rather than copied, because segments such as department and location replace many legacy accounts.
- Vendors and customers. Deduplicated, with inactive records left behind, and with addresses, terms and tax settings verified.
- Items. Raw materials, purchased components, subassemblies and finished goods, with units of measure, costing method, lot or serial settings, preferred vendors and lead times.
- Bills of materials. Components and quantities per revision, including scrap allowances.
- Routings and work centers. Operations, run and setup times and the work centers they use, if you are using routings.
- Pricing. Price levels, customer-specific pricing and vendor price lists.
Items and bills of materials are where manufacturers lose the most time. Legacy systems often hold half of the real BOM, with the rest in spreadsheets and in the heads of people on the floor. Plan to rebuild rather than export, and have production review every finished good before it is loaded. Our guides to bills of materials in NetSuite and multi-level BOMs cover how to structure them.
Open balances and transactions
These are loaded at cutover, after the old system is closed for the period:
- Trial balance as of the cutover date, by account and segment.
- Open accounts receivable as individual open invoices, so customers can be invoiced, collected and aged normally.
- Open accounts payable as individual open bills, so payments continue without interruption.
- Inventory on hand by item, location, bin and lot or serial number, with a unit cost. Load from a physical count where you can, not from the old system’s quantities.
- Open sales orders and purchase orders, with remaining quantities and dates.
- Open work orders, either migrated with their issued components or completed in the old process before cutover. Finishing them first is usually simpler.
Each open balance has a control account, and each must reconcile to it. Open AR should equal the AR balance in the trial balance, open AP should equal AP, and the extended value of inventory should equal the inventory accounts. If they do not, find out why before go-live, not after the first close.
History: summarize, don’t replay
Most manufacturers load monthly trial balances for the current and prior fiscal year, which gives comparative financial statements from the start. Detailed transactions stay in the old system in read-only mode or in an export archive. The exceptions are records you are obliged or likely to need: lot and shipment history for recall readiness, serial history for warranty, and customer sales history if sales relies on it for pricing. Those can be loaded as targeted imports.
Tools for loading data into NetSuite
- CSV Import Assistant. NetSuite’s built-in import tool handles most master data and many transactions. It maps CSV columns to fields, can save the mapping for reuse, and supports add and update modes. Large data sets are split into batches.
- Script-based imports. For complex records such as BOMs with many revisions, or transactions that need logic during load, a SuiteScript or integration-based import gives more control and better error handling.
- Integration platforms. If an existing integration will keep running after go-live, it can sometimes also handle the initial load of the records it manages.
Whatever the tool, keep the source files, mappings and load logs. When someone asks in six months why an item has a particular cost, you want to be able to show where it came from.
Prove it before cutover
A migration is only finished when it has been checked. The checks that matter most for manufacturers:
- Mock loads. Run the full migration into a sandbox at least twice. The first pass always finds problems.
- Control totals. Record counts by type, trial balance by account, AR, AP and inventory value, each matched to the source.
- Spot checks by the people who use the data. Buyers check vendors and lead times, production checks BOMs, sales checks customers and pricing.
- A test build. Create a work order for a typical finished good, issue components, build it, and check the cost against what you expect.
- A test MRP run. If planning output looks wrong, the problem is almost always lead times, safety stock or BOMs in the migrated data.
Common data migration mistakes
- Cleaning data after go-live. It never happens, and bad master data affects every transaction that uses it.
- Loading inventory from the old system’s quantities. Count first, then load.
- No owner for each data set. The implementation team can load data, but only the business can say it is right.
- Too much history. It multiplies the work and rarely gets used.
- Last-minute item changes. New items created in the old system during the freeze must be captured, or they will be missing on day one.
Moving from QuickBooks specifically? Our QuickBooks to NetSuite migration guide covers what moves, what stays behind and how to plan the cutover.
Getting migration right
Data migration is where implementation quality shows up first. Consule Solutions treats it as its own workstream in every NetSuite implementation, with mock loads, reconciliations and sign-off by the people who own the data. Our NetSuite implementation guide shows where migration fits in the overall plan. If you are planning a move to NetSuite, talk to us.
Frequently asked questions
What data should be migrated to NetSuite?
Master data such as setup lists, the chart of accounts, customers, vendors, items, bills of materials and routings, plus open balances at cutover: trial balance, open invoices and bills, inventory on hand, and open sales, purchase and work orders. History is usually migrated as monthly trial balances, with detail kept in an archive.
How do you import data into NetSuite?
Most records are loaded with NetSuite’s CSV Import Assistant, which maps spreadsheet columns to NetSuite fields and supports adding and updating records. Complex records or transactions that need logic during load are often imported with SuiteScript or an integration platform.
Should I migrate historical transactions to NetSuite?
Usually only as summaries. Monthly trial balances for the current and prior year give comparative reporting. Detailed history is kept in the old system or an archive, except for records like lot and shipment history that may be needed for recalls or warranty.
How do you verify a NetSuite data migration?
Run mock loads into a sandbox, reconcile record counts and control totals such as the trial balance, AR, AP and inventory value to the source system, have data owners spot check their records, and run a test production build and MRP run before cutover.
How should inventory be migrated into NetSuite?
Load inventory by item, location, bin and lot or serial number with a unit cost, ideally from a physical count taken at cutover rather than from the old system’s quantities, and reconcile the total value to the inventory accounts in the trial balance.