Importing Data into NetSuite

Owned by David Geilhufe
Last updated: Mar 31, 2017 by Mike Ongchua (Unlicensed)

Types of Data

Importing Options

The options available for getting your data into NetSuite include (from least to most complicated):

  1. Type your data into NetSuite
  2. Import a spreadsheet into NetSuite (csv import)
  3. 3rd party tools
  4. ODBC (extra module at additional cost)
  5. Web Services (write code to import your data)

Quickbooks Imports

Quickbooks information can be imported into NetSuite. You options from least difficult to most difficult are:

  1. Import opening balances only.
  2. Import summary journal entries to provide accurate historical information to whatever level or granularity you require.
  3. Import financial transactions from Quickbooks.

**We strongly recommend options 1 or 2. In general, it is better to choose a cut over date and view information prior to the cut over date in Quickbooks. Option three will require engagement of a consultant (various NetSuite partners provide migration services, too).

Recommendations

In general we recommend that grantees use one of two methods:

  1. CSV Import. There is no cost for this capability.
  2. Celigo SmartClient. There is a cost for this capability. http://celigo.com/products/netsuite/excel-smartclient/

 Suggested Sequence

  1. Classifications: Department/Class/Location
  2. Chart of Accounts
  3. Employees
  4. Import Relationships(Entities)
  5. Import Activities and Communications
  6. Import ERP Transaction Data 

Best Practices:

  • Import Customer records first
  • Import Contact records second
  • Consider values associated with Global Subscription Status field - A marketing automation consideration
  • Designate one address as the primary address when importing multiple addresses

Preparing for Data Import

  • Review existing data and scrub data
  • Determine import options
  • Determine how to map from existing application into Netsuite
  • Create a .csv template
  • Run test imports
  • Resolve errors
  • Plan for data migration
  • Import data prior to the "go-live" event
  • Resolve any errors
  • Review data validity

Import files