In order to support the batch loading of Accounts, Contacts, Events, or Custom Table information, ChurnZero allows the ability to upload a CSV file. To access Data > Imports, you must have the "Digital Tools Tools" user permission. 

Importing CSVs allows you to create and update the information on your ChurnZero accounts, contacts, events, and custom tables. If these objects and fields bi-directionally sync with your CRM, this will cause your CRM to update as well. If you have any questions about how to execute these imports or what it will look like with your current integration workflow, please reach out to your ChurnZero Customer Success Manager or Implementation Specialist.

• NOTE:
  • There is a threshold for the number of validation issues we can process before cancellation. That threshold is set to 100. File uploads will cancel automatically if the CSV import hits 100 validation issues.
  • Depending on how many Imports are submitted, and how much data they contain, they may take some time to complete. You can check the progress of your Imports in your Admin space under Data > Dev Console. More information on this feature can be found in our Dev Console article.

Use the links below to jump to the relevant section in this article:

• How to Import (Steps)
• Account Imports (Required fields)
• Contact Imports (Required fields)
• Event Imports (Required fields)
• Activity Imports (Required fields)
• Survey Imports (Additional steps  and required fields)
• Custom Table Imports (Additional information and required fields)

How to Import:

1. In the Admin space, go to Data > Imports from the left-side navigation bar.
2. Select from the Entity drop-down. In this example, we've selected Account.
3. Enter your email address in the Notification email field to receive an alert when the import is completed. You will also receive an error email if the import fails. 
   
4. Click the Choose File button, then attach the .csv file you wish to upload. The CSV must have a header and must support the fields for your entity (Account, Contact, etc).
   • You can download a .csv file template containing all supported headers by clicking the Export button.
5. When you have attached the .csv to upload, confirm that your columns will be recognized in the import based on the Position identifier. 
   • Please ensure that all fields you are looking to update with the import have a Position recognized before submitting the import.
6. Click the Submit button on the right-hand side.

Account Imports

Follow the steps in the "How to Import" section. Below you will find the required and optional fields for the Account entity.

Required Fields:

• accountExternalId (string) - The accountExternalId is your unique record to identify your account. This ID should also be in your CRM.

Optional Fields:

• Name (string)
• NextRenewalDate (date)
• TotalContractAmount (double)
• IsActive (Boolean)
• BillingAddressLine1 (string)
• BillingAddressLine2 (string)
• BillingAddressCity (string)
• BillingAddressState (string)
• BillingAddressZip (string)
• BillingAddressCountry (string)
• StartDate (datetime)
• EndDate (datetime)
• LicenseCount (int)
• OwnerUserAccount (string - matches on UserName of the ChurnZero user)
• ParentAccountExternalId (string)
• cf_XXXX The custom field to be updated prefixed by "cf_"

To see a list of the custom fields with their corresponding CSV Column Header label on your accounts, click on Data > Imports, then select Account from the Entity drop-down. Make sure that your .csv file contains the exact naming convention that is shown in CSV Column Header.

Note: A custom field must already exist in ChurnZero in order for attribute values to be sent via CSV. Also, if the column headers exist in the import file, the value will be updated accordingly. So, if you include a header with blank values underneath it, the values will be wiped out to null or cleared out. If you need help getting a field added, ask support@churnzero.net for help.

Contact Imports

Follow the steps in the "How to Import" section. Below you will find the required and optional fields for the Contact entity.

Required Fields: 

• contactExternalId (string) - The ContactExternalId must be unique within the account. This could be an email address, a unique record that is also contained in your CRM, or the ID of the contact record of your CRM.
• accountExternalId (string) - The accountExternalId is your unique record to identify your account. This ID should also be in your CRM.

Optional Fields:

• FirstName (string)
• LastName (string)
• Email (string)
• cf_XXXX The custom field to be updated prefixed by "cf_".

To see a list of the custom fields with their corresponding CSV Column Header label on your accounts, click on Data > Imports, then select Contacts from the Entity drop-down. Make sure that your .csv file contains the exact naming convention that is shown in CSV Column Header.

Note: A custom field must already exist in ChurnZero in order for attribute values to be sent via CSV. Also, if the column headers exist in the import file, the value will be updated accordingly. So, if you include a header with blank values underneath it, the values will be wiped out to null or cleared out. If you need help getting a field added, ask support@churnzero.net for help.

Event Imports

NOTE: By default, ChurnZero ignores duplicate events (same Date, Account, Contact, and Description). You can allow duplicates by toggling "Allow Duplicates" to YES. This function will cross check with Events that already exist in ChurnZero. It will not check for duplicates in the CSV file being submitted.

Required Fields: 

• accountExternalId (string) - The accountExternalId is your unique record to identify your account. This ID should also be in your CRM.
• contactExternalId (string) - The ContactExternalId must be unique within the account. This could be an email address, a unique record that is also contained in your CRM, or the ID of the contact record of your CRM.
• EventName (string) - This is the unique name of the event (ie. "Sent Blog Post"). If theEvent Name is not found it will be created.
• EventDate - The date of the event (defaults to time of API call) in format ISO-8601 ("2012-03-19T07:22Z")

Optional Fields:

• Description (string) - A description of this particular event (ie. blog title)
• Quantity (number) - The number related to this event. (ie. Commonly used to track things like email sent, etc)
• cf_XXXX The custom field to be updated prefixed by "cf_".
• Custom Fields on Events are not a common occurrence. Do not be alarmed if your account has no Event Custom Fields. 

To see a list of the custom fields with their corresponding CSV Column Header label on your accounts, click on Data > Imports, then select Event from the Entity drop-down. Make sure that your .csv file contains the exact naming convention that is shown in CSV Column Header.

Note: A custom field must already exist in ChurnZero in order for attribute values to be sent via CSV. Also, if the column headers exist in the import file, the value will be updated accordingly. So, if you include a header with blank values underneath it, the values will be wiped out to null or cleared out. If you need help getting a field added, ask support@churnzero.net for help.

Activity Imports

Follow the steps in the "How to Import" section. Below you will find the required and optional fields for the Activity entity.

Required Fields: 

• accountExternalId (string) - The accountExternalId is your unique record to identify your account. This ID should also be in your CRM.
• assignedTo (string) - The assignedTo field references the user account that the activity is assigned to. This should match on UserAccount.UserName.
• subject (string) - The subject of this particular activity
• Comments (string) - Refers to any comments associated with the activity.
• activityStatus (picklist)- The type must be designated from the list of activity types in your instance.
• dueDate (date)- The due date of an open activity. This is required if you want the activity to be brought in as Due/Upcoming.
• closeDate (date) - The date that the activity was closed/logged. This is required if you want the activity to be brought in as Completed/Logged.

Optional Fields:

• contactExternalId (string) - The ContactExternalId must be unique within the account. This could be an email address, a unique record that is also contained in your CRM, or the ID of the contact record of your CRM.
• Type (picklist) - The type must be designated from the list of activity types in your instance.
• cf_XXXX The custom field to be updated prefixed by "cf_".
  • Custom Fields on Events are not a common occurrence. Do not be alarmed if your account has no Activity Custom Fields. 

To see a list of the custom fields with their corresponding CSV Column Header label on your accounts, click on Data > Imports, then select Activity from the Entity drop-down. Make sure that your .csv file contains the exact naming convention that is shown in CSV Column Header.

Note: A custom field must already exist in ChurnZero in order for attribute values to be sent via CSV. Also, if the column headers exist in the import file, the value will be updated accordingly. So, if you include a header with blank values underneath it, the values will be wiped out to null or cleared out. If you need help getting a field added, ask support@churnzero.net for help.

 

Survey Imports

Below you will find the required and optional fields, as well as more information on the Survey entity.

1. Follow the steps in the "How to Import" section. In addition, you will:
2. Designate which type of survey you are importing (NPS, CSAT or CES) in the Survey field
3. Enter a name and description for your survey, which will appear in the UI
4. Designate whether the survey contains follow-up questions.
   • Along with including follow-up questions, you can designate if those questions are the same for all ratings.
   • If the questions are not the same, you can make selections for each question depending on the type of responder organized by rating, as shown below:

Required Fields: 

• accountExternalId (string) - The accountExternalId is your unique record to identify your account. This ID should also be in your CRM.
• contactExternalId (string) - The ContactExternalId must be unique within the account. This could be an email address, a unique record that is also contained in your CRM, or the ID of the contact record of your CRM.
• Rating (number) - The number rating associated with responses to your survey. For many survey types, this will be the "Score" field. 
• ResponseDate (datetime) - The date and time associated with your survey responses.

Optional Fields:

• FollowUpResponse (data type varies) - This field can be included if you have follow-up questions associated with your survey.

To see a list of the custom fields with their corresponding CSV Column Header label on your accounts, click on Data > Imports, then select Survey from the Entity drop-down. Make sure that your .csv file contains the exact naming convention that is shown in CSV Column Header.

 

Custom Table Imports

A Custom Table is anything that appears on the custom tables of an account within ChurnZero.

Required Fields: 

• accountExternalId (string) - The accountExternalId is your unique record to identify your account. This ID should also be in your CRM. This will allow the Custom Table to show on the correct account within ChurnZero
• Identifier- Each record in your Custom Table should have an identifier associated with it. The Identifier can be anything that your team chooses, as long as it's unique per record on the Custom Table. This identifier will allow the record on the Custom Table to be updated with future imports, rather than creating a new record on the Custom Table. You will need to let your Customer Success Manager or Implementation Specialist know what you have chosen as your Identifier field so that the field can be configured appropriately.  

To see a list of the custom fields with their corresponding CSV Column Header label on your accounts, click on Data > Imports, then select the custom table from the Entity drop-down. Make sure that your .csv file contains the exact naming convention that is shown in CSV Column Header.

Note: A custom field must already exist in ChurnZero in order for attribute values to be sent via CSV. Also, if the column headers exist in the import file, the value will be updated accordingly. So, if you include a header with blank values underneath it, the values will be wiped out to null or cleared out. If you need help getting a field added, ask support@churnzero.net for help.