Importing into NetSuite, step by step

Exactly what to choose on each NetSuite screen to turn a NetOrderFlow CSV into Sales Orders.

You have a CSV from the Export center and you want Sales Orders in NetSuite. This is the NetSuite side of the process. There is also a shorter version of this inside the app at Settings → NetSuite import guide.

Before you start

  • Your NetSuite role needs the CSV Imports permission.
  • Customers and items referenced by the file must already exist in NetSuite with matching Internal IDs or External IDs.
  • If the export produced a file ending in _new_customers.csv, import that first as Customers, then bring the new Internal IDs back into NetOrderFlow through Settings → Import before importing the orders.

Scan & Upload File

  1. 1Go to Setup → Import/Export → Import CSV Records.
  2. 2Set Import Type to Transactions.
  3. 3Set Record Type to Sales Order.
  4. 4Choose One File to Upload and select the CSV from the Export center.
  5. 5Leave the CSV Column Delimiter as Comma.
  6. 6Select Next.

Import Options

  1. 1Data Handling: choose Add for a first-time import. Choose Add or Update when you are re-importing a corrected file — NetSuite matches on External ID and updates the existing transaction instead of duplicating it.
  2. 2Open Advanced Options and set the Date Format to match the format configured on Settings → Defaults in NetOrderFlow.
  3. 3Set the Custom Form if your account requires a specific Sales Order form.
  4. 4Leave Run Server SuiteScript and Trigger Workflows off for your first test import, then turn on whatever your account normally relies on.
  5. 5Select Next.
Date format is the quiet failure

A mismatch between the CSV format and the format selected here does not error. It imports the wrong date. Confirm both sides before your first real batch.

File Mapping

The file is a single flat CSV with one row per order line, so NetSuite treats it as one file containing both header and line data. Confirm the Sales Order record and its Items sublist are both selected.

Field Mapping

  1. 1Map external_id to External ID on the Sales Order. This is the key that groups consecutive rows into one transaction, so it is the single most important mapping on the screen.
  2. 2Map customer to the Customer field, using the reference type your template writes — Internal ID is the default.
  3. 3Map order_date to Date, and requested_ship_date to Ship Date if you export it.
  4. 4Map item, quantity, and rate to the Items sublist fields Item, Quantity, and Rate.
  5. 5Map subsidiary, location, department, and class to their segment fields. Subsidiary is mandatory on OneWorld accounts.
  6. 6Map po_number, memo, terms, shipping_method, sales_rep, and any custom columns to their NetSuite equivalents.
  7. 7Map discount columns to the discount item and rate fields your account uses.
  8. 8Select Next.

Save Mapping & Start Import

  1. 1Give the mapping a name such as NetOrderFlow Sales Orders and save it.
  2. 2Select Save & Run.
  3. 3Watch the job at Setup → Import/Export → View CSV Import Status.
  4. 4Download the error CSV if the job reports failures, and work through them with the import errors article.
Reuse the saved mapping

Once the mapping is saved, later files with the same column layout can be imported in a couple of clicks. If you change an export template, re-check the saved mapping — new or reordered columns will not map themselves.

Finish in NetOrderFlow

Return to Settings → Reconcile, tick the orders that imported successfully, optionally record the NetSuite transaction ID for each, and mark them reconciled. That closes the loop and keeps the outstanding list honest.

Troubleshooting failed rows

NetOrderFlow does this for you. Start a 14-day free trial.

Questions about this guide?