- If you are not familiar with the record and fields in the record that needs to be imported, the best thing is to do at first is manually create a record with the data in the import file. By doing this we can identify the additional or custom fields that should be mapped even if they are not mandatory.(Certain script or work flow will some sometimes restrict record creation if we miss some data)
- Create saved search(s) to monitor the data as it is imported and then run validations on the outcome.
- Determine any scripts or workflows that could trigger with your import.
- We create sample runs to make sure my field mapping is exact. NetSuite can be picky about what is accepted and how it is accepted.
- Always use External IDs: in order to identify your records, using a External ID is the best way to not lose track of your data.
- Identify duplicates
- Cleanse your data – make sure all duplicates are removed, your data file is as full of information for each entity. The fuller the information on each record the more efficient and precise the output can/will be.
- Field format – if the field is a date field then the date field in the CSV file must be exactly the same, for example, if you have an American date format in NetSuite but you use a UK date format in Excel it will not upload as required.
- Use Internal IDs where you can – the use of Internal ID’s can be beneficial, for example, if you have multiple subsidiaries, mapping using Internal ID’s will remove the use of the string name that the subsidiary field requires.
- Fields within NetSuite that are lists – If the field you are uploading to is a list field, the options within the list must be used on the CSV file, they must also be exact.