How to export your data from Twilio

Twilio lets you export Messages, Calls, Conferences and Participants records as CSV (small volumes, via Console) or as gzipped JSON files (large volumes, via the Bulk Export API/Console Log Archives), covering call/message metadata but not media attachments or account configuration.

Formats: CSV, JSON (gzip)Plan: Any plan for CSV/API exports up to ~10,000 records; Twilio Editions plan required for automatic daily Bulk Export via ExportConfigurationRole: Account Owner or Admin (bulk export job notifications go to owners/admins by default)

✓ Verified against Twilio's official documentation, September 2026

Step by step

1For up to 10,000 message records: open Console > Monitor > Logs > Messages (console.twilio.com/us1/monitor/logs/sms) and click 'Export to CSV' in the top right.
2For up to 2,500 call records: open Console > Monitor > Logs > Calls (console.twilio.com/us1/monitor/logs/calls) and click 'Export CSV'.
3For up to 1,000 records via API: build the URL https://api.twilio.com/2010-04-01/Accounts/{AccountSid}/Calls.csv?PageSize=1000 (or Messages.csv for SMS), open it in a browser, and authenticate with your Account SID as username and Auth Token as password.
4Add filters like To, From, StartTime or DateSent to the URL query string to narrow the export to a date range or number.
5For larger or ongoing exports: open Twilio Console > Voice > Settings > Log archives (for SMS, the equivalent page under Messaging > Settings).
6On the 'Custom jobs' tab, click 'Create custom job', choose the resource type (Messages, Calls, Conferences, Participants), a start/end date range, and optionally a webhook or email for completion notification.
7Optionally click 'Setup daily exports' on the same tab to have Twilio generate a file automatically every day (requires a Twilio Editions plan).
8Once the job completes, go to the 'Files' tab and download the generated gzipped JSON files; files remain available for 7 days after generation.

What the export includes

✓Message records (SID, from/to, body, status, direction, price where available, timestamps)
✓Call records (SID, from/to, duration, status, price where available, timestamps)
✓Conference records and Participant records
✓Up to 366 days worth of history per 24-hour request window via Bulk Export custom jobs

What it doesn't include

✗Media/MMS attachment files (only metadata fields are exported, not the media binaries themselves)
✗Fields such as price_units, api_version, uri, and subresource_uris (media URLs) are stripped from Bulk Export message records
✗Account configuration, phone number settings, Studio Flows, Functions, TwiML Apps, or Verify/Proxy service configs are not part of these log exports
✗Analytics/aggregated metrics from Messaging Insights or Calls Insights (a separate product, not raw log export)

Before you start

⚠Bulk Export files are automatically deleted 7 days after generation, so you must download them promptly.
⚠A parent account plus all its subaccounts can request a combined total of up to 366 days of data within any 24-hour UTC window; exceeding this gets the request rejected until the next UTC day.
⚠The Bulk Export API is only available on the default US1 region; it does not work with Twilio Regions Ireland (IE1) or Australia (AU1).
⚠Automatic daily exports via ExportConfiguration require a Twilio Editions plan; the Console CSV export and one-off Custom Jobs do not.
⚠Deleting a BulkExport Call record (for calls under 13 months old) does not delete the underlying Call resource, but deleting the Call resource does delete its BulkExport record; for calls older than 13 months, BulkExport is the only place the record exists.
⚠Call record deletions are processed asynchronously and can take up to a week to complete.
⚠Console CSV export caps out at 10,000 message records or 2,500 call records; anything larger needs the Bulk Export Custom Jobs or API instead.

Where to take your data

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

Plivo

Alternatives Twilio vs Plivo

Use the exported CSV/JSON call and message logs as historical records for compliance/reporting; recreate active phone number routing and applications manually in Plivo since Twilio exports do not include number configuration or app logic.

Vonage API

Same approach: retain Twilio's exported logs as an archive for compliance/analytics, then rebuild messaging/voice application logic natively on Vonage's APIs since Twilio's export contains only historical activity data, not app configuration.

Resend

Alternatives Twilio vs Resend

Not directly applicable for SMS/voice history, but if migrating Twilio SendGrid email sending to Resend, use SendGrid's own export tools (separate from this Bulk Export API) for email activity/contact data, then set up sending domains and templates fresh in Resend.

Exporting from Twilio: common questions

Can I export all my Twilio SMS and call history at once?+

Yes, via the Bulk Export API or Console Log Archives you can request a custom job covering a date range (up to 366 total days per 24-hour window across an account and its subaccounts), which generates one gzipped JSON file per day.

What format does Twilio use for large exports?+

Bulk Export files are delivered as compressed GZIP JSON files with one record per line, with timestamps in UTC ISO 8601 format.

Is there a simple CSV download for smaller accounts?+

Yes, the Message Logs and Call Logs pages in Console each have an 'Export CSV' button, capped at 10,000 message records or 2,500 call records respectively.

How long do exported files stay available for download?+

Bulk Export files are automatically removed after seven days, so you need to download them before then.

Does the export include message/call recordings or MMS media files?+

No. Bulk Export records omit subresource_uris (which would contain media URLs), so only the metadata fields are exported, not the actual media or recording files.

Do I need a specific plan to export my data before leaving Twilio?+

No paid plan is required for one-off exports (Console CSV, API CSV up to 1,000 records, or Bulk Export custom jobs); a Twilio Editions plan is only needed if you want automatic daily exports configured ahead of time.