Does Intercom sync with HubSpot natively?

Yes. Data sync, mixed, covering 4 objects. What it does not do is rebuild configuration: that is the 31 items below.

How long does a Intercom to HubSpot migration take?

Typically 3-6 weeks. Data extraction alone: 2-3 weeks for meaningful volumes due to API rate limits. Automation rebuild: 1-2 weeks depending on complexity. weeks. Complexity is driven by automation and reporting depth, not by record count: the connector moves records, so a large database is not by itself a long project.

How many Intercom features have a HubSpot equivalent?

Of 51 features we mapped, 25 (49%) carry across directly and 21 (41%) map partially, meaning something is lost or reshaped. 5 have no HubSpot equivalent at any tier.

What does not transfer from Intercom to HubSpot?

31 items have to be rebuilt by hand, and 8 documented limitations are not surfaced by the connector at all. The full list of both is on this page.

What HubSpot subscription is needed?

Free for basic sync. Data Hub Starter+ for custom field mappings.

What can HubSpot not do that Intercom does?

5: Push Notifications, Tooltips, Product Tours, Checklists (Onboarding), News (Newsfeed). If a client depends on one, it belongs in the conversation before the contract.

Does a migration rebuild Intercom's custom code?

No. 1 item on this page is Intercom's own code or product, which a HubSpot migration does not port and which carries no hours in an estimate. It still needs a decision, because the client is giving something up.

Can we run both systems in parallel during the migration?

Only in one direction. The sync is not bidirectional here, so a parallel period means picking a system of record and accepting drift in the other.

Agency Migration Guide

Intercom to HubSpot Migration

What actually transfers, what quietly does not, and what has to be rebuilt by hand.

We mapped Intercom against HubSpot feature by feature: 51 features, 4 synced objects, 8 documented traps and 31 items that have to be rebuilt. The whole map is on this page, ungated.

The PDF is the same reference, formatted to send to a client.

Size Your Migration

Get The Guide And The Calculator

The full Intercom to HubSpot reference as a branded PDF you can send straight to a client, plus the Excel calculator we scope these migrations with: every one of the 51 features as a row, enter your counts, get hours.

Three files: the guide as a PDF, the same guide unbranded in Markdown for your AI tool, and the full Excel effort calculator.

Intercom to HubSpot is a high migration, typically 3-6 weeks. Data extraction alone: 2-3 weeks for meaningful volumes due to API rate limits. Automation rebuild: 1-2 weeks depending on complexity. weeks. Of 51 features we mapped, 25 carry across as they are and 21 land with something lost. The work is not moving records: it is the 31 items nothing moves for you.

Migration Scorecard

High

Migration complexity: High
Typical timeline: 3-6 weeks. Data extraction alone: 2-3 weeks for meaningful volumes due to API rate limits. Automation rebuild: 1-2 weeks depending on complexity. weeks
Recommended method: Custom API migration with professional service recommended. Do NOT attempt migration using standard CSV imports. Native integration is not suitable for migration: only for ongoing coexistence.
Native sync: Data sync, mixed
Smart transfer: Not supported
HubSpot subscription: Free for basic sync. Data Hub Starter+ for custom field mappings.

Feature parity across 51 capabilities

2549%

2141%

510%

Maps directly: 25 (49%)
Maps partially: 21 (41%)
No equivalent: 5 (10%)

Objects synced natively

Limitations and traps

Manual rebuild items

Source editions covered

Where this comes from: Our own research corpus, verified 2026-07-31, behind every number on this page.

Size Your Own Migration

The Four Objects That Sync Natively

What the connector moves for you, and which way each one flows.

Intercom	HubSpot	Direction	What To Watch
Users/Leads	Contacts	Two way	Two integration paths: (1) Intercom's native HubSpot app syncs one-way Intercom→HubSpot only; creates contacts with lifecycle stage 'Lead' (not customizable). (2) HubSpot Data Sync app enables bidirectional contact sync. Custom qualification attributes can be mapped to HubSpot contact properties via settings.
Companies	Companies	Two way	Only available via HubSpot Data Sync app (bidirectional). The Intercom-built native app does NOT sync company-level attributes to HubSpot: only user-level attributes are supported.
Conversations	Timeline Activities	Into HubSpot	Via Intercom's native HubSpot app only. End-user replies sync in real-time; teammate replies only sync after conversation closes. CRITICAL: Only conversations started AFTER app connection are sent. Pre-existing conversations do NOT sync unless the customer replies after the app was connected. Intercom Series emails (mass messages) are excluded. Only one-on-one/direct conversations show up.
Tickets	N/A	Into HubSpot	Intercom tickets do NOT sync to HubSpot via any native integration. No ticket sync capability exists in either the Intercom-built or HubSpot-built apps.

Users/Leads

Two way

Becomes Contacts

Two integration paths: (1) Intercom's native HubSpot app syncs one-way Intercom→HubSpot only; creates contacts with lifecycle stage 'Lead' (not customizable). (2) HubSpot Data Sync app enables bidirectional contact sync. Custom qualification attributes can be mapped to HubSpot contact properties via settings.

Companies

Two way

Becomes Companies

Only available via HubSpot Data Sync app (bidirectional). The Intercom-built native app does NOT sync company-level attributes to HubSpot: only user-level attributes are supported.

Conversations

Into HubSpot

Becomes Timeline Activities

Via Intercom's native HubSpot app only. End-user replies sync in real-time; teammate replies only sync after conversation closes. CRITICAL: Only conversations started AFTER app connection are sent. Pre-existing conversations do NOT sync unless the customer replies after the app was connected. Intercom Series emails (mass messages) are excluded. Only one-on-one/direct conversations show up.

Tickets

Into HubSpot

Becomes N/A

Intercom tickets do NOT sync to HubSpot via any native integration. No ticket sync capability exists in either the Intercom-built or HubSpot-built apps.

Eight Things the Sync Does Not Tell You

Each one is documented, and each one has ended a migration in a bad week.

No Historical Conversation Sync

Only conversations started after the HubSpot app is connected will sync. All pre-existing conversation history is left behind. Historical data cannot be synced using the native integration.

Workaround: Use Intercom REST API with custom scripts to export historical conversations. Note: Export API only allows 90-day windows per request and has 10-second rate limits.

Conversation Transcript Export Limitations

Intercom's native CSV and S3 exports don't include conversation transcripts. UI transcript downloads skip parts of long conversations after the visible 200-line limit. Full transcripts require custom REST API extraction.

Workaround: Build custom scripts hitting the Intercom REST API to extract full conversation transcripts, working within 90-day windows and 10-second rate limits.

No Ticket Sync at All

Neither the Intercom-built nor HubSpot-built integration supports syncing Intercom tickets to HubSpot. Tickets are entirely excluded from native sync.

Workaround: Use third-party migration services (Help Desk Migration) or custom API scripts to migrate tickets as HubSpot tickets.

Intercom Native App Is One-way Only

The Intercom-built HubSpot app only sends data from Intercom to HubSpot. It cannot sync data from HubSpot back to Intercom. The separate HubSpot Data Sync app offers bidirectional sync but only for contacts and companies: not conversations.

Workaround: Use both apps in tandem: HubSpot Data Sync for bidirectional contact/company sync, Intercom native app for one-way conversation sync.

Flat Conversation Model Vs. Structured Ticket Model

Intercom uses a flat conversation model. HubSpot requires structured Contact/Company/Ticket relationships. You cannot dump Intercom conversations into HubSpot: each conversation must be mapped to a Ticket, the transcript converted to an Engagement Note, and both associated with the correct Contact and Company IDs.

Workaround: Build mapping logic that creates HubSpot tickets from conversations, converts transcripts to engagement notes, and creates proper associations.

Company Attributes Not Synced via Native App

The Intercom-built native app only supports user-level attributes. Company-level attributes cannot be sent to HubSpot through this app.

Workaround: Use the HubSpot Data Sync app for bidirectional company data synchronization.

Lifecycle Stage Locked to 'Lead'

Contacts created via the Intercom native app are automatically set to 'Lead' lifecycle stage. This is not customizable within the integration.

Workaround: Use HubSpot workflows to update lifecycle stage based on other properties after sync.

API Rate Limits Constrain Transcript Extraction

Intercom API has 10-second rate limits. The Export API only allows 90-day windows per request. Extracting full conversation history for migration requires 2-3 weeks of data extraction work for any meaningful volume.

Workaround: Plan for extended extraction timeline. Use incremental exports within 90-day windows.

Five Intercom Features HubSpot Cannot Replace

Not a workaround away. If a client depends on one of these, it belongs in the conversation before the contract.

Push Notifications

HubSpot has no native mobile push notification capability. Requires third-party service (OneSignal, Firebase, etc.).

Tooltips

HubSpot has no in-app tooltip functionality. Requires product adoption platform (Pendo, Appcues, WalkMe, etc.).

Product Tours

HubSpot has no product tour functionality. Requires product adoption platform (Pendo, Appcues, WalkMe, Userpilot, etc.).

Checklists (Onboarding)

HubSpot has no in-app checklist feature. Requires product adoption platform or custom implementation.

News (Newsfeed)

HubSpot has no in-app newsfeed feature. Blog or email newsletters are alternative channels for product updates.

One Thing a Migration Does Not Rebuild

This is Intercom's own code or product. A HubSpot migration does not port it, so it carries no hours in any estimate. It still needs a decision, because the client is giving something up.

Mobile SDK (iOS & Android)

Mobile SDK replacement requires app code changes. In-app messaging and push notification functionality gaps. May need multiple SDKs to replace Intercom's.

The 31 Items That Get Rebuilt by Hand

This is the list that separates a quote that holds from one that does not.

Data And Objects

Ticket Pipelines and Statuses -- Must Build From Scratch in HubSpot (no Ticket Sync Exists)

Custom User/contact Attributes -- Map to HubSpot Custom Properties

Conversation Tags -- Map to HubSpot Ticket Properties or Custom Multi-select Fields

Custom Data Attributes and Events -- Recreate as HubSpot Custom Properties and Behavioral Events

User Segments -- Recreate as HubSpot Lists and Smart Filters

Automation

Intercom Workflows (event-driven, Cross-channel) -- Rebuild as HubSpot Workflows (fundamentally Different Model: Intercom Is Conversation-centric, HubSpot Is Ticket/contact-centric)

Custom Bots and Resolution Bot -- Rebuild in HubSpot Chatbot Builder (bot Resolution Outcomes Won't Transfer as Structured Data)

Proactive Messaging Rules -- Rebuild Using HubSpot Workflows and Live Chat Targeting Rules

Product Tours -- No Direct HubSpot Equivalent; Use Third-party Tool or HubSpot Playbooks

Intercom Series (multi-step Campaigns) -- Rebuild as HubSpot Sequences or Workflows

Assignment Rules and Routing -- Rebuild in HubSpot Routing Rules (HubSpot's Routing Is More Enterprise-grade With ARR/tier/language-based Options)

SLA Policies -- Define From Scratch in HubSpot SLA Settings

Saved Replies / Macros -- Rebuild as HubSpot Snippets

Auto-close and Snooze Rules -- Rebuild as HubSpot Ticket Automation Workflows

Reporting

All Intercom Analytics -- Complete Redesign Required; Intercom Is Conversation-centric, HubSpot Enables Cross-service/revenue Dashboards

Resolution Time and Response Time Metrics -- Rebuild in HubSpot Service Analytics

Bot Performance Reports -- Rebuild With HubSpot Chatbot Analytics

Customer Satisfaction Scores -- Rebuild With HubSpot Feedback Surveys

Revenue Correlation Reports -- Leverage HubSpot's Native Cross-object Reporting

Sales And Marketing Config

Messenger Widget and Customization -- Rebuild Using HubSpot Live Chat Widget

Knowledge Base Articles (Intercom Articles) -- Import via HubSpot KB Importer (supports Intercom Directly, 400 Article Limit Per Batch)

Help Center / Customer Portal -- Rebuild in HubSpot Knowledge Base

Outbound Messages -- Rebuild Using HubSpot Email and In-app Messaging

Banner and Tooltip Messages -- No Direct HubSpot Equivalent; Use Third-party Tool

Custom Actions and Webhooks -- Rebuild Using HubSpot Workflows With Webhook Actions

Users And Permissions

User Roles and Permissions -- Manually Configure in HubSpot

Team Inbox Configurations -- Set up in HubSpot Conversations Inbox

Business Hours -- Configure in HubSpot Settings

Integrations

Intercom App Store Integrations -- Find HubSpot Equivalents or Connect via Zapier/Make

Messenger Home Screen Apps -- No Direct Equivalent in HubSpot

Custom Integrations via Intercom API -- Rebuild Using HubSpot API or Custom Coded Workflows

Estimate The Hours

The Sequence

Sync First, Then Migrate

Order is the content here. These are a dependency chain, and running them out of order is a documented way these migrations fail.

1
Audit Intercom Data
conversation volume, custom attributes, automation count, KB article count
2
Build HubSpot Infrastructure
ticket pipelines, custom properties, teams, routing rules
3
Export Contacts and Companies via Intercom API or CSV Export
Export contacts and companies via Intercom API or CSV export
4
Import Contacts and Companies to HubSpot (can Use HubSpot Data Sync for Ongoing Bidirectional Sync)
Import contacts and companies to HubSpot (can use HubSpot Data Sync for ongoing bidirectional sync)
5
Extract Conversation History via Intercom REST API (90-day Windows, 10-second Rate Limits
plan 2-3 weeks)
6
Map Conversations to HubSpot Tickets
create ticket, convert transcript to engagement note, associate with contact/company
7
Import Knowledge Base Articles via HubSpot KB Importer (supports Intercom Directly, 400 Article Limit Per Batch)
Import Knowledge Base articles via HubSpot KB importer (supports Intercom directly, 400 article limit per batch)
8
Manually Rebuild All Automations, Bots, Routing Rules, and SLAs in HubSpot
Manually rebuild all automations, bots, routing rules, and SLAs in HubSpot
9
Rebuild Messenger Widget as HubSpot Live Chat
Rebuild Messenger widget as HubSpot live chat
10
Run Parallel Testing Period With Both Systems Active
Run parallel testing period with both systems active
11
Switch Routing
point all channels to HubSpot, disable Intercom channels
12
Validate
check ticket associations, conversation completeness, automation behavior

Typically 3-6 weeks. Data extraction alone: 2-3 weeks for meaningful volumes due to API rate limits. Automation rebuild: 1-2 weeks depending on complexity. weeks end to end, depending on how much of the source configuration is actually in use.

Effort Estimator

How Big Is This Migration?

A handful of questions, no email required. The ranges come from the research above: every feature we mapped carries an effort figure, and this adds up the ones that apply to you.

Custom fields and properties across all records

Everything beyond the out-of-the-box fields, added up across contacts, companies, deals and anything custom.

Automations, workflows and rules

Anything that fires on its own: workflows, sequences, assignment and validation rules, approvals.

Custom reports and dashboards

Only the ones the business actually uses. Reports nobody opens do not need rebuilding.

Marketing assets to rebuild

Email templates, forms, landing pages, lists and segments taken together.

Custom objects or extra pipelines

Record types beyond contacts, companies, deals and tickets.

Third-party integrations wired into the current system

Anything connected by API, webhook or installed package that has to keep working afterwards.

Users to move across

Seats, plus whatever permission structure sits behind them.

Roughly how many contact records

This affects the sync approach and the reconciliation effort, not the per-record work. The connector moves records; people do not.

Estimated Effort

Answer a couple of questions and an hours range appears here.

Built from our research on 51 Intercom features. It is a range, not a quote.

A planning range, not a quote. It is delivery effort only, with no project management line and no agency markup, so add your own. What moves it most in practice is data quality.

What Goes Wrong Most Often

The failures that show up again and again, in roughly the order they bite.

CSV Exports Don't Include Conversation Transcripts

must use REST API

UI Transcript Downloads Skip Parts of Long Conversations After 200-line Limit

UI transcript downloads skip parts of long conversations after 200-line limit

API Rate Limits (10-second) Make Large-scale Transcript Extraction Slow

plan 2-3 weeks

Export API Only Allows 90-day Windows Per Request

Export API only allows 90-day windows per request

Conversation Model Mismatch

Intercom flat conversations must be mapped to HubSpot's structured Ticket/Contact/Company model

Intercom Workflows Are Event-driven and Cross-channel

HubSpot Workflows are if/then ticket-based, fundamentally different approach

Bot Resolution Outcomes Don't Transfer as Structured Data

Bot resolution outcomes don't transfer as structured data

Activities Exported via API Are Impossible to Get Through Standard CSV Exports Alone

Activities exported via API are impossible to get through standard CSV exports alone

Native App Sync Activities Can't Link to Both Contacts and Companies Simultaneously

Native app sync activities can't link to both contacts and companies simultaneously

Knowledge Base

400 article limit per import batch

Questions

Intercom To HubSpot, Answered

Ready to get started?

Let's do something great together.

Augment your agency's marketing team's bench with our end-to-end inbound and digital solutions and find out why we're "The HubSpot Agency for HubSpot Agencies."

Fill out this form, and someone from our Solutions team will be in touch with you soon!