Week 7 of 8
Data migration and CSV imports
Whether you are moving from QuickBooks, adding a subsidiary or loading a new price list, the CSV Import Assistant is usually how data reaches NetSuite. It takes up to 25,000 records or 50 MB per job, and Oracle recommends starting each load with a test import of a couple of records.
Two cautions from Oracle are worth repeating. Imported transactions behave like ones entered on screen, so an imported vendor bill with inventory items changes inventory. And open A/R and A/P must not be counted again in the opening balances you import later.
This week: plan the loads and agree how you will prove them
- Sequence the loads: setup records, then master data, then open transactions, then the opening trial balance journal.
- Use External IDs as reference keys. Name references must match NetSuite’s dropdown values exactly.
- Agree reconciliation checks and tolerances with the controller before the first mock: counts, trial balance, A/R and A/P aging, inventory quantity and value.
- Log every import job’s error rate and read every response file. Then run the reconciliation on every mock, not just the last one.
Number of the week
25,000
records (or 50 MB) is the CSV Import Assistant limit per import job.
Source: Oracle NetSuite Help Center, General CSV File ConventionsUse this week
- NetSuite CSV Import Data Migration Tracker →
Load plan, job log with error rates and a source-to-NetSuite reconciliation.
- Mock Cutover Rehearsal Tracker →
Goals, timings and variance for each rehearsal.
- NetSuite Implementation Test Plan & Go-Live Checklist (Word) →
Test levels, entry and exit criteria and a 14-point go-live checklist.
Next week, the last of the playbook: making the upgrade call, and keeping up without burning out a small team.
Get the playbook in your inbox, one week at a time
Subscribe free and every template in the library is yours.