Customer import
It is important to identify whether an entity being imported is an individual or a company. Individual customers have Firstname and Lastname fields, which are missing from a company customer. That information is recorded on the contact record for a company customer. I recommend splitting entity imports into an individual file and a company file because they require different import maps.
Example 1 – Customer import use case
Let's analyze this table for import as an example:
Company | Firstname | Lastname | Email  | Street address | City | State | Country | Terms |
Disney | Donald | Duck | dd@disney.com | 123 Main Street | Orlando | Florida | United States | Net 30 |
Universal | Harry | Potter | h@potter.com | 905 Young Street | Orlando | FL | US | Net 30 |
Mi6 | James | Bond | 007@mi5.co.uk |  100 Church Street | London | UK | Net 60 | |
N/A | Katy | Perry |  kphotmail.com |  102 7th Ave | New York | NY | USA | Net 15 |
The values in the country field need to be changed:
- United States is named three different ways and these need to be changed to the value in NetSuite, which is United States...