> For the complete documentation index, see [llms.txt](https://docs.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.distro.so/records/import-csv.md).

# Import a CSV

Use **Records → People** or **Companies → Import CSV**. An admin uploads the file, checks the column mapping and then starts the import.

## Prepare the file

Use a UTF-8 CSV with a header row. The upload can be up to **10 MB**; an import processes up to **50,000 rows**. For People, include an email column. For Companies, include a domain column.

For example:

```csv
email,first_name,title,company
alex@example.com,Alex,Head of Sales,Example
```

## Check the mapping

1. Select the file and continue to **Match columns**.
2. Map exactly one column to **email** or **domain**, depending on the record type.
3. Review the proposed fields and confidence. A suggested match still needs your review.
4. Choose **skip** for columns you do not want to import.
5. Use lowercase field names containing letters, numbers and underscores. Do not map two columns to the same field.
6. Select **Lock mapping and import**.

The locked mapping is used for that import. You cannot rerun the same locked import with a different mapping; correct the file and create a new import.

## Review the result

Return to Records and search for a few known identities. Check the imported and skipped counts. Blank cells do not erase existing values. Rows without a valid identity may be skipped.

Importing a file fills Distro records. To write imported fields to an existing CRM record, use [Link to CRM](/records/link-to-crm.md) and [Push to CRM](/records/push-to-crm.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.distro.so/records/import-csv.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.