> For the complete documentation index, see [llms.txt](https://doc.batch.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.batch.com/getting-started/other/faq/changes-to-data-exports-export-api-and-custom-exports.md).

# Changes to data exports (Export API & custom exports)

As part of our platform migration, the **data source** used for exports is evolving. This page explains what stays the same and what will change for your exports, whether they run through the **Export API** or as a **custom export**.

## What isn't changing

We've done compatibility work to guarantee full continuity of your exports:

* your exports keep running with no interruption;
* the **format** of the files and responses stays identical;
* no action is required on your side to maintain your existing flows.

This remains true even after the legacy installation bases (MEP/legacy) are retired and the v1 push is discontinued.

## What will change

Starting **`[DATE — TBD]`**, the data source for exports will switch from the installation base to the **Profiles** base. The flow and format are preserved, but this change of source introduces a few functional differences to anticipate.

### 1. Advertising ID (IDFA/GAID) — empty values

The Advertising ID (IDFA/GAID) is no longer indexed in the new source, so the corresponding field will always be returned empty in your exports.

### 2. Smart Segments — empty values

Smart Segments are no longer available for export and will return empty values.

### 3. Exported volumes — likely decrease

The number of exported profiles (both API and custom exports) will likely decrease. By default, the Profiles base only retains **profiles active over the last 13 months**; profiles that have been inactive for longer are no longer included in exports. This retention period (TTL) is **configurable on request** — contact your CSM if you need a longer window.

## When?

This change takes effect on **`[DATE — TBD]`**. Until then, nothing changes for your exports.

## Questions?

For any question about the impact on your use case, or to adjust the retention period, reach out to your CSM.


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://doc.batch.com/getting-started/other/faq/changes-to-data-exports-export-api-and-custom-exports.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.