Contact Import CSV
Print
Notes:
- Trim leading and trailing spaces from the entire sheet using Ablebits.
- Column header names must follow the exact same naming scheme as provided or the import upload will fail.
- Blank rows are considered empty and skipped by the importer.
- It is possible to successfully upload 0 rows of information, as long as all required columns are present, the importer will still “succeed”.
- Overwrites will be performed on any data that has been changed between exporting/importing.
Field | Is Field Required? | Additional Details | Max Characters/Values |
Id | Leave Blank | |
|
Name | Yes | | |
Title | No |
| 100 |
Customer Number | Yes | - Refers to the DM Customer Number that was assigned in the customer import
- Not necessary if you have the customer name
- Must be True or False
- Indicates if the row is visible to the end-user since most records are just hidden
| |
Customer Name | No | - Refers to the DM Customer Name from the Customer Import (NEEDS TO BE AN EXACT MATCH)
- Best Practice Tip: Once customers are imported into DM, do an export and use the Customer Number and Customer Name columns to do a Vlookup for the Customer Number on the Contact .csv that is being prepared.
| 120
|
Phone Number | No |
| 50 |
Fax Number | No |
| 50 |
Email Address | No |
| 150 |
Is Deleted | Yes | - True/False
- For Active contacts set to FALSE; Inactive contacts set to TRUE
|
|
Tags | No | - Multiple tags in column to be separated by ; no space. Example: Rush;Delivery
| 200 |
Created Date | No |
|
|
Last Order Date
| No |
|
|
Requires PO
| Yes
| |
|
Credit Card Processing Account
| No |
|
|
Payment
|
|
|
|
Username
| Leave Blank
| | |
Password
| Leave Blank
| | |
Security Role
| Leave Blank
| - Multiple security roles in column to be separated by ; no space.
Example: Rush;Delivery | 200
|
Portals | Leave Blank | - Multiple portals in column to be separated by ; no space. Example: Rush;Delivery
- Portals names must match already existing portals
| |
Default Portal | No |
|
|
Budgets | No | - Must be in the format that is in the Settings > Customers > Budgets
- Multiple budgets can be added in the same row, must be separated by “;”
|
|
Default Budget
| No |
|
|
Budget Required
| Yes | |
|
Approver
| No |
|
|
Billing Id | Leave Blank | - Can be a null or empty value
- Cannot be user created
- Checks for existing Id(s):
If it exists in the database, the Location object associated to the contacts billing location is overwritten with the new information. If they do not exist, a new Location object is created for the contacts billing location.
|
|
Billing Name | No | - If not provided, copy customer name into this column
| 255 |
Billing Address | No | | 500 |
Billing City | No | - If there is an address 1 and address 2, merge the 2 columns with a comma[Space] in order to combine the address into one field
| 50 |
Billing Region | No | - Abbreviated Prov/State
- If region is not in the Settings > Customers > Locations, you will need to add the Name and Abbreviation prior to importing
| 255 |
Billing Country | No | - Country must match Settings>Locations
- If Country is not in the Settings > Customer > Locations, you will need to add the Country prior to importing.
| 255 |
Billing Zip/Postal | No | | 20 |
Shipping Id | Leave Blank | |
|
Shipping Name | No | - If not provided, copy customer name into this column
- Refers to the name of the Location object being created containing the location information about the shipping address
| 255 |
Shipping Address | No | | 500 |
Shipping City | No | | 50 |
Shipping Region | No | - Abbreviated Prov/State
- If region is not in the Settings > Customers > Locations, you will need to add the Name and Abbreviation prior to importing.
| 255 |
Shipping Country | No | - Country must match Settings>Locations
- If Country is not in the Settings > Customer > Locations, you will need to add the Country prior to importing.
| 255 |
Shipping Zip/Postal | No | | 20 |
Did you find it helpful?
Yes
No
Send feedback Sorry we couldn't be helpful. Help us improve this article with your feedback.