Export chats from Intercom.
About ten minutes for an admin. Intercom exports as JSON via an admin-only URL — no API keys needed for this route.
Send raw. We anonymise on receipt. Full anonymisation guarantee in the data note. If your policy requires a scrubbed file, ask us for anonymise.py.
What we need
- Conversations — the full message thread for each conversation, in order, with timestamps and who wrote what.
- Period: 30 days minimum. 90 days is better if your load is seasonal.
- Format: JSON (Intercom's default).
- Channels: Messenger and Email. Include phone if you use Intercom for voice.
Sign in as a workspace admin
You need Full access or Admin role on the workspace you want to export. Reporter and Agent roles don't have export permission.
Open Settings → Data → Export
Click your workspace name in the bottom left → Settings → in the sidebar under Data, click Export. Then choose Conversations.
Pick the date range and start the export
Set the range to the last 30–90 days (whatever we've agreed). Leave the type filter as All conversations unless you want to send a specific inbox or team's traffic only.
Intercom will show an estimate ("about N conversations, ready in X minutes"). Click Request export.
Download the ZIP when the email arrives
Intercom emails a one-time download link to the admin who requested the export. The link expires in 30 days. You get a ZIP archive containing one JSON file per conversation plus a manifest — don't unzip it, upload the ZIP as-is to the private link we sent.
Password-protect the ZIP if your policy requires it, and send the password separately.
If you want the API route instead
Some teams prefer pulling conversations through the Intercom API (endpoint GET /conversations, paginated). If that's you, we accept a folder of newline-delimited JSON. Filter by created_at for the same date range. This is the cleaner route for teams with more than ~100K conversations in the period.
Common questions
Our conversations include a lot of bot messages from Fin.
Perfect — please leave them in. Seeing what Fin resolves, hands off, and answers confidently and wrong is one of the most interesting things the report can show.
The export contains user attributes and events, not just messages.
Fine. We use conversation content only; the extra attributes are ignored (and stripped during anonymisation regardless).
We're on Intercom's EU workspace.
The export screen is identical. Data residency doesn't change the steps; we store the file in the EU either way.