How to export your data from Sentry

Sentry lets you export query results as CSV from the Errors (Discover) view, and export up to 10,000 log lines as CSV or JSON Lines (JSONL) from the Logs view. There is no built-in full-account/project-settings backup — exports are query-result based, not a complete data dump.

Formats: CSV, JSONLPlan: Errors/Discover-style CSV export: the Errors page and its trend-analysis features are only available on Trial, Business, or Enterprise plans. Logs export was not described in the docs as plan-restricted beyond having Logs enabled.Role: Not specified in Sentry's documentation — any org member with access to the project/query appears able to trigger an export.

✓ Verified against Sentry's official documentation, October 2026

Step by step

1For error event data: go to Explore > Errors in your Sentry organization.
2Build or select a saved query (filters, date range, projects, environments, columns) for the data you want.
3Click 'Export Data' to download a CSV of the results.
4If the result set is large, Sentry generates the file in the background and emails you a download link instead of downloading immediately.
5Verify the downloaded file's integrity using the included SHA1 checksum.
6For log data: go to Explore > Logs.
7Click 'Export Data', choose CSV or JSONL, pick either 'currently displayed columns' or 'all columns' (all columns requires JSONL), and set the number of rows (max 10,000).
8Download the file directly, or wait for the email link if the export is large.

What the export includes

✓Error event metadata matching your query: fields like count, user counts, tags, release, platform, URL, stack filename, timestamps, etc.
✓Log lines matching your Logs query, with the columns you selected (or all columns in JSONL)
✓A SHA1 checksum for the Errors CSV to verify the download wasn't corrupted

What it doesn't include

✗Full raw stack traces, breadcrumbs, or attachments are not part of these CSV/JSONL exports
✗Project settings, alert rules, integrations configuration, and team/member data are not covered by the Errors or Logs export tools
✗Issue comments, assignment history, and resolution workflow state are not included in these exports
✗Logs exports are capped at 10,000 lines per export, so full historical log volumes typically require multiple exports

Before you start

⚠Errors/Discover CSV exports are capped at 10 million rows or 1 GB, whichever limit is hit first
⚠Large Errors exports are delivered by email rather than an immediate browser download
⚠Logs exports cap at 10,000 lines per export; exporting 'all columns' requires JSONL, not CSV
⚠Depending on export size, Logs files either download directly or arrive by email
⚠The Errors query/export feature itself is gated to Trial, Business, or Enterprise plans

Where to take your data

Free and cheaper tools that can take a Sentry export. See all Sentry alternatives →

Bugsnag Free

Bugsnag has no native importer for Sentry's CSV/JSONL exports. Use the exported files as a historical reference/archive (e.g., load into a spreadsheet or database) and start fresh error tracking in Bugsnag going forward by installing its SDK.

Highlight.io

Highlight.io doesn't support importing Sentry's exported CSV/JSONL as live issues. Keep the export as an archive for past incident data, and instrument your app with Highlight's SDK for new error capture.

Sentry Free

Alternatives

If you're moving between Sentry organizations/plans rather than leaving Sentry, there's no CSV re-import path either — the exports are for backup/analysis, not organization migration. New errors will simply start accumulating in the destination org once the SDK is pointed there.

Exporting from Sentry: common questions

Can I export my entire Sentry account/organization in one click?+

No. Sentry's documented export tools are query-result exports (Errors CSV, Logs CSV/JSONL), not a single full-account backup.

Will I lose my error history if I downgrade or cancel my Sentry plan?+

The Errors (Discover-style) export feature itself requires a Trial, Business, or Enterprise plan, so you should export the data you need before downgrading.

What's the maximum amount of data I can export at once?+

Errors CSV exports cap at 10 million rows or 1 GB (whichever comes first); Logs exports cap at 10,000 lines per export.

Can I verify my exported file wasn't corrupted?+

For Errors CSV exports, Sentry provides a SHA1 checksum you can check against the downloaded file with sha1sum.

Can I export logs in a structured format instead of CSV?+

Yes, the Logs export supports JSON Lines (JSONL) in addition to CSV, and JSONL is required if you want to export all columns rather than just the displayed ones.

Does exporting data migrate my alert rules, integrations, or team settings too?+

No, these exports only cover the Errors/Logs query data itself — project settings, alert rules, and integration configs aren't part of these export features.