TL;DR Short answer: the Intercom data that matters for analysis lives in conversation parts, not just conversations, so pick a tool that syncs every reply, note and assignment incrementally. Then check how it handles Intercom's regional hosting and its limits on exporting companies. Eight options:
Airbyte Fivetran Stitch Hevo Data CData Sync Coupler.io Zapier Intercom reports The Intercom constraint: response times, handoffs and Fin AI resolution only show up in conversation parts, the individual messages and actions inside each conversation, so a tool that syncs only conversation summaries cannot rebuild these metrics. Intercom ETL tools move conversations, conversation parts, contacts, companies, tags and team data out of Intercom and into a warehouse or spreadsheet. There support performance can be measured over time and joined with product usage, billing and CRM data to understand how support affects retention and expansion.
Why move Intercom data into a warehouse? Intercom's reports cover support volume, response times and CSAT within Intercom. Product and revenue teams usually want more: which features drive conversations, whether customers who contact support churn faster, how Fin AI deflection changes support cost per account, and how conversation topics trend after a release. Those answers need Intercom data next to product events, subscriptions and CRM records.
How do the Intercom ETL tools compare? Tool Best destination Conversation parts Deployment Pricing model Airbyte Warehouse, lake or database Yes, incremental Cloud, self-hosted, Enterprise Flex Free self-hosted; Cloud volume-based; Pro and Flex capacity-based Fivetran Warehouse Yes Cloud, hybrid Monthly active rows Stitch Warehouse Yes Cloud Rows per month Hevo Data Warehouse Yes Cloud Events CData Sync Database or warehouse Depends on configuration Cloud or self-hosted Subscription by connector Coupler.io Sheets, Excel, BigQuery Limited Cloud Subscription by imports Zapier Other apps New events only Cloud Tasks per month Intercom reports CSV No Intercom web app Included with Intercom
Which Intercom ETL tools should you consider? Eight options, from warehouse ELT to manual exports:
1. Airbyte Airbyte is an open-source ELT platform with 700+ connectors. Its Intercom source syncs conversations and conversation parts, contacts, companies, company segments, segments, tags, teams and admins, with incremental sync on the high-volume streams. Conversation parts give you every reply, note, assignment and state change, which is what response time and handoff metrics are built from.
You authenticate with OAuth on Airbyte Cloud or an access token from an Intercom app on Airbyte Core. Airbyte fits when Intercom needs to sit next to product, billing and CRM data in the same warehouse, self-hosted, on Airbyte Cloud or as Enterprise Flex.
Pros Cons Conversation parts for response time and handoff metrics Large conversation histories take time to backfill Incremental sync on high-volume streams Bound by Intercom's API rate limits Intercom next to product, billing and 700+ other sources Transformation happens in the warehouse
2. Fivetran Fivetran is a fully managed ELT service with an Intercom connector that loads conversations, parts, contacts and companies into a standard warehouse schema, with packaged dbt models for support metrics. Fivetran completed its merger with dbt Labs in June 2026.
Pros Cons Fully managed, with a standard schema Monthly active row pricing grows with conversation volume Packaged dbt models for support metrics Connector behaviour cannot be modified Handles schema changes automatically Warehouse-only destinations
3. Stitch Stitch is a simple, hosted extract-and-load service built on the Singer specification, with an Intercom integration among its 140+ connectors. Qlik acquired Stitch with Talend in 2023 and now publishes a migration path to Qlik Talend Cloud, which is worth weighing before starting a new pipeline on it.
Pros Cons Quick to set up for a single workspace No transformation layer Published, tier-based pricing Product line being consolidated into Qlik Talend Cloud Familiar to teams already using Singer taps Narrower catalogue than larger platforms
4. Hevo Data Hevo Data is a no-code managed pipeline platform with 150+ connectors, including Intercom. It can transform data before it loads, using Python or a drag-and-drop editor, and prices on events, with a free tier for small volumes.
Pros Cons No-code setup for support ops teams Event-based pricing grows with conversation volume Transformation before load Cloud-only, with no self-hosted option Free tier for small workspaces Smaller catalogue than Airbyte or Fivetran
5. CData Sync CData Sync is a replication tool built on CData's drivers, which expose Intercom contacts, companies, conversations and other objects as relational tables. It replicates into common databases and warehouses and can run in the cloud or on your own infrastructure.
Pros Cons Presents Intercom objects as relational tables Commercial licence priced per connector Cloud or self-hosted deployment Smaller ecosystem than the largest ELT platforms Many database and warehouse destinations Less community content than open-source tools
6. Coupler.io Coupler.io exports Intercom data into Google Sheets, Excel, Looker Studio and BigQuery on a schedule. It suits small support and success teams that build reports in spreadsheets and want them refreshed automatically.
Pros Cons Spreadsheet and Looker Studio destinations Less suited to large conversation histories No-code, scheduled refreshes Pricing tied to import volume and frequency Quick to set up Limited support for conversation-level detail
7. Zapier Zapier connects Intercom to 8,000+ apps through triggers such as new conversations, new contacts and tag changes. It is ideal for operational flows, like creating a CRM task when a high-value customer opens a conversation, but it does not backfill history or model data for analytics.
Pros Cons Fastest no-code setup for simple flows No historical backfill Real-time triggers in both directions Task-based pricing grows with activity Connects Intercom to 8,000+ apps Not built for analytics-grade pipelines
8. Intercom reports Intercom's built-in reports cover conversations, response times, team performance, CSAT and Fin AI resolution, and most can be exported to CSV. They are the quickest way to answer a one-off question, but exports are manual and summary-level, and do not combine Intercom with other systems.
Pros Cons Built in, with no extra tools Manual CSV exports Covers support and Fin AI performance Summary-level, not conversation parts No setup beyond Intercom access Cannot be joined with other data automatically
What should you check before syncing Intercom? Intercom's API is well documented, but a few details decide whether warehouse metrics match Intercom's own reports:
Authentication: connect with OAuth or an access token from an Intercom app in the Developer Hub, never with a teammate's login. Give the app read-only permissions.Data hosting region: Intercom hosts workspaces in the US, EU or Australia, each with its own API address. The tool must call the region your workspace lives in.Conversation parts: response times, reassignments, notes and bot handoffs live in conversation parts. Sync them, not just conversations, if you report on support performance.Company exports: Intercom limits how company data can be paged through, and only one bulk company export can run at a time per workspace. Avoid running several tools against companies at once.Rate limits and backfill: Intercom limits API requests per minute per app. Large workspaces with years of conversations take time to backfill, so set a start date for the first sync.Custom attributes and personal data: most workspaces rely on custom contact, company and conversation attributes, which should arrive as columns. Conversation bodies contain customer personal data, so restrict access in the warehouse.Intercom's API exposes the full support and engagement model, including:
Conversations: state, priority, assignee, team, source channel, tags, ratings and timestamps. Conversation parts: every reply, note, assignment, state change and bot action within a conversation. Contacts: users and leads with attributes, location, signup and last-seen dates, and custom attributes. Companies: accounts with plan, size, monthly spend and custom attributes, plus their segments. Admins and teams: the support team behind assignments and performance reporting. Tags and segments: classifications used to group conversations, contacts and companies. How do you start pulling data from Intercom? If you decide to test Airbyte, setting up an Intercom pipeline takes three steps.
Step 1: Set up Intercom as a source In Airbyte, open Sources, choose New source and select Intercom . On Airbyte Cloud, authenticate your Intercom workspace with OAuth; on Airbyte Core, create an app in the Intercom Developer Hub, copy its access token and paste it in. Set a start date to control how much conversation history is backfilled.
Step 2: Set up a destination Pick where your Intercom data should land: a warehouse such as Snowflake, BigQuery or Databricks, a database, or another Airbyte destination.
Step 3: Configure the connection Select conversations, conversation parts, contacts, companies, admins and teams, use incremental sync with deduplication, and schedule runs hourly or daily. The process is the same whether you deploy Airbyte Open Source or start with Airbyte Cloud .
Which Intercom ETL tool should you choose? For support analytics joined with product, billing and CRM data, use a warehouse tool that syncs conversation parts: Airbyte for control and broad destinations, Fivetran for a managed pipeline with packaged models, Hevo for a no-code setup, or CData Sync for relational tables with a self-hosted option. Stitch still works for simple setups, with its future under Qlik in mind. Small teams reporting in spreadsheets will move fastest with Coupler.io, Zapier suits operational automations, and Intercom's own reports cover one-off questions.
For a wider view of the market, see our guide to the top data integration tools .
Sync Intercom to your warehouse with Airbyte Replicate Intercom conversations, conversation parts, contacts and companies incrementally, next to your product, billing and 700+ other sources, self-hosted, on Airbyte Cloud or with Enterprise Flex.
Try Airbyte Cloud free for 14 days or talk to our team .
Frequently Asked Questions (FAQs) 1. How do you export Intercom conversations to a data warehouse? Connect Intercom to an ELT tool such as Airbyte, Fivetran or Hevo, choose your warehouse as the destination, and sync conversations and conversation parts incrementally. Conversation parts hold the individual replies and actions needed for response time metrics.
2. What is the difference between conversations and conversation parts? A conversation is the overall thread with its state, assignee and tags. Conversation parts are the individual messages, notes, assignments and state changes inside it, which you need to calculate response times and handoffs.
3. Why does my Intercom connection fail for an EU workspace? Intercom hosts workspaces in separate regions, such as the US, EU and Australia, each with its own API address. Make sure the tool supports and is configured for the region your workspace is hosted in.
4. Can you export Intercom data to Google Sheets? Yes. For one-off needs, export reports as CSV from Intercom. For scheduled refreshes, Coupler.io sends Intercom data to Google Sheets, while ELT tools such as Airbyte are better for large conversation histories.
Suggested reads Zendesk Support ETL Tools
Freshdesk ETL Tools
HubSpot ETL Tools
Stripe ETL Tools
.webp)