How to export your data from Segment
Segment does not offer a single one-click 'export workspace' button. Instead, raw event data is exported as line-separated JSON logs via a connected Amazon S3 destination or data warehouse, and Business-plan customers can additionally use 'Replay' to backfill full timestamped history into a new destination.
✓ Verified against Segment's official documentation, September 2026
Step by step
- 1Decide which export method fits your plan: data warehouse, S3 logs, webhooks, or (Business plan only) Replay.
- 2To export raw event logs: go to your workspace's destinations catalog and enable the Amazon S3 destination, pointing it at your own S3 bucket.
- 3Segment will copy your API calls to that bucket as line-separated JSON objects — but only data sent to Segment after you turn the destination on, not retroactively.
- 4To get structured/SQL-queryable data instead: connect a data warehouse destination (Free and Team plans can connect one warehouse; Business plans can connect multiple).
- 5If you're on the Business plan and moving to a new vendor, use Replay to resend your full timestamped historical data (since your first event) to any server-side destination that accepts timestamps, including S3.
- 6For basic metrics only, you can instead enable a third-party reporting destination (e.g. Google Analytics, Clicky, Keen.io) and pull data from that tool's own reporting API.
- 7If you need real-time forwarding instead of a batch export, set up the Webhooks destination (or Iron.io, which adds queue management and scripting) to receive events on your own endpoint.
What the export includes
- ✓Raw API calls (track, identify, page, etc.) as line-separated JSON objects when using S3
- ✓Translated/loaded event data in SQL form when using a connected warehouse
- ✓Full timestamped historical event data when using Replay (Business plan)
What it doesn't include
- ✗S3 logs only capture data sent to Segment after you enable the S3 destination — nothing sent before that point is copied
- ✗Workspace/account configuration (sources, destination settings, tracking plans) is not part of these data export methods
- ✗Full historical Replay backfill is restricted to the Business plan
- ✗Third-party reporting APIs (Clicky, Google Analytics, Keen.io) only expose basic aggregated metrics, not full raw event data
- ✗No native CSV export is documented for bulk raw data
Before you start
- ⚠S3 export is forward-only: enable the S3 destination well before you plan to leave, or you'll miss historical data
- ⚠Free and Team plans are limited to one connected warehouse; Business plans can connect as many as needed
- ⚠Webhooks and Iron.io require you to build and operate your own receiving server/queue — Segment doesn't host this for you
- ⚠Replay (the closest thing to a full historical export/migration tool) is only available to Business plan customers
- ⚠Reporting-API-based exports (Clicky, GA, Keen.io) are described as the most restrictive option and won't surface all Segment data
Where to take your data
Free and cheaper tools that can take a Segment export. See all Segment alternatives →
RudderStack
Point RudderStack at the same S3 bucket (or a new one) as a source/warehouse destination, then replay or backfill your line-delimited JSON event logs into RudderStack's pipeline.
Jitsu
Load the line-delimited JSON event logs from your S3 bucket into Jitsu as a batch source, or forward live traffic to Jitsu's HTTP endpoint as a Segment webhook destination.
PostHog
Use PostHog's S3/warehouse import to ingest the JSON event logs Segment wrote to your bucket, or route new events to PostHog going forward via a webhook destination while historical data backfills from S3.
Exporting from Segment: common questions
Can I export all my Segment data for free?+
Yes for raw event logs: Free and Team plans can connect one data warehouse or enable the S3 destination to capture ongoing event data as JSON. A full historical backfill to a new vendor via Replay, however, is a Business plan feature.
Does Segment support CSV export?+
Segment's documented export options are JSON (line-delimited logs in S3) and SQL tables via a connected warehouse — there's no documented native CSV export for bulk raw data.
Will I get my historical data or only new events going forward?+
The S3 destination only copies data sent to Segment after you enable it — it is not retroactive. To get full historical, timestamped data replayed to a new tool, you need Replay, which is limited to the Business plan.
What's the easiest way to get basic metrics out without building infrastructure?+
Enabling a third-party reporting destination like Google Analytics, Clicky, or Keen.io and pulling from that tool's own reporting API is the simplest route, though it only surfaces basic metrics, not full raw data.
Do webhooks give me a real export file?+
No — webhooks (and the similar Iron.io option) stream events in real time to an endpoint you build and manage; they're a live forwarding mechanism, not a downloadable export file.
Do I need a developer to do this?+
For warehouse or S3-based exports you mainly need to enable a destination in the catalog, but consuming the resulting JSON/SQL data, or building a webhook/Iron.io receiver, generally requires engineering work.
Sources
This guide was written from Segment's own documentation and checked against it in September 2026. If a step has changed, the official page wins.