Skip to main content

Data Migration

Import your data into NetSuite via CSV.


The Import Process

DATA MIGRATION WORKFLOW
===============================================================================

Step 1: Export from old system

Step 2: Prepare CSV file (map columns)

Step 3: Test import (small batch)

Step 4: Fix errors

Step 5: Full import

Step 6: Verify data

Setup > Import/Export > Import CSV Records

Step-by-Step: Basic Import

Step 1: Prepare Your CSV

CSV FILE EXAMPLE: CUSTOMERS
===============================================================================

Company Name,Email,Phone,Address,City,State,Zip
"ABC Corporation",contact@abc.com,555-1234,123 Main St,New York,NY,10001
"XYZ Industries",info@xyz.com,555-5678,456 Oak Ave,Chicago,IL,60601
"Demo Company",demo@demo.com,555-9999,789 Pine Rd,Dallas,TX,75001

CSV Tips:

  • First row = column headers
  • Use quotes around text with commas
  • Save as UTF-8 encoding
  • Maximum 25,000 rows per file

Step 2: Start the Import

STARTING AN IMPORT
===============================================================================

Step 1: Navigate
Setup > Import/Export > Import CSV Records

Step 2: Select Import Type
├── Record Type: Customer
└── Character Encoding: UTF-8 (usually)

Step 3: Select your file
Click "Select" and choose your CSV

Step 4: Click "Next"

Step 3: Map Fields

FIELD MAPPING
===============================================================================

CSV Column → NetSuite Field
─────────────────────────────────────────
Company Name → Company Name
Email → Email
Phone → Phone
Address → Address 1
City → City
State → State
Zip → Zip

Tip: NetSuite will auto-match common column names

Step 4: Set Import Options

IMPORT OPTIONS
===============================================================================

Common Settings:
├── Overwrite/Add: Add new records only OR update existing
├── Multi-Select Delimiter: How to separate multiple values
└── Run in Background: ✓ for large imports

For Updates:
├── Match by: Which field identifies existing records
│ ├── Internal ID
│ ├── External ID
│ └── Name/Email/etc.

Step 5: Run Test Import

TESTING YOUR IMPORT
===============================================================================

Always do a test first!

Option 1: Test with small file
├── Create CSV with 5-10 rows
├── Run import
├── Check the results
└── Delete test records

Option 2: Use "Preview" feature
├── Click "Preview" instead of "Import"
├── Review what would happen
└── Check for errors before committing

Step 6: Review and Fix Errors

HANDLING ERRORS
===============================================================================

After import, check the Job Status:
Setup > Import/Export > View CSV Import Results

Common Errors:
├── "Required field missing" → Add column to CSV
├── "Invalid value" → Fix data format
├── "Duplicate record" → Already exists (use update)
└── "List value not found" → Value not in dropdown

What Can Be Imported?

Record TypeExamples
ListsCustomers, Vendors, Items, Employees
TransactionsSales Orders, Invoices, Bills
Custom RecordsAny custom record you've created

Import Order Matters

When importing related data, follow this order:

IMPORT DEPENDENCY ORDER
===============================================================================

Groups/Classifications FIRST:
├── Departments
├── Locations
├── Classes
└── Custom Lists

Then Master Records:
├── Customers
├── Vendors
├── Items
└── Employees

Last, Transactions:
├── Sales Orders
├── Invoices
├── Purchase Orders
└── Bills

Why? Transactions reference customers, items, etc.

Common Field Mappings

Customer Import

CSV ColumnNetSuite Field
Company NameCompany Name
Contact NameContact (create separately)
EmailEmail
PhonePhone
AddressAddress 1
CityCity
StateState/Province
ZipZip
CountryCountry
Credit LimitCredit Limit
Payment TermsTerms

Item Import

CSV ColumnNetSuite Field
Item NameItem Name/Number
DescriptionDescription
PriceBase Price
CostCost
Item TypeItem Type
Inventory LocationLocation
QuantityInitial Quantity

Best Practices

DoDon't
Test with small batch firstImport 10,000 rows untested
Clean data before importImport dirty data
Back up before major importsSkip backups
Import in correct orderImport transactions first
Document what you importedForget what you did

Quick Reference

I want to...Go to
Import recordsSetup > Import/Export > Import CSV Records
Check import statusSetup > Import/Export > View CSV Import Results
Download templateDuring import wizard, click "Download Template"
Delete failed importsLists > [Record] > Delete or Mass Delete

Key Takeaways

  1. Clean data first - garbage in = garbage out
  2. Test small batch - before full import
  3. Follow dependency order - lists → masters → transactions
  4. Map fields carefully - check the preview
  5. Keep import files - for reference later