Skip to content
Outrich Data

Export guide · Checked against Intercom documentation 2026-11-17

How to export all your conversations and data from Intercom

Intercom has no single export file. Teammates with the right permission export saved Inbox views and report datasets as CSV, or conversations as text or PDF transcripts. For full history, an administrator sends up to two years of conversation data as JSON to Amazon S3 or Google Cloud Storage from Settings > Data > Imports & exports > Export data.

Who can export from Intercom

Each route has its own permission. At the time of checking, exporting a saved Inbox view as CSV needs the Can export conversation data permission and an Inbox seat, and Intercom lists it as available on all plans with Inbox access. Dataset export from Reports needs two permissions: Can access Chart drill-in and Can export CSV.

The cloud storage export is confirmed by email, and that email verifies that you are an Intercom administrator with permission to use the Data export feature. You also need write access details for an Amazon S3 or Google Cloud Storage bucket that your company controls.

Customers can download a text transcript of their own conversation from the Messenger menu, which is worth knowing when you decide what counts as already shared with them.

How to export, step by step

Route 1 of 5

JSON export to Amazon S3 or Google Cloud Storage

Intercom administrator with permission to use Data export

  1. 01Go to Settings > Data > Imports & exports > Export data and select New data export.
  2. 02Choose the Data API version and the Output format, and turn on Include attachments if you need them.
  3. 03Set an optional folder name and choose whether to use dated folders.
  4. 04In the Destination section, enter your S3 or Google Cloud Storage bucket details.
  5. 05Click Test and wait for the message that your bucket was successfully tested.
  6. 06In the Schedule section, enable Export historical data for the last two years, then choose Hourly or Daily for periodic exports.
  7. 07Click Start data export, then OK.
  8. 08Open the email from Intercom and click Confirm.

Intercom can write to the bucket but cannot read or delete files in it, and you cannot export more than one workspace to the same bucket. Periodic exports begin after the historical export shows Completed.

Route 2 of 5

Saved Inbox view as CSV

Teammates with Can export conversation data and an Inbox seat

  1. 01In the Views section of the Inbox left navigation, hover over a saved view and click its name.
  2. 02Click the download icon labeled Export as CSV in the actions row.
  3. 03Download the file, or wait for the emailed link if the export is larger than 25,000 cells.

The CSV is a point-in-time snapshot of the visible columns in on-screen order, and each row includes a direct link to the conversation in Intercom.

Route 3 of 5

Dataset export from Reports

Teammates with Can access Chart drill-in and Can export CSV

  1. 01Go to Reports > Dataset export.
  2. 02Select a dataset and set a time period.
  3. 03Filter by attributes if needed and choose the columns.
  4. 04Preview the result and click Export CSV.

Browser downloads are limited to 10,000 rows. Larger exports are emailed and can take up to an hour. You can also save a schedule with a name and a frequency.

Route 4 of 5

Transcripts as text or PDF

Teammates working in the Inbox

  1. 01Filter the Inbox and check the conversations you want.
  2. 02Click More actions in the bulk actions bar and type export.
  3. 03Select Export as text or Export as PDF.

For one conversation, open it, click the three dots at the top right and select Export conversation as text or Export conversation as PDF.

Route 5 of 5

Conversations API

Developers with an access token for the workspace

  1. 01Use the Conversations API to retrieve a list of conversation IDs.
  2. 02Send a GET request to /conversations/{conversation_id} for each ID.
  3. 03Add display_as=plaintext if you want message bodies as plain text.
  4. 04Send the page parameter and follow conversation_parts.pages.next until it is null for conversations with more than 500 parts.

What comes out

The cloud storage export writes JSON or JSONL files to your bucket, inside date-based folders if you chose that option. File names start with the start and end date-times of the batch in UTC, and each file holds at most 200 conversations. Each JSON object is the entire conversation with all of its parts. A periodic file repeats the whole conversation when it is updated, not only the new parts. Attachments are stored under attachments/<conversation_id>/<conversation_part_id>/<attachment_name> and are referenced from the conversation data.

Through the API a conversation is one object: the source message that started it, a list of conversation parts each with a type, body, author and attachments, the contacts and teammates involved, tags, statistics such as time to first admin reply, a rating if one was given, and custom attributes.

The CSV routes are flat tables. A saved view export mirrors the columns on screen. A dataset export holds reporting metadata such as conversation IDs, timestamps, attributes and metrics. Transcripts are one text or PDF file per conversation.

In the exportWhat it contains
Conversation JSON or JSONL filesBatches of up to 200 full conversations, named by the UTC start and end time of the batch.
attachments folderAttachment files stored by conversation ID and conversation part ID, when Include attachments is on.
Saved view CSVVisible Inbox columns for each matching conversation or ticket, with assignees, teams, tags and companies shown as names.
Dataset CSVReporting metadata from one of 13 datasets, without message or conversation content.
Text or PDF transcriptThe message chronology with timestamps and participant information. Internal notes are excluded.
API conversation objectSource message, conversation parts, contacts, teammates, tags, statistics, rating and custom attributes.

Before you rely on it

Limits and gotchas.

  • The historical cloud storage export covers the last two years, and dataset exports also draw on up to two years of data.
  • Conversation and ticket data exported to cloud storage does not contain a transcript. Intercom points to the UI export or the REST API for transcripts.
  • A saved view matching more than 100,000 conversations is refused. Only saved views can be exported, not system views such as Inbox, and exports cannot be scheduled.
  • Only one saved view export can run per workspace at a time, so another teammate's export can block yours.
  • Bulk transcript export supports about 200 to 300 conversations per operation. Intercom says to use the Conversations API for larger volumes.
  • Without paging, the API returns only the 500 most recent parts of a conversation.
  • After setup, only the Data API version, output format and attachments setting of a cloud export can be edited. Any other change means deleting and recreating the export, which leaves files already delivered in place.

Handle with care

Personal data inside a Intercom export.

  • Contact records attached to each conversation
  • Message bodies written by customers, which can contain anything they typed
  • Email subjects and recipient lists (to, cc, bcc) on email conversations
  • The user IP address recorded on the source message
  • Teammate names as authors and assignees
  • Company details and custom attributes linked to the contact
  • Uploaded attachments such as screenshots and documents

An export is a copy outside the access controls of Intercom. Store it encrypted, limit who can open it and delete working copies when you are done. The personal data scrubber removes common identifiers in your browser before a file is shared.

What the export can be worth

Outrich Data is a direct buyer of de-identified company data for AI training, from companies with 50 or more employees. We never connect to your Intercom account: your team runs the export above and removes what is out of scope. Not every export qualifies, and a rights review comes before any offer.

Questions

Exporting from Intercom: common questions.

Can I export all Intercom conversations at once?
The closest route is the data export to Amazon S3 or Google Cloud Storage, which can include historical data for the last two years as JSON and then keep sending new and updated conversations hourly or daily. The Inbox and Reports exports are limited by rows and do not carry full message history.
Does the Intercom CSV export include the message text?
The dataset export does not. Intercom states it contains reporting metadata and no message or conversation content. A saved view CSV contains the visible Inbox columns. For message text use transcripts, the cloud storage JSON export or the Conversations API.
How do I get Intercom transcripts in bulk?
Select conversations in the Inbox, open More actions and choose Export as text or Export as PDF. Intercom says this supports about 200 to 300 conversations per operation and recommends the Conversations API beyond that.
Are attachments included in an Intercom export?
In the cloud storage export they are optional. With Include attachments turned on, files are written to an attachments folder organized by conversation ID and part ID. In the API, each attachment is listed with its name, URL, content type and file size.

Steps were checked against Intercom documentation on 2026-11-17. Vendors change menus, plans and limits, so confirm against the linked pages. Intercom is a trademark of its owner. Outrich Data is not affiliated with Intercom.

Find out if your data qualifies.

Eleven questions, about five minutes, no call required. You get an answer on screen and a written follow-up.

esc