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

# Exporting Your Data

If you are an admin, you can export selected Collective data from the Open Collective platform for use elsewhere.

We offer the option to export and download certain data from your Collective and Collectives that your Fiscal Host supports for use outside the platform. Collective and fiscal host admins, as well as users with the Accountant role, can request and download exports for accounts they can access.

Accountants can request, view, download, and rename exports. Only admins can delete an export.

If you want to know how to export data to display on your website, go to the [Adding Embeds to your Website](https://documentation.opencollective.com/collectives/raising-money/adding-embeds-to-your-website.md) page.

### Export Transactions

Go to your Collective or Fiscal Host's Dashboard > Transactions and click "Export CSV" in the top right.

You can download a CSV file of all transactions or use the filters to choose which groups of transactions to download, like expenses or contributions.

By default, the platform will select the "Platform Default" export set, but if you'd like to add or remove filters and categories, click the drop down and then "New Preset."

#### Background (async) exports

Transaction exports are processed in the background for the following accounts:

* Collectives, Projects, and Events
* Organizations with money management enabled (fiscal hosts)

Background exports are available to admins and accountants of the account, of its parent account (for Projects and Events), or of its fiscal host. For these users, the export window shows a **Generate Export** button and lets you name the export. There is no 100,000-row limit on background exports.

Open the **Exports** section of your dashboard to check the status of an export and download completed files. You will also receive an email with a link to the export when it is ready.

Other accounts (for example, Organizations without money management and individual profiles) and other viewers keep the direct CSV download.

{% hint style="info" %}
If an export fails, the platform automatically retries it a limited number of times before marking it as failed.
{% endhint %}

### Export Contributors

Go to your Collective or Fiscal Host's Dashboard > Contributors and click "Export CSV" in the top right.

### Export Collectives

Go to your Collective or Fiscal Host's Dashboard > Collectives and click "Export CSV" in the top right.

By default, the platform will select the "Platform Default" export set, but if you'd like to add or remove fields like Name or Currency, click the drop down and then "New Preset."

### Export data as JSON files

You can also export your data as a JSON file, which can be used with other applications. The information you download can be filtered by:

Options:

* All members (contributors of all types)
* Only users (individuals)
* Only organizations

Parameters:

* limit: number of members to return
* offset: number of members to skip (for paging)
* TierId: only return the members within a certain Tier. You can find the Tier ID by viewing the URL that comes up when you select a tier on your Collective page


---

# 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://documentation.opencollective.com/advanced/exporting-your-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.
