# NetSuite CSV Import Template Guide > Source: https://netray.co/tools/netsuite-csv-import-template-guide > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Generate a one-page CSV import plan and column specification document for a NetSuite record type, ready to hand to whoever prepares the data. ## Category netsuite ## Erp NetSuite ## Audience - NetSuite administrator - Data migration lead - NetSuite consultant ## Tool **Kind:** template **Output:** document **Fields:** #### Company **Key:** company **Type:** text **Default:** Acme Precision Ltd #### Record type **Key:** record_type **Type:** select **Options:** - Customers - Vendors - Inventory Items - Assembly Items - Sales Orders - Journal Entries - Bill of Materials **Default:** Inventory Items #### Import owner **Key:** owner **Type:** text **Default:** A. Kumar #### Planned run date **Key:** run_date **Type:** date **Default:** 2026-11-05 #### Import type **Key:** import_type **Type:** select **Options:** - Add - Update - Add or Update **Default:** Add or Update #### External ID rule **Key:** ext_id **Type:** text **Default:** Legacy system key prefixed with source code, e.g. ITM-000123 #### Date format in file **Key:** date_format **Type:** select **Options:** - MM/DD/YYYY - DD/MM/YYYY - YYYY-MM-DD **Default:** MM/DD/YYYY #### Expected row count **Key:** row_count **Type:** number **Default:** 1500 **Blocks:** #### NetSuite CSV Import Plan **Body:** Company: {{company}} Record type: {{record_type}} Import owner: {{owner}} Planned run date: {{run_date}} Import type: {{import_type}} Expected rows: {{row_count}} #### File rules **Body:** Save the file as CSV with a header row. Use the date format {{date_format}} 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: {{ext_id}} #### Column specification **Table:** **Columns:** - Column header - NetSuite field - Required - Format or allowed values - Example **Rows:** **0:** External ID **1:** External ID **2:** Yes **3:** Unique text, stable across re-runs **0:** Name or number **1:** Primary identifier **2:** Yes **3:** Text **0:** Subsidiary **1:** Subsidiary **2:** If OneWorld **3:** Exact name as in NetSuite **0:** Date columns **1:** Date fields **2:** As needed **3:** {{date_format}} **0:** List or record columns **1:** Linked records **2:** As needed **3:** Exact name or internal ID #### Import steps **Body:** 1. In the sandbox, go to Setup, Import/Export, Import CSV Records. 2. Choose the record type {{record_type}} and the import type {{import_type}}. 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 **Body:** Compare imported record count with the expected {{row_count}} 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 **Signatures:** - Prepared by - Data owner - NetSuite administrator **Notes:** 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. ## Content **Intro:** 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. **Sections:** #### How to use it **Body:** 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 **Body:** 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 **Body:** 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 **Body:** 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. **Cta:** 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. **Faq:** #### How do I import CSV records in NetSuite? **Answer:** 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? **Answer:** 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? **Answer:** 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? **Answer:** 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. ## Search terms netsuite csv import template, netsuite csv import guide, netsuite import csv records steps, netsuite external id csv import, netsuite csv import errors, netsuite data migration template, netsuite import assistant mapping --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json