Export Intercom Contacts and Conversations to CSV

Decide first: words or numbers

Intercom's own help page for exporting conversation data draws the line clearly. CSV exports provide metadata summaries, whereas message content or full conversations require using tools like the Conversations API or Amazon S3 exports. The same page covers conversation related exports only, and directs readers to the relevant settings pages for user or ticket data exports. Start from the question you need to answer. If the question is how many conversations, how fast they were answered, or who handled them, a CSV is the right file. If the question is what was said, a CSV is the wrong file.

Export a saved View as CSV

A saved Inbox View can be exported to CSV as a point in time snapshot, with the same columns, the same order, and a link back to every conversation. Intercom describes the use plainly: pull the list, split it by owner in a spreadsheet, and click back into Intercom to act on it. The snapshot answers what matches the View right now, not what happened over a date range.

Exports up to 25,000 cells download immediately. Larger ones arrive by email. The feature is available on all plans with Inbox access, for US, EU, and AU data residency, and was released August 28, 2026, according to the help page. Every export is recorded in the Team Activity Log before the job starts, naming the View that was exported. That audit entry is useful if a list is later questioned: the log shows which View produced it, and when.

The help page text opened for this guide names the View export flow under headings, but the detailed click steps under those headings were not present in the text opened. This guide therefore does not invent a click path for the View export. Open the saved View in the Inbox in your own workspace, look for the export control on the View actions, and confirm the columns and order in the downloaded file before sharing it.

Export a dataset CSV from Reports

For a dated, repeatable export, use the dataset CSV export in Reports and Dataset export. Intercom describes it as a flexible CSV export feature, where you can choose exactly what data you need and even schedule automatic exports. The walkthrough on the help page shows the full flow: selecting a dataset, choosing a time period, selecting columns, previewing the data, and clicking Export CSV.

Scheduled exports use the same flow. If you want to receive a conversation data export with the same filters at regular intervals, you can schedule an export, and the export will be delivered at the specific time and day selected in the schedule.

Download conversation content from the Inbox

When you need the words, and the set is small, download conversation content directly from the Inbox as PDF or text files, with no API required. A single conversation can be downloaded individually. Both PDF and text exports include the complete message chronology with timestamps, all participant information, and all visible conversation content. Internal notes are excluded from transcript exports, and unlike ticket exports, there is no option to include them.

Bulk export from the Inbox handles 200 to 300 conversations per operation, according to the comparison table on the help page. The individual UI export is for single conversations, one at a time, while the bulk UI export is for multiple conversations in PDF or text format. Both are manual, one operation at a time.

Contacts: the API route, stated honestly

For contacts, the position in the official pages opened is less complete than for conversations, and this guide states that gap plainly. The Intercom help page opened covers conversation related exports only, and directs readers to the relevant settings pages for user data exports. It does not give a contacts CSV click path in the text opened. This guide therefore does not invent one.

The Intercom developer docs describe a contacts search endpoint. Send a POST request to https://api.intercom.io/contacts/search with a query object in the body defining filters. Multiple filters can be combined with boolean logic. The response returns contact objects as JSON. A recently created contact may not appear immediately; the docs note a delay of a few minutes, and webhooks as an alternative for instant notification.

To turn that JSON into a CSV, convert the returned contact objects to rows in your own code or spreadsheet tool, choosing the fields you need from the objects returned. The conversion step is yours, not an Intercom export feature. Test it on a small search first, confirm the fields present for your contacts, and only then run it across the full set.

Check the file before you use it

Open every CSV before it is shared or loaded. Check the header row, the row count against the limit that applied, and whether the file contains metadata or message content. A View export should show the same columns and order as the View, with a link back to each conversation.

For the full set of Intercom export routes, see the Intercom export methods directory. For Mailchimp destinations, see the Mailchimp exports by destination directory.

Open flags

No official contacts CSV click path was verified in the Intercom pages opened; the contacts route above is the API search endpoint, plus a conversion step that is the reader's own. The detailed click steps for the saved View export were not present in the help text opened. No plan limit for CSV exports is stated beyond the View export availability and the 25,000 cell immediate download limit. Attribute names in the new dataset export differ from the old export in some cases, so check headers on each new export.

Source

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

Facts verified 2026-10-31. Open flags are listed in the section above.

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.