> For the complete documentation index, see [llms.txt](https://docs.zero.inc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zero.inc/settings/exporting-data.md).

# Exporting Data

Any list exports to CSV from the list view itself. What you get is what you are looking at — the rows and columns of the current view, filters included — and every export is recorded in the list's Import/Export history.

## Export a list as CSV

{% stepper %}
{% step %}
Open the list, click the **⋯** menu in the top right, and choose **Export as CSV** under **Import & Export**. The same menu exists on a sequence's **Contacts** page.
{% endstep %}

{% step %}
The modal takes three things:

* **Filename** — defaults to `<List name> - <View name> - <YYYY-MM-DD>.csv`; edit it freely.
* **Delimiter** — **Comma** (default), **Semicolon**, **Tab**, or **Space**.
* **Columns** — a multi-select of the columns in your current view, all selected by default. A **Name** column for the record itself is always offered first. Deselect anything you don't want in the file.

<figure><img src="https://storage.googleapis.com/zero-production-api-docs/images/export-modal.png" alt="Export dialog with a filename field, delimiter options and a removable chip for each column included in the CSV"><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Click **Download CSV**. Browsers that support it open a save dialog with the suggested filename; the rest download straight away.
{% endstep %}
{% endstepper %}

## What gets exported

The rows currently in the view — so the view's filters are the export's filters — and the columns you picked, with a header row on the first line. **Intent** and **Usage** are never written to the file even if selected.

Values come out readable rather than as raw IDs:

* **Select** and **multi-select** properties export their option labels; multiple values are joined with `,` .
* **User** properties export the user's name (multiple users joined with `,` ).
* **Pipeline** and **stage** columns export the pipeline and stage names.
* **Location** properties export their parts (city, state, country, …) joined with `,` .
* Linked records (for example a contact's companies) export their names, joined with `,` .
* **LinkedIn** values stored as usernames are expanded to full `https://www.linkedin.com/in/...` URLs.
* An **Open tasks** column is split into two CSV columns: **Next Steps** (task names) and **Next Steps Deadline** (task deadlines, `N/A` when a task has none).
* Values containing the delimiter, quotes, or line breaks are quoted and escaped following standard CSV rules, so the file can be re-imported cleanly. Zero's [CSV import](/getting-started/data-import/csv-import.md) auto-detects the delimiter.

## Export history

Every export is logged with its filename, entity and row count. **Import/Export history** in the same **⋯** menu shows the list's **Imports** and **Exports**; expanding an entry gives you **Exported by**, **Exported rows**, and when it ran.

History is private to whoever ran it — you see your own runs, not your teammates'.


---

# 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 by asking a question.

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

```
GET https://docs.zero.inc/settings/exporting-data.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 `automate deployments from our CI pipeline` 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.