NetSuite CSV Import Template Guide
Most failed NetSuite CSV imports are caused by a few avoidable issues: bad dates, missing required fields, duplicate external IDs and record names that do not match exactly. This generator produces a one-page import plan and column spec so the person preparing the file knows the rules before the first run.
Fill in
NetSuite CSV Import Template Guide
NetSuite CSV Import Plan
Company: Acme Precision Ltd Record type: Inventory Items Import owner: A. Kumar Planned run date: 2026-11-05 Import type: Add or Update Expected rows: 1500
File rules
Save the file as CSV with a header row. Use the date format MM/DD/YYYY and make sure it matches the date format preference of the user who runs the import. Do not use thousands separators in numbers. Keep text with commas inside double quotes. Remove blank rows at the end of the file.
External ID rule: Legacy system key prefixed with source code, e.g. ITM-000123
Column specification
| Column header | NetSuite field | Required | Format or allowed values | Example |
|---|---|---|---|---|
| External ID | External ID | Yes | Unique text, stable across re-runs | |
| Name or number | Primary identifier | Yes | Text | |
| Subsidiary | Subsidiary | If OneWorld | Exact name as in NetSuite | |
| Date columns | Date fields | As needed | MM/DD/YYYY | |
| List or record columns | Linked records | As needed | Exact name or internal ID | |
Import steps
1. In the sandbox, go to Setup, Import/Export, Import CSV Records. 2. Choose the record type Inventory Items and the import type Add or Update. 3. Upload the CSV file and set the character encoding and data handling. 4. Map each file column to a NetSuite field, then map related list or sublist fields if the file has more than one line per record. 5. Save the import map with a clear name so the run can be repeated. 6. Run the import and download the job status and error file. 7. Fix rejected rows in the original file and re-run only those rows. 8. Repeat the full process in production only after the sandbox result has been reviewed.
Post-import checks
Compare imported record count with the expected 1500 rows. Spot check at least ten records against the source. Run a saved search on External ID to find duplicates or blanks. Confirm related lists, currencies and subsidiaries are correct before opening the records to users.
Sign-off
This is a planning document, not a replacement for the Import Assistant. Required fields and field names depend on your account features and customisation, so confirm against the record's import field list in your own account.
Get a second pair of eyes on your migration data
Optional: have your source data profiled before load, with duplicates, blanks and mismatched values listed for review.
Optional. The tool and every export work without this. No spam.
How to use it
Choose the record type, import type and date format, then fill in the owner, planned date and external ID rule. Export the document to PDF or Word and send it with a sample file. Add your real columns to the specification table. Keep one plan per import so every run is documented and repeatable, especially during a data migration with several waves.
Why external IDs matter
An external ID is a text key you control. If you set one on every record, you can safely re-run an Add or Update import, link child records to parents without internal IDs, and find the exact source row behind any NetSuite record. Choose a pattern with a source prefix and never reuse values. Without them, a re-run after a partial failure creates duplicates.
Mapping and import types
Add creates new records, Update changes existing ones, and Add or Update does both based on a match key such as the internal ID, external ID or name. Save the mapping once and reuse it. When the file has multiple lines per record, such as sales order lines, map the sublist fields and keep a shared key on every line so the lines group under one transaction.
Common mistakes
Frequent problems include dates that do not match the user's preference, unmatched list values because a name differs by one character, running in production without a sandbox test, importing with a script or workflow still active that changes the data, and fixing errors in the error file instead of the source. Always correct the source file so the next run is clean.
Frequently Asked Questions
How do I import CSV records in NetSuite?
Go to Setup, Import/Export, Import CSV Records, pick the record type and import type, upload the file, map columns to fields, save the map and run. Review the job status page for errors and download the error file to fix rejected rows.
Why does my NetSuite CSV import fail on dates?
The date format in the file must match the date format preference of the user running the import. A file with day first dates will fail or load wrong values for a user set to month first. Standardise the format before uploading.
Should I use internal IDs or external IDs?
External IDs are easier to manage because you control them and can set them in advance. Internal IDs only exist after creation and differ between sandbox and production, so they are poor keys for repeatable migrations.
Can I undo a CSV import?
Not as a single action. Plan for it by testing in a sandbox, tagging imported records with an external ID or a batch field, and keeping the original file so you can search for the batch and correct or remove records deliberately.
If you are planning a larger migration into NetSuite, Netray can help with reconciling and checking source ERP data before it is loaded, including on-prem options.
Related Tools
NetSuite Saved Search Formula Generator
Fill in your field IDs and thresholds and get copy-ready formula snippets for NetSuite saved search results and criteria.
NetSuiteNetSuite Role Permission Matrix Worksheet
An editable worksheet that records which role holds which permission level on each record area and scores the access risk for review.
NetSuiteNetSuite Assembly Build Checklist
A pre-build and post-build checklist for NetSuite assembly items and work orders, covering setup, inventory and costing checks.
NetSuiteNetSuite Month End Close Checklist
A practical NetSuite period close checklist covering subledgers, inventory and manufacturing, accruals, reconciliations and period lock.
More NetSuite tools
See all- NetSuite Inventory Costing Method Reference
- NetSuite License Cost Estimator
- NetSuite User Access Request Form Template
- NetSuite Custom Record Design Spec Template
- NetSuite SuiteScript Deployment Handover Template
- NetSuite Sandbox and Release Change Log Worksheet
- NetSuite Script and Workflow Inventory Worksheet
- NetSuite SuiteQL Transaction Query Generator
- NetSuite Transaction Type Codes Reference