Skip to main content
Your event and profile data belongs to you, and you can take a full copy of it out of Mixpanel at any time. Use this page when you want a backup, a copy in your own warehouse, or everything you need to move to another tool. For request parameters and response formats, follow the links to the API reference.

​
What You Can Export

You can also download smaller sets of events, profiles, and report results as CSV from the UI. See Export Methods for every option, including report exports.

​
Plan Availability

Data Pipelines comes with a 30-day trial. See how the trial works for its limits.
A few projects on older Free plans don’t include the Raw Event Export API. If the API returns “Your plan does not support raw data export”, contact support.

​
Rate Limits

Export limits apply per project. The Raw Event Export API limits are the same on every plan. If you go over a limit, the API returns a 429 error. See Rate Limits for details.

​
Data Retention

Mixpanel deletes events 2 years after the event date. Projects created before September 1, 2025 keep events for 5 years, until the project changes plan or moves to the Free plan. After that, the 2-year period applies. If you want to keep history older than your retention period, export it before it ages out. User data is kept for the duration of an active subscription plan. Read the full data retention policy.

​
Export Everything at Once

This recipe takes a one-time copy of a whole project: events, user profiles, and group profiles.
1

Set up authentication

Create a service account with access to the project, or use your project secret. With a service account, include project_id in every request. If your project has classified data, the service account needs permission to access it. See Raw Event Export authentication.
2

Pick your server

For the Raw Event Export API, use data.mixpanel.com for most projects. Use data-eu.mixpanel.com if your project is in EU Data Residency, or data-in.mixpanel.com for India Data Residency.
3

Export events in date ranges

Split your history into date ranges and send one Raw Event Export request per range. Smaller ranges are easier to retry if a request fails. Each response is JSONL, with one event per line.
Raw exports aren’t deduplicated. Deduplicate on event name, distinct_id, timestamp, and $insert_id before you load the data anywhere else. For projects created before January 1, 2023, timestamps are in your project timezone. For newer projects, they’re in UTC.
4

Export user profiles

Call the Engage API with no filter to return every user profile. Results come back one page at a time. Pass the session_id from the first response and increase page until a response returns fewer records than page_size.
5

Export group profiles

Repeat the Engage API export once for each group key, passing its data_group_id. You can find each data_group_id in your project settings. See Group Profile Export via API.
The Raw Event Export API and the Engage API return the canonical distinct ID shown in the UI. Data Pipelines exports events as Mixpanel ingested them, so use the identity mappings table to match Mixpanel’s unique user counts.

​
Keep a Continuous Copy

Data Pipelines exports events, user profiles, and identity mappings on a schedule. It writes to Amazon S3, Google Cloud Storage, Azure Blob Storage, BigQuery, Databricks, Redshift Spectrum, or Snowflake. When you create a pipeline, you can backfill up to 6 months of history. For older events, use the Raw Event Export API for those dates.