How to import data
Last updated: November 9, 2026
You can import your existing cases into Ondorse in bulk, with their related natural persons and documents. You upload one file per type of data (.csv or .xlsx, plus a .zip for document files). Ondorse validates each file and imports the valid rows. You can then fix the rows that failed and re-upload only those.

Overview
Copy the import template and fill one tab per type of data.
Go to Settings > Data > Import / export, tab Import.
Upload your files in this order: cases, then related natural persons, then documents.
Check the result of each import and fix failed rows with the Error report.
1. Prepare your files with the template
Start by copying our import template.

Each tab of the template matches one section of the Import page:
Template tab | Import section | Use it for |
|---|---|---|
Business cases | Business cases | Cases whose subject is a business (KYB) |
Natural person cases | Natural person cases | Cases whose subject is a natural person (KYC) |
Related persons | Related natural persons | Persons attached to your business cases (UBOs, shareholders, legal representatives…) |
Documents | Documents | Documents attached to cases or persons, with a .zip of the document files |
The tabs prefixed ref: list the accepted values for some columns, such as legal types.
Column names don't have to match the template exactly: you can remap them during the import.
2. Format of each file
Business cases
Column | Description | Constraint |
|---|---|---|
| Your reference for the customer or case (account ID, client ID…). The other files use it to point to this case. | Required. Unique within your account. |
| Registration country of the company | Required. ISO 3166 alpha-3 code, e.g. FRA, GBR |
| Registration number of the company | Required |
| Name of the company | Required |
| Legal form of the company | Required. One of the values in the ref: legal types tab |
| Date the customer was onboarded, e.g. date of first KYC or start of the business relationship | YYYY-MM-DD |
| Address of the company | See Address format |
| Value of a custom field. Replace XXX with the custom field's API field name (Settings > Data > Custom fields). Add one column per custom field. | Must match the custom field's type, e.g. one of its dropdown values |

Natural person cases
Column | Description | Constraint |
|---|---|---|
| Your reference for the customer (account ID, client ID…) | Required. Unique within your account. |
| Value of a custom field, XXX being its API field name. Add one column per custom field. | Must match the custom field's type |
Fill the other columns of the Natural person cases template tab (identity, address) the same way as for related natural persons below.
Related natural persons
Column | Description | Constraint |
|---|---|---|
| Your reference for the person. If you have none, use any unique identifier. | Required |
| The | Required |
| First name(s) of the person | |
| Last name of the person | |
| Date of birth | |
| City of birth | |
| Email address of the person | |
| The person is the signatory of the case | TRUE or FALSE |
| The person is an ultimate beneficial owner | TRUE or FALSE |
| The person is a shareholder | TRUE or FALSE |
| The person is a legal representative | TRUE or FALSE |
| Address of the person | See Address format |
Documents
Upload this file together with a .zip file containing the document files. The path_to_file column points to each file in the .zip.
Column | Description | Constraint |
|---|---|---|
| Your reference for the document. If you have none, use any unique identifier. | Required |
| The | Required if no |
| The | Required if no |
| Path of the file in the .zip. Example: for | Required |
| The expected document of your account this document corresponds to | ID of the expected document |
| Issuing country of the document | ISO 3166 alpha-3 code, e.g. FRA, GBR |
| Expiry date of the document |
Address format
Addresses can use one of two formats. Set the format in the address_type column.
Single line: the whole address in one column.
Column | Constraint |
|---|---|
|
|
| Full address on one line (street, postal code, city) |
| ISO 3166 alpha-3 code, e.g. FRA, GBR |
Multi-line: one column per component.
Column | Constraint |
|---|---|
|
|
| Street and number |
| City |
| Postal code |
| ISO 3166 alpha-3 code, e.g. FRA, GBR |
3. Upload your files
Go to Settings > Data > Import / export and open the Import tab.
Upload your files in the matching sections, in this order (persons and documents refer to cases that must already exist):
Business cases and/or Natural person cases: your cases file (.csv or .xlsx).
Related natural persons: your persons file (.csv or .xlsx).
Documents: your documents file (.csv or .xlsx), then the .zip of document files.
Map your columns if their names differ from the template, then confirm. Ondorse validates the file before importing it.


4. Check the result and fix errors
Each import appears in the list under its section:
Import: in progress while it runs.
Once done: the import date, the number of rows, and how many were imported and failed.
If some rows failed, you don't need to start over:
Click Error report to download a file with only the failed rows, and the reason for each error in a dedicated column.
Fix the errors directly in that file.
Upload it again in the same section. Only these rows are imported.
Repeat until all rows are imported.


If the report can't be generated, the import shows Report unavailable: contact support@ondorse.co.
To import your configuration (workflow, rules, custom fields…) rather than your data, see How to export and import configuration between environments.