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.
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
- 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
- Maps directly: 25 (49%)
- Maps partially: 21 (41%)
- No equivalent: 5 (10%)
4
Objects synced natively
8
Limitations and traps
31
Manual rebuild items
3
Source editions covered
Where this comes from: Our own research corpus, verified 2026-07-31, behind every number on this page.
The Four Objects That Sync Natively
What the connector moves for you, and which way each one flows.
Users/Leads
Two wayBecomes 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 wayBecomes 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 HubSpotBecomes 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 HubSpotBecomes 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
The states an Intercom conversation or ticket moves through.
HubSpot: Ticket pipelines and stages
Built from scratch: no sync exists between the two. Configure before importing anything.
Custom User and Contact Attributes
Attributes Intercom holds on a user, often written by the product itself.
HubSpot: Custom contact properties
Whatever writes these attributes has to be repointed at HubSpot, or the properties arrive once and then go stale.
Conversation Tags
Tags applied to conversations for grouping and reporting.
HubSpot: A multi-select ticket property
No native tag object. Tags that drive reporting should become real fields rather than free text.
Custom Data Attributes and Events
Product events Intercom records against a user, used for targeting.
HubSpot: Custom properties and behavioural events
This is application instrumentation, not CRM data. The product has to be changed to emit events to HubSpot, which is engineering work outside the migration team.
User Segments
Saved audience definitions used to target messages.
HubSpot: Active lists
Rebuilt as list rules. Segments built on product events depend on the instrumentation above landing first.
Automation
Intercom Workflows
Intercom's event-driven, cross-channel automation canvas.
HubSpot: Workflows
The models differ at the root: Intercom automates around a conversation, HubSpot around a contact and a ticket. These are redesigned rather than translated, and that should be scoped as design time, not build time.
Custom Bots and Resolution Bot
Automated answering flows that deflect conversations.
HubSpot: The chatbot builder
Rebuilt flow by flow. Resolution outcomes do not transfer as structured data, so the deflection rate reporting starts again from zero.
Proactive Messaging Rules
Rules pushing a message to a user based on behaviour.
HubSpot: Workflows and chat targeting rules
Depends on the product event instrumentation. Without it, behaviour-triggered messaging cannot be rebuilt at all, which is worth confirming before the contract.
Product Tours
In-app guided walkthroughs built in Intercom.
HubSpot: No equivalent, needs a third-party product
HubSpot does not do in-app tours. If the client runs onboarding through tours, this is a separate product purchase and belongs in the conversation before the contract.
Intercom Series
Multi-step campaigns spanning email and in-app messages.
HubSpot: Workflows and sequences
The email steps rebuild cleanly. The in-app steps have no home, so each Series has to be reviewed for what survives.
Assignment Rules and Routing
Rules distributing conversations across teammates.
HubSpot: Help desk routing rules
One of the few places HubSpot offers more than Intercom, with routing on attributes like tier and language. Worth designing fresh rather than porting.
SLA Policies
Response and resolution targets.
HubSpot: SLA settings
Defined from scratch. Configure business hours first or everything measures against a 24-hour clock.
Saved Replies
Reusable reply text teammates insert.
HubSpot: Snippets
Rebuilt by hand. Triage down to what is actually used.
Auto-close and Snooze Rules
Rules closing or deferring conversations automatically.
HubSpot: Ticket automation workflows
Snooze has no direct counterpart, so this usually becomes a status plus a delayed workflow. Test it before trusting it with live conversations.
Reporting
Intercom Analytics
Intercom's reporting over conversations and teammates.
HubSpot: Custom reports and dashboards
A redesign, not a rebuild: Intercom reports on conversations, HubSpot reports across contacts, tickets and revenue together. Some questions get better answers and some cannot be asked at all.
Resolution and Response Time Metrics
Speed-of-service reporting.
HubSpot: Service analytics
The definitions differ, so the numbers will not match the old ones. Agree the new definition with whoever reports on it before go-live.
Bot Performance Reports
Reporting on bot deflection and resolution.
HubSpot: Chatbot analytics
Starts from zero, since bot outcomes do not transfer.
Customer Satisfaction Scores
Conversation ratings collected in Intercom.
HubSpot: Customer feedback surveys
History lands in a property while new ratings come from surveys, so reporting spans two sources initially.
Revenue Correlation Reporting
Reporting that ties support activity to revenue.
HubSpot: Cross-object custom reports
This is easier in HubSpot than in Intercom, because deals and tickets already share a database. A genuine gain worth pointing at.
Sales And Marketing Config
Messenger Widget and Customisation
The Intercom messenger and its branded configuration.
HubSpot: The live chat widget
The widget swaps easily; matching the Intercom look and behaviour is where the time goes.
Knowledge Base Articles
Published help articles in Intercom Articles.
HubSpot: Knowledge base
HubSpot's importer reads Intercom directly, which makes this one of the cheaper items. It batches, so a large library is several passes.
Help Centre
The public help site built over the articles.
HubSpot: Knowledge base site
Separate from the article import. Branding, navigation and search configuration are their own build.
Outbound Messages
Proactive email and in-app messages sent to users.
HubSpot: Marketing email and in-app messaging
Email rebuilds cleanly. In-app messaging is the part that does not, so review each message for whether it survives the move at all.
Banner and Tooltip Messages
In-product banners and tooltips driven by Intercom.
HubSpot: No equivalent, needs a third-party product
Same conversation as product tours. If the product relies on these, that is a purchase decision, not a migration task.
Custom Actions and Webhooks
Outbound calls Intercom makes into other systems.
HubSpot: Workflow webhook actions
The receiving endpoint expects Intercom's payload shape, so both ends usually need work.
Users And Permissions
User Roles and Permissions
Teammate access levels.
HubSpot: Users and permission sets
Configured fresh. Audit the teammate list first rather than recreating dormant accounts.
Team Inbox Configuration
How shared inboxes are split across teams.
HubSpot: The conversations inbox and help desk
Inbox structure drives routing and visibility, so agree it before building the routing rules rather than after.
Business Hours
Operating hours shown to customers and used by SLAs.
HubSpot: Business hours settings
Small job, large blast radius. Configure before the SLAs.
Integrations
App Store Integrations
Intercom apps connecting to the rest of the stack.
HubSpot: App Marketplace integrations, or Zapier and Make
Inventory what is genuinely used before pricing replacements.
Messenger Home Screen Apps
Custom cards shown inside the Intercom messenger.
HubSpot: No equivalent
The HubSpot chat widget has no equivalent surface. Where these do real work, the function has to move somewhere else in the product.
Custom API Integrations
Bespoke code written against the Intercom API.
HubSpot: HubSpot APIs and custom coded workflow actions
Rewritten against a different object model. Scope against the code rather than a description of it.
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.
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
Yes. Data sync, mixed, covering 4 objects. What it does not do is rebuild configuration: that is the 31 items below.
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.
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.
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.
Free for basic sync. Data Hub Starter+ for custom field mappings.
5: Push Notifications, Tooltips, Product Tours, Checklists (Onboarding), News (Newsfeed). If a client depends on one, it belongs in the conversation before the contract.
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.
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.
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!