CSV
If you have data that you're not able to import through the use of our integrations or API, we may be able to help you import this data for you via CSV file. Please read the notes below and contact your Vitally CSM or Vitally support for assistance.
Accounts and account traits
Users and user traits
NPS responses
If you have any other types of data that you would like our help importing into your Vitally account, please reach out to your CSM and we'd be happy to evaluate your request.
Below are examples of the columns required for each type of import.
The only required column to import Account data is the externalID field. This is the primary id used to identify all of your accounts in Vitally. It's important that this identifier match the existing external IDs used in Vitally in order to prevent duplicating your data. For more on External IDs, see The significance of 'external ID'. Insert any additional account traits you would like to import as new columns
externalId | industry | phoneNumber |
47594e998e26 | Software | 5551118888 |
There are two required fields to import user data. These consist of the user's External ID, and the External ID of the account they should belong to. It's important that these identifiers match the existing external IDs used in Vitally in order to prevent duplicating your data. For more on External IDs, see The significance of 'external ID'. Insert any additional user traits you would like to import as new columns.
accountId | userId | role | |
47594e998e26 | 3572f345n33 | Owner |
If you wish to import historical NPS scores into Vitally, we can help you get these imported into Vitally. For NPS records, you can send either the user's email address or external ID; only one of the two are required. The other required fields can be found below.
externalID | score | feedback | uniqueID | timestamp | |
3572f345n33 | 8 | I love Vitally! | abc1245 | 2020-08-13T14:08:50.000Z |
Please limit requests to import CSV files to 2 requests per month, per customer. This service is offered as a courtesy, but we'd much prefer you use our integrations and API when possible.
