|SharpSpring allows you to import more than one contact at a time by importing a Comma-Separated Value (.CSV) file via the Import Tool.
This article will provide information on the Import Tool.
Regarding CRM Migration
This article details the methods and features involved when importing contacts. This article does not go into detail on migrating accounts. Refer to the following articles for more information on migrating over accounts, opportunities, campaigns, or notes from other CRM platforms:
Preparing Import with .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|
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.
Refer to the following help articles for more information on how to structure .CSV files and what they should contain:
Importing Contacts with .CSV Files
You can import .CSV files as necessary.
To import .CSV files, do the following:
Important: The Import Tool is for contact and lead information only. Imports do not trigger certain features, such as dynamic lists.
Configuring Import Settings
Once a .CSV file has been imported, its list of contacts will need to be configured. Doing so will determine which list the contacts will be set to, their ownership, and overall status.
To configure an imported list, do the following:
After the import settings have been configured, you will need to map the contents of your spreadsheet to SharpSpring.
To map contacts when importing .CSV files, do the following:
When importing .CSV files, SharpSpring tries to automatically map certain standard fields like First Name, Last Name, and Email. It is not always able to do so, but you may see fields already mapped. You can reassign these fields if you do not want to map them how SharpSpring tries to map them for you.
Once imported, the list will appear in the Import History.
Important: 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. To restore system fields, contact SharpSpring Support.
Sender Reputation: Evaluating Imported Lists
When you import a new list, SharpSpring evaluates the overall quality of the list based on a variety of factors, including an evaluation done by a third-party verification service. If 45% or more of the list contains contacts with email addresses deemed invalid, toxic, or purchased, SharpSpring will not allow your import to continue.
SharpSpring has determined these lists would fall into the lowest 2.5% of list quality, and they have a high risk of damaging your sender reputation should an email send be attempted. This measure is taken to ensure the long-term health and viability of the platform and to protect your own sender and domain reputation.
In the rare case that a list is rejected due to low quality, SharpSpring's compliance team will be notified. Contact firstname.lastname@example.org for further clarification.
Refer to Using Email Engagement Tools for more information about the evaluation of imported or created contacts and list rejections.