Importing files
Importing files
# Overview
You can import your data via CSV imports, which you can upload in the Integrations > Imports section of the vertical menu. Four imports are available: customers, contacts, contracts and team.
The structure of expected files is described below :
- 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:
# CSV Import Guidelines
# File Format
| FORMAT | CSV |
|---|---|
| SEPARATOR | Comma (",") |
| HEADER | The first line of the file must contain the column headers |
# Expected Files
# 1. Customer File Structure
Info
If you perform multiple uploads, only new customers will be created; existing customers will be updated.
Tips
Account hierarchy If you want to import multiple hierarchical levels of accounts, perform several imports: first the parent accounts only, then the "intermediate" accounts, then the child accounts if you have 3 hierarchical levels.
Info
All your custom fields can also be added to your import file. Just keep the column label as the name of the field you created.
| Expected Fields | Description | Type | Sample Value / Comments |
|---|---|---|---|
| Name* | Customer name | Alphanumeric | |
| Domain | Customer domain name | Alphanumeric | google.com |
| Customer ID | Internal identifier (e.g., BO or CRM) | Alphanumeric | |
| Description | Free text with data on the customer | Alphanumeric | |
| CSM Pulse | Healthscore according to the CSM | Numeric | 1–5 |
| Owner email | Account owner's email | Alphanumeric | john.doe@mondomain.com |
| Team members emails | Account contributors' emails (except owner) | Alphanumeric (comma-separated) | |
| Tags | Keywords assigned to the account | Alphanumeric (comma-separated) | |
| Stage | Lifecycle stage | Alphanumeric | Trial, Onboarding, Run (stages must be created in platform) |
| Health score profile | Account assignment group for Health-score | Alphanumeric | Must be pre-created in platform |
| Parent customer | Name of the parent if the created account is a child | Alphanumeric | The parent must be created first in Skalin |
| Interaction goal | Target interaction group | Alphanumeric | Must be pre-created in platform |
| Deleted | Allows deletion of customers | Numeric | 1 or “true” to delete |
- Note: Column order is flexible but respecting titles is recommended for auto-mapping.
- Fields with * are mandatory.
- Bold fields are merge fields.
# 2. Contacts File Structure
Info
Multiple uploads: only new contacts are created; existing contacts are updated.
Info
All your custom fields can also be added to your import file. Just keep the column label as the name of the field you created.
| Expected Fields | Description | Type | Sample Value / Comments |
|---|---|---|---|
| Contact ID | Unique identifier (BO or CRM) | Alphanumeric | |
| Email* | Contact's email | Alphanumeric | |
| Additional emails | Other emails (aliases) | Alphanumeric (comma-separated) | |
| Customer ID/Customer domain | Parent customer's ID or domain | Alphanumeric | google.com |
| Phone | Contact's phone number | Alphanumeric | +33 6 45 87 45 63 |
| Firstname | Contact's first name | Alphanumeric | |
| Lastname | Contact's last name | Alphanumeric | |
| Tags | Keywords assigned to contact | Alphanumeric (comma-separated) | 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 | MALE, FEMALE |
| Role | Role in platform | Alphanumeric | admin, user |
| NPS Score | Contact's NPS score (link to a CRM field or populate via the API) | Numeric | 1 to 10 |
| Deleted | Allows deletion of the corresponding contact | Numeric | 1 or “true” to delete |
# 3. Agreement File Structure
Info
All your custom fields can also be added to your import file. Just keep the column label as the name of the field you created.
| Expected Fields | Description | Type | Sample Value / Comments |
|---|---|---|---|
| Customer ID/Customer domain | Parent customer ID or domain | Alphanumeric | google.com |
| Agreement type* | Type of agreement | Alphanumeric | INITIAL, RENEW, AMENDMENT, SERVICE, OTHER |
| Agreement ID | Agreement ID from Stripe, Chargebee, your CRM or manually added | Numeric | 5541268 |
| Plan | Subscribed offer | Alphanumeric | Basic |
| Start date* | Agreement start date | YYYY/MM/DD or DD/MM/YYYY | |
| Monthly fee* | Monthly subscription amount | Numeric (decimal with ".") | |
| One-time fee | Setup/service amount | Numeric (decimal with ".") | |
| Duration* | Agreement duration | Numeric | 1 |
| Duration period* | Duration unit | Alphanumeric | DAY, WEEK, MONTH, YEAR |
| Notice* | Notice duration | Numeric | 3 |
| Notice period* | Notice period unit | Alphanumeric | DAY, WEEK, MONTH, YEAR |
| Auto-renew* | Indicates automatic renewal | Numeric | 1 or “true” |
Notes:
- Column order is flexible but respecting titles is recommended for auto-mapping.
- Fields with * are mandatory (** only one of the fields is required).
- Bold fields are merge fields.
Agreement ID
If you are planning on importing the agreement CSV several times in a row, do not forget to add an agreement ID from the first import so that you modify data instead of creating duplicates.