Importing from CSV

The steps

1. Open a list, e.g. Clients, and click Import CSV. You need to be able to edit records.
2. Choose a file: a CSV with a header row, up to 10 MB and 20,000 rows. Commas, semicolons and tabs all work; save it as UTF-8.
3. Match columns to fields. Columns are matched automatically when the header is the field's label or key; change or skip any of them.
4. Update existing records: tick the fields that identify a record (by default the unique fields, otherwise the name). A row whose values match an existing record in all ticked fields updates it; other rows create new records. Tick nothing to always create.
5. Preview shows what each row will do: create, update, or an error with the reason.
6. Import. Rows are saved in batches of 500; a row that fails never stops the others. Afterwards you can download the error rows as a CSV, fix them and import that file.

Column formats

• Numbers and money: 48000, 48,000 or $48,000. Percent: 12.5.
• Dates: 2026-12-15 (YYYY-MM-DD) is safest.
• Yes/no: yes, no, true, false, 1, 0 or x.
• Picklists: one of the field's values (capitals don't matter). Several values: separate them with ;.
• Links (e.g. a contact's client): the linked record's name, id, or a unique value such as its number.
• People (e.g. owner): their email address or full name, as in the workspace.

Empty cells are skipped, so an update never clears a value you left blank.

What can't be imported

• Calculated fields (formulas, roll-ups and fields from linked records) and the health score: they're worked out by XPI CRM.
• Files: add them on the record page.

After the import

Each change appears in the record's history as “via import”. Playbook rules run exactly as if the records had been saved in the app — for example, an imported client with Health “At Risk” starts your at-risk playbook.

To connect another tool instead of uploading files, see the REST API reference.