Data Migrations Setup

You'll need to move some company information from your other system into NetSuite. Besides system integrations, comma-separated value (CSV) import is the most way to move small or medium data sets from other applications into NetSuite. CSV import saves time and helps prevents errors since you can add or update many records at one time, instead of entering them manually.

Use web services for large or ongoing data migrations and for migrating record types that CSV import doesn't support. For information, see System Integrations Setup.

Review the following tasks and the detailed information available to prepare for migrating your company’s data.

Task	More Information
Clean up your data before importing, and make sure your CSV files match NetSuite file conventions and record types.	Guidelines for CSV Import Files
Save related data in separate CSV files, for example, save employee data in one file. There is one exception to this guideline: import customers, prospects, and leads with contacts.	Importing Entities and Contacts Together
Follow these best practices when performing CSV imports: Start with a test import using a couple of records. Break large jobs into smaller chunks to help things run smoothly. Each import file can have up to 25,000 records. Run imports during off-peak hours.	—
When importing transactions: Don't import lots of historical transactions – your storage may be limited. For information about how much space you have, contact your account manager. Imported transactions behave like those you create in the user interface. For example, an imported vendor bill with inventory items affects your inventory. When you import open accounts payable and accounts receivable transactions, make sure the amounts are not duplicated in the account balances you import later.	Transactions Import Type

Task

More Information

Clean up your data before importing, and make sure your CSV files match NetSuite file conventions and record types.

Guidelines for CSV Import Files

Save related data in separate CSV files, for example, save employee data in one file. There is one exception to this guideline: import customers, prospects, and leads with contacts.

Importing Entities and Contacts Together

Follow these best practices when performing CSV imports:

Start with a test import using a couple of records.
Break large jobs into smaller chunks to help things run smoothly. Each import file can have up to 25,000 records.
Run imports during off-peak hours.

—

When importing transactions:

Don't import lots of historical transactions – your storage may be limited. For information about how much space you have, contact your account manager.
Imported transactions behave like those you create in the user interface. For example, an imported vendor bill with inventory items affects your inventory.

When you import open accounts payable and accounts receivable transactions, make sure the amounts are not duplicated in the account balances you import later.

Transactions Import Type

Related Topics