SharpSpring enables you to import your contacts through a Comma-Separated Value (.CSV) spreadsheet by using the Import Tool. In order to import the file properly, you will need to map your spreadsheet to SharpSpring. This article will detail how to map contacts from your .CSV fields into SharpSpring fields.
|
Available with: | ||||
Marketing Automation | ✓ | ||||
CRM Ultimate | ✓ | ||||
CRM PRO | ✓ | ||||
CRM Free | ✓ | ||||
Toolbar: | |||||
![]() |
|||||
Users: | |||||
Administrators | ✓ | ||||
Company Managers | ✓ | ||||
Marketing Managers | ✓ | ||||
Sales Managers | ✓ | ||||
Salespersons | |||||
Jr. Salespersons | |||||
Important Information Regarding .CSV Files
The Import Tool uses information from .CSV files and creates contact lists from this information. These files contain only alphanumeric data and are presented in a table format.
Any .CSV file that you import should be structured similar to the following:
First Name | Last Name | Is Unsubscribed | |
Galileo | Galilei | g@polymath.com |
0 |
Edwin | Hubble | space@extragalatic.com |
0 |
Hipparchus | math@trig.com |
1 |
When importing .CSV files, be aware of the following:
- Header rows are required. Header rows are necessary for mapping SharpSpring fields to imported fields.
- Email fields are required. The Import Tool requires that your .CSV file contain a column mapped to the Email field. You will still need to include the Email column when a contact does not have an email address.
- Is Unsubscribed fields are required. For SharpSpring to successfully import a .CSV file, the file needs one column header that is labeled as Is Unsubscribed. The Is Unsubscribed field should be a boolean field, where 0 is for leads who are opted in, and 1 is for leads who are not opted in.
- Utilize first and last names. For the import to be successful, a first and last name are suggested in the event that you do not have an email address for that contact. Use both as often as possible.
- Values must match. When importing custom field values, ensure that they are formatted to match the custom field values. For example, picklist and checkbox values are case-sensitive.
- When importing data with picklist and checkbox fields, the fields must be present in the file import in order to appear. Ensure that the picklist or checkbox fields in your file exist before importing. Otherwise, the data may not import properly.
- When importing to a checkbox custom field, the data cannot have spaces between values and commas. An example of this would be value1,value2,value3.
For more information on how to structure .CSV files and what they should contain, refer to the following help articles:
Importing Contacts
You can import contacts through the Import Tool.
To import contacts, do the following:
|
||||
|
||||
Note: You can import notes via the CRM Migration Tool.
|
||||
|
Mapping Fields
When importing .CSV files, SharpSpring tries to automatically map certain standard fields like First Name, Last Name, and Email. You can reassign these fields if you do not want to map them how SharpSpring tries to map them for you. To map contacts when importing .CSV files, do the following:
|
||
Important: When importing and mapping contacts, use SharpSpring fields already present in the system when possible instead of duplicating the fields. Importing and mapping custom fields with the same name as system fields results in those system fields being rendered invisible and unusable in the platform. For more information on available system fields, refer to Available SharpSpring System Fields. To restore system fields, contact SharpSpring Support.
|