Skip to content
DataGrine home

How to export conversations, tickets, contacts and articles from Intercom

Intercom has no single “export everything” button. Contacts export to CSV from the Contacts list. Conversations and tickets export from the Inbox as text or PDF, or as a CSV of a saved view; reporting datasets export as CSV without message content. For complete threads at volume, use the cloud storage export, which sends up to two years of conversations as JSON to Amazon S3 or Google Cloud Storage, or the REST API. Articles have no UI export and come out through the Articles API.

By the DataGrine team · Updated · 3 min read

Key takeaways

  • Text and PDF transcripts exclude internal notes.
  • Dataset CSV exports are reporting data, with no message content.
  • Through the API, a conversation returns at most its 500 most recent parts.
  • Configuration such as Workflows, Fin settings and saved replies is documented by hand, not exported.

Every export route at a glance

WhatWhereFormatLimits Intercom documents
Conversations or ticketsInboxText or PDFInternal notes excluded; 200 to 300 per bulk operation
A saved viewInbox, saved viewCSVNeeds the export permission; very large views are refused
Reporting datasetsReports, Dataset exportCSVNo message content
All conversationsSettings, Data, Imports and exportsJSON or JSONL to Amazon S3 or Google Cloud StorageHistorical export of up to two years, then hourly or daily exports
Users, leads, companiesContacts list, More, ExportCSV by emailLink expires after one hour; only the most recent company’s name and ID
ArticlesArticles API onlyJSONNo UI export

Before relying on the cloud storage export as an archive, open one exported file and confirm the message bodies you need are there.

The REST API

The API is the complete route, and the one a migration uses: list conversations, then retrieve each one by ID for its thread.

  • Threads: retrieving a conversation returns at most the 500 most recent parts. Check your longest threads.
  • Rate limits: private apps get 10,000 calls a minute per app and 25,000 per workspace by default, spread over 10-second windows, and every app on the workspace shares the workspace limit.
  • Attachments: parts carry attachment URLs. Download each file as you read its conversation, not in a later pass.

Exporting to move to another helpdesk?

Then you may not need an export file at all. A migration reads Intercom’s API directly, keeps contacts, companies and conversations linked, and runs again at cut-over for what changed. With DataGrine you can run it self-serve on the platform or have the migration team handle it end to end, with 24/7 support either way. See Intercom to Zendesk, Intercom to Freshdesk, or moving between two Intercom workspaces.

Questions

Asked about this, often.

Can I export all conversations from Intercom at once?

Not from the Inbox, which exports 200 to 300 at a time. For all conversations, use the cloud storage export, which sends up to two years of history to Amazon S3 or Google Cloud Storage, or the REST API.

Do Intercom exports include internal notes?

Inbox text and PDF transcripts exclude internal notes. The API returns notes as conversation parts, up to the 500 most recent parts of each conversation.

How do I export Intercom contacts?

Select the users or leads in the Contacts list, open More and choose Export users. The CSV is emailed and the link expires after one hour.

Can I export Intercom Help Center articles?

Not from the interface. Use the Articles API, which returns each article’s HTML body, title, metadata and localisation data.

Let’s move your data forward.

Tell us where you are moving from and to. Run it yourself on the DataGrine platform or let our migration team handle it end to end, with 24/7 support either way.

  • A written mapping document before anything moves
  • A sample migration you review before the live run
  • Delta sync at cut-over and rollback per run
  • 24/7 premium support until you sign off