Intercom Export Methods

How to use this directory

Pick by the question first, then by the file type. If the question needs numbers, counts, or a list of conversations, a CSV route fits. If the question needs the words that were written, a CSV route will not fit, and the content routes below are the ones to use. Intercom states that CSV exports provide metadata summaries, while message content requires the Conversations API or cloud storage exports, or the Inbox exports.

For Mailchimp destinations, see the Mailchimp exports by destination directory. The two directories link both ways, because an export question is usually a destination question first and a vendor question second.

Saved View as CSV

Export any saved Inbox View to CSV as a point in time snapshot, with the same columns, the same order, and a link back to every conversation. Exports up to 25,000 cells download immediately, and larger ones arrive by email. Every export is recorded in the Team Activity Log, naming the View exported. See the export Intercom contacts and conversations to CSV guide.

Dataset CSV from Reports

Use Reports and Dataset export for a dated, repeatable CSV. Select a dataset, choose a time period, select columns, preview the data, and export. The same flow supports scheduled exports at a chosen time and day. The file contains metadata summaries, not message content. See the export Intercom contacts and conversations to CSV guide.

Inbox transcript export

Download a single conversation, or 200 to 300 conversations in bulk, from the Inbox as PDF or text files, with no API required. Both formats include the complete message chronology with timestamps, all participant information, and all visible conversation content. Internal notes are excluded, with no option to include them. See the export Intercom contacts and conversations to CSV guide.

Data Export API

Create an export job for messages sent in a date range, with one active job per workspace, and download the result as a gzipped CSV. Completed jobs expire two days after processing. Load the downloaded CSV into a database or spreadsheet after download. See the export Intercom data to PostgreSQL guide.

Cloud storage export

Export all customer conversations to Amazon S3 or Google Cloud Storage as JSON or JSONL files, hourly or daily, with an option for two years of historical data. Each file holds a maximum of 200 conversations. Attachments, when included, are referenced from the exported data. See the export Intercom data to PostgreSQL guide.

Contacts search API

Search contacts through the Intercom API with a query object, and convert the returned JSON contact objects to rows in your own code. No contacts CSV click path was verified in the official pages opened, so this route is stated as an API route plus a conversion step, not as a built in CSV export. See the export Intercom contacts and conversations to CSV guide.

The export pattern

Every Intercom route on this page follows the same pattern: choose content or metadata first, export in the format that route produces, and check the file before it is used. A CSV checked against its header row, a transcript checked for its message chronology, and a JSON file checked for its conversation count will each reveal a wrong route quickly. A file used without that check will reveal the wrong route slowly, in a report built on the wrong data.

Source

• Intercom Help, Export Your Conversations Data
• Intercom Help, Export Conversations Data to Cloud Storage
• Intercom Developer Docs, Data Export API
• Intercom Developer Docs, Search for Contacts

Facts verified 2026-10-31. Open flags: no official contacts CSV click path was verified in the pages opened; the View export click steps were not present in the help text opened. See the guides linked above for the full flags.

This page explains how the process works and what the official rules say. It is general information, not legal advice. For a dispute about your specific situation, talk to your state motor vehicle agency or court.