Find and export
your Intercom data.

1. 1Use a teammate role allowed to access Reports.
2. 2Create or open a Conversations report and inspect New conversations for the selected dates.
3. 3Run non-overlapping periods when adding several years and note the reporting-history limit.
4. 4For older retained conversations, ask a developer to inspect the conversation-search API and its total count.

Report in records, identifying conversation counts, dates and inbox scope. Describe messages, internal notes and attachment availability.

Include the customer and teammate scope, with older history identified separately from the standard reporting window.

1. 1As an authorized admin, open Settings → Data → Imports & exports → Export data.
2. 2Create a new cloud-storage export using JSON or JSONL and the required attachment option.
3. 3Connect an approved Amazon S3 or Google Cloud Storage bucket and test the connection.
4. 4Enable the historical export and follow the start and verification steps. Confirm another route for history beyond its supported period.

Intercom documents a two-year historical cloud export, with ongoing hourly or daily exports available.

A reporting CSV can provide metrics without message text. Check that the selected collection includes the actual conversations and files.

Customer conversations can connect a product question with the clarification and solution provided.

Inbox and contact context can show how a support team handles a continuing relationship.

Select the inboxes, conversations and customer fields in scope, reviewing sensitive message content and attachments.

Telegraph Lab reviews the proposed material with you and agrees how sensitive information will be handled. Preparation can include excluding material, redacting details and replacing personal identifiers. Your company keeps ownership; the licensing agreement defines the material, permitted uses and authorized recipients.