How to export your data from June
June lets you export your full dataset (events, identifies, and groups) as a CSV file delivered by email, or migrate that same data directly into an Amplitude workspace via API key — both triggered from June's built-in migration page.
✓ Verified against June's official documentation, September 2026
Step by step
- 1Go to the migration page at analytics.june.so/a/go-to-my-workspace/migrate.
- 2Stop sending data to June first: remove or disable June tracking (track/page/identify/group calls) in your codebase.
- 3Mark each data type as 'done' on the migration page, then confirm no new events appear in Developer Logs (Settings > Developers > Logs) for a clean export.
- 4Scroll to the 'Select a data export option' section and choose CSV, then click Continue.
- 5In the 'Export your data' section, click the green 'Export data' button to start the export.
- 6Watch the status move from 'Export requested' to 'Export in progress' (usually within 30 minutes) to 'Export completed'.
- 7Wait for an email from June with a download link — this can take a few minutes up to 24 hours depending on data volume.
- 8Unzip the .zst (Zstandard) file using the zstd package on macOS or 7-Zip on Windows to get the final .csv file.
What the export includes
- ✓Full event data
- ✓User identify data
- ✓Group data (account/company-level data)
What it doesn't include
- ✗Saved reports, dashboards, audiences, or Slack alert configurations are not mentioned as part of the export in June's docs
- ✗Only raw event/identify/group data is described — no mention of annotations or milestone definitions being included
Before you start
- ⚠Stop all tracking (track/page/identify/group calls) before exporting to avoid missing or inconsistent recent data.
- ⚠Export status can sit on 'Export requested' for up to 30 minutes before moving to 'in progress' — reach out to June support if it's stuck longer.
- ⚠Full delivery of the CSV via email can take anywhere from a few minutes to 24 hours depending on data size.
- ⚠The exported file arrives compressed as .zst (Zstandard), not a plain .csv — you need zstd (macOS) or 7-Zip (Windows) to unpack it.
- ⚠If migrating directly to Amplitude instead of CSV, Amplitude workspaces are region-locked (EU vs US) and certain Amplitude features like Computations only work in US-hosted workspaces.
Where to take your data
Free and cheaper tools that can take a June export. See all June alternatives →
Amplitude
Skip the CSV entirely: on June's migration page, choose Amplitude instead of CSV, select your workspace region (EU or US, matching your Amplitude URL), paste in an Amplitude HTTP API source key, and click Start migration. June pushes Groups, Identifies, and Events directly into Amplitude, typically completing within a few hours (up to 24 hours for very large workspaces).
PostHog
Export as CSV from June, then use PostHog's CSV/data import tooling or a custom script to map June's events/identifies/groups columns to PostHog's event and person properties.
Mixpanel
Export as CSV from June, then use Mixpanel's Import API or CSV import feature to load events and user profiles, mapping June's user/group fields to Mixpanel's user and group properties.
Exporting from June: common questions
What format does June export data in?+
CSV, delivered as a .zst (Zstandard) compressed file via email. You need zstd (Mac) or 7-Zip (Windows) to unpack it into a plain .csv file.
How long does a June data export take?+
Status typically moves to 'Export in progress' within 30 minutes, and the final email with your CSV can arrive anywhere from a few minutes to 24 hours later depending on data volume.
Do I need to stop tracking before exporting?+
June recommends disabling all track/page/identify/group calls in your codebase first and confirming via Developer Logs that no new data is coming in, to ensure a clean, complete export.
Can I migrate straight to Amplitude without downloading a CSV?+
Yes. On the same migration page, you can choose Amplitude instead of CSV, enter an Amplitude API key, and June will push your Groups, Identifies, and Events directly into your Amplitude workspace.
Does the export include dashboards or saved reports?+
June's documentation only describes exporting the underlying event, identify, and group data — it does not mention dashboards, saved reports, or audience definitions being part of the export.
Where do I start the export in the June app?+
Go directly to analytics.june.so/a/go-to-my-workspace/migrate, which is June's dedicated migration/export page.
Sources
This guide was written from June's own documentation and checked against it in September 2026. If a step has changed, the official page wins.
June head-to-head
More Analytics tools people are leaving
All Analytics alternatives →What would you save without June?
Pick your team size and see the yearly number.