Importing files
Importing files
# Overview
You can import your data via CSV imports, which you can upload in the Settings > Imports section of the vertical menu. Four imports are available: customers, contacts, contracts and team.
The structure of expected files is described in the technical documentation :
- Expected file structure for customers
- Expected file structure for contacts
- Expected file structure for agreement
Note that the order of the columns is not important; it's the headings that enable us to identify and match the information during import. If the headings are different, you'll simply have to map the fields manually.
All files must respect the following format:
| FORMAT | Fichier CSV |
| SEPARATOR | Comma (“,”) |
| HEADER | The first line of the file must contain the column header |
# Expected files
# Customer file structure
Info
If you perform several successive uploads, only new customers will be created while existing customers will be updated.
| Expected fields | Description | Type | Sample value / comments |
|---|---|---|---|
| Name* | Customer name | Alphanumeric | |
| Domain* | Customer domain name | Alphanumeric | google.com |
| Customer ID | Internal identifier (e.g. that of your BO or CRM) | Alphanumeric | |
| CSM Pulse | Healthscore according to the CSM | Numeric | Entier entre 1 et 5 |
| Owner email | Account owner's email | Alphanumeric | john.doe@mondomain.com |
| Team members emails | Account contributors's e-mail (except owner) | Alphanumeric (if several addresses, separate the values by a comma) | |
| Tags | Tags ( = keywords) assigned to the account | Alphanumeric (if several addresses, separate the values by a comma) | |
| Stage | Life cycle stage | Alphanumeric | Trial, onboarding, run: the “stages” must first be created in the platform |
| Health score profile | Defines the account assignment group for the calculation of the Health-score | Alphanumeric | The “health score profile” must first be created in theplatform |
| Interaction goal | Defines the group account assignment in terms of target interactions | Alphanumeric | The “health score profile” must first be created in the platform |
| Deleted | Allows the deletion ofclients | Numeric | 1 or “true” to delete the account |
The column order is free but it it is preferable to respect the titles (auto-mapping).
The fields followed by an * are compulsory (** only one of the fields is required).
The fields in bold are the merge fields
# Contacts file structure
Info
If you carry out several successive uploads, only new contacts will be created while existing contacts will be updated.
| Expected fields | Description | Type | Sample value / comments |
|---|---|---|---|
| Contact ID | Unique identifier of the contact (eg that of your BO or CRM) | Alphanumeric | |
| Email* | Contact's email | Alphanumeric | |
| Additional emails | Other emails of the contact (alias…) | Alphanumeric (if several addresses, separate the values with a comma) | |
| Customer ID** | Contact's Customer Identifier (eg that of your BO or CRM) | Alphanumeric | |
| Customer domain** | Contact's Customer domain. | Alphanumeric | google.com |
| Phone | Contact's phone number | Alphanumeric | +33 6 45 87 45 63 |
| Firstname | Contact's firstname | Alphanumeric | |
| Lastname | Contact's lastname | Alphanumeric | |
| Tags | Tags (= mots-clés) assigned to contact | Alphanumeric (if several addresses, separate the values by a comma)/td> | SPONSOR, KEY USER, CHAMPION, END USER |
| Job title | Job title | Alphanumeric | Chief Marketing Officer |
| Language | Contact's language | Alphanumeric | FR |
| Gender | Contact's gender | Alphanumeric | Available values: MALE or FEMALE |
| Role | Contact's role in your plateform | Alphanumeric | admin, user |
| NPS Score | Relationship Evaluation by the CSM | Alphanumeric | Entier entre 1 et 5 |
| Deleted | Used to delete contacts | Numeric | 1 ou “true” to delete contact |
# Agreement file structure
| Expected fields | Description | Type | Sample value / comments |
|---|---|---|---|
| Customer ID** | Identifier of the home Customer of the agreement (eg that of your BO or CRM) | Alphanumeric | |
| Customer domain** | Name of the home Customer of the Agreement. | Alphanumeric | google.com |
| Agreement type* | Agreement type | Alphanumeric | Available values: 'INITIAL', 'RENEW', 'AMENDMENT', 'SERVICE', 'OTHER' |
| Plan | Offer subscribed by the customer | Alphanumeric | Basic |
| Start date* | Agreement start date Available | Allowed formats : YYYY/MM/DD ou DD/MM/AAAA | |
| Monthly fee* | Amount of the monthly subscription | Numeric (decimals separated by a “.”) | |
| One-time fee | Amount of the setup (or service provision) | Numeric (decimals separated by a “.”) | |
| Duration* | Agreement duration | Numeric | 1 |
| Duration period* | In days / weeks / year | Alphanumeric | Available values:'DAY', 'WEEK', 'MONTH', 'YEAR' |
| Notice* | Notice duration | Numeric | 3 |
| Notice period* | In days / weeks / year | Alphanumeric | Available values: 'DAY', 'WEEK', 'MONTH', 'YEAR' |
| Auto-renew* | Indicates whether the contract includes an identical tacit renewal | Numeric | 1 or “true” if true |
The column order is free but it it is preferable to respect the titles (auto-mapping).
The fields followed by an * are compulsory (** only one of the fields is required).
The fields in bold are the merge fields