Export events

Last updated:

At PostHog we believe in your right to own your data - this means being able to export the raw events whenever you want.

There are several ways to export your events depending on your use case:

PostHog UI - click "Export" on the events tableYou need to export a small number of events3,500 events
Events APIGreat for one-off smaller exports1 day date range and 3,500 events
Data export appYou need to export a large number of eventsNo limits

If you're looking to migrate to a new PostHog instance follow the migrating between PostHog instances guide.

Not sure which export method to use?

Here's a decision tree you might find useful:

Do you need to export a large number of events? Above 3,500
Use a data export app
Do you need to run regular exports e.g. once a day or once a week?
Use the PostHog UI or the Events API

Using Data Export Apps

Popular apps for data export include the S3, Google Cloud Storage, BigQuery, PostgreSQL, Redshift, Snowflake. See the full list of data export apps, or find out how to build your own app.

To export your historical data you'll want to connect the app and then run a historical export.

Additionally, these apps stream all the new events to the destination. This keeps your destination up to date with new events as they come in.

Why are there limitations on the PostHog UI export and the events API?

The PostHog UI and the events API are designed to quickly respond with a small number of events. To prevent your queries running slower when another user is trying to export large numbers of events we've built a separate system for managing the exporting of large number of events using apps.


Was this page useful?

Next article


The following pages in this section cover Data model , Ingestion pipeline , ClickHouse and Querying data . This document gives an overview of the general architecture. How our cloud or a deployed PostHog Helm chart works on Kubernetes. Zooming right out There are only a few systems to consider. A Website and API is presented for users. An API for Client Apps. A plugin service for processing events on ingestion. And a worker service for processing events in response to triggers (e.g…

Read next article