> For the complete documentation index, see [llms.txt](https://docs.mediarithmics.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mediarithmics.io/setup-and-monitor/collect-and-manage-your-data/export-your-data.md).

# Export your data

The ways data leaves the platform, and how to pick between them.

## Your goal

Get data out of the datamart to the right place, in the right form - a file for a partner, a stream for your cloud, a one-off extract for an analyst.

## Expected outcome

An export route chosen deliberately, rather than one built ad hoc because it was the first thing that worked.

## Pick a route

| You want                                                                          | Use                                                       | Where it is documented                                                                                             |
| --------------------------------------------------------------------------------- | --------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ |
| A one-off or scheduled extract of query results, as `ndjson`                      | **Query export**                                          | [Export](/setup-and-monitor/collect-and-manage-your-data/export-your-data/export.md)                               |
| Files delivered to SFTP, S3, or Google Cloud Storage - typically to a partner     | **File destination**                                      | [File destination](/setup-and-monitor/collect-and-manage-your-data/export-your-data/file-destination.md)           |
| Every ingested change streamed to your own cloud, continuously                    | **Datamart replication**                                  | [Datamart replication](/setup-and-monitor/collect-and-manage-your-data/export-your-data/datamart-replication.md)   |
| Data landing in your cloud data warehouse, as tables                              | **A data warehouse replication** to BigQuery or Snowflake | [Data warehouse export](/setup-and-monitor/collect-and-manage-your-data/export-your-data/data-warehouse-export.md) |
| Audience segments pushed to a partner's solution, kept recurring and synchronised | **Audience feeds**                                        | The `Audience & Activation` section                                                                                |

```mermaid
flowchart LR
    DM[("Datamart")]
    Q["Query export<br/>ndjson from an OTQL query"]
    F["File destination<br/>SFTP, S3, GCS"]
    R["Datamart replication<br/>message queues"]
    W["Datamart replication<br/>data warehouses"]
    A["Audience feeds"]
    DM --> Q
    DM --> F
    DM --> R
    DM --> W
    DM --> A
    Q --> AN["Analysts, one-off needs"]
    F --> P["Partners, custom connectors"]
    R --> C["Your cloud, continuous"]
    W --> T["BigQuery, Snowflake tables"]
    A --> D["Activation platforms"]
```

## How they differ

|                      | Query export                     | File destination                                | Datamart replication                                                   |
| -------------------- | -------------------------------- | ----------------------------------------------- | ---------------------------------------------------------------------- |
| Triggered by         | You, per execution               | A feed writing to it                            | Ingestion, continuously                                                |
| Output               | One `ndjson` file per execution  | Aggregated files, on size or frequency triggers | A message per `update` or `delete` operation                           |
| Content              | Whatever your OTQL query selects | Whatever the feed streams                       | The objects you selected at creation                                   |
| Destination          | Downloaded from the platform     | SFTP, S3, Google Cloud Storage                  | Google Pub/Sub, Microsoft Azure Event Hubs, Google BigQuery, Snowflake |
| Available by default | Yes                              | Yes                                             | **No** - contact your account manager                                  |

## Before you export anything

{% hint style="warning" %}
Exports move personal data outside the platform, where the platform's own controls no longer apply. Two things to settle first:

* **Which processing activity justifies the export**, and whether the users concerned have accepted it. See [Manage consent & Processing activities](/setup-and-monitor/ensure-privacy-and-compliance/manage-consent-and-processing-activities.md).
* **What happens to the data at the destination** - retention there is your responsibility, not the platform's. See [Data retention](/setup-and-monitor/plan-and-integrate/set-up-the-environment/manage-data-retention.md).
  {% endhint %}

## In this section

<table data-view="cards" data-search="false"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Export</strong></td><td>Query exports: definitions, executions, downloads.</td><td><a href="/setup-and-monitor/collect-and-manage-your-data/export-your-data/export.md">Export</a></td></tr><tr><td><strong>File destination</strong></td><td>Where and how generated files are delivered.</td><td><a href="/setup-and-monitor/collect-and-manage-your-data/export-your-data/file-destination.md">File destination</a></td></tr><tr><td><strong>Datamart replication</strong></td><td>Streaming every change to your cloud.</td><td><a href="/setup-and-monitor/collect-and-manage-your-data/export-your-data/datamart-replication.md">Datamart replication</a></td></tr><tr><td><strong>Data warehouse export</strong></td><td>Replicating documents into BigQuery or Snowflake.</td><td><a href="/setup-and-monitor/collect-and-manage-your-data/export-your-data/data-warehouse-export.md">Data warehouse export</a></td></tr></tbody></table>


---

# 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.mediarithmics.io/setup-and-monitor/collect-and-manage-your-data/export-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.