Migration Reference
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 for a procurement file.
Get The Reference And The Calculator
The full Intercom to HubSpot reference as a PDF, 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 reference as a PDF, the same reference in Markdown for your AI tool, and the full Excel effort calculator.
Intercom to HubSpot is a high migration, typically 3-6 weeks is the range to plan around, and data extraction alone can take 2-3 weeks of it once volumes are meaningful, purely because of API rate limits rather than anything about the data itself. Automation rebuild adds another 1-2 weeks on top, depending on how much complexity you are carrying across. weeks. Of the 51 features we mapped, 25 carry across as they are and 21 land with something lost: the 31 items nothing moves for you is what will actually set your timeline, not the sync.
Migration Scorecard
- Migration complexity
- High
- Typical timeline
- 3-6 weeks is the range to plan around, and data extraction alone can take 2-3 weeks of it once volumes are meaningful, purely because of API rate limits rather than anything about the data itself. Automation rebuild adds another 1-2 weeks on top, depending on how much complexity you are carrying across. weeks
- Recommended method
- The recommendation is a custom API migration, and bringing in a professional service for it rather than running it in-house. Standard CSV imports are not a shortcut worth attempting here, and neither is the native integration: it exists for ongoing coexistence between the two systems, not for the migration itself.
- 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 separate paths exist for contacts, and they behave differently. The app Intercom built moves data one way only, Intercom into HubSpot, and stamps every new contact with a fixed 'Lead' lifecycle stage nobody can change. HubSpot's own Data Sync app instead moves contacts in both directions and lets custom qualification attributes be mapped onto HubSpot contact properties through its settings. Which path is running decides whether a contact record can be trusted to reflect what happens on the HubSpot side at all.
Companies
Two wayBecomes Companies
Company sync only exists through the HubSpot Data Sync app, and only that app moves it in both directions. The app Intercom itself built has no path for company-level attributes at all, user-level only, so a team running the native app alone is missing this object entirely rather than receiving a partial version of it.
Conversations
Into HubSpotBecomes Timeline Activities
Conversations move through the Intercom-built app alone, and even there only partially. A customer's own replies sync in real time; a teammate's replies wait until the conversation is closed. Nothing that started before the app was connected sends at all, unless the customer happens to reply after connection, which in practice means the entire back catalogue of Arabic and English conversation history is invisible to this sync unless someone reopens it. Mass Series emails never sync either: only the direct, one-on-one conversations qualify.
Tickets
Into HubSpotBecomes N/A
No native path moves a ticket at all: not through the app Intercom built, not through the one HubSpot built. A ticket needs a route outside either native integration or it simply does not arrive.
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
The native integration only carries conversations forward from the moment it is connected: whatever a customer said to your support team before that point, potentially years of Arabic and English chat history, stays behind in Intercom and never reaches HubSpot. Historical data has no path through the native sync at all.
Workaround: Recovering that history means custom scripts against the Intercom REST API rather than a setting to switch on, and the API itself paces the work: a 90-day window per request and a 10-second gap enforced between calls, so pulling years of conversation out is a scripted job measured in weeks, not an afternoon.
Conversation Transcript Export Limitations
Neither Intercom's native CSV export nor its S3 export carries the conversation transcript itself, and downloading transcripts by hand through the UI loses whatever ran past the visible 200-line mark on a long thread. A conversation that ran long, which in a WhatsApp-heavy regional support queue is the normal case rather than the exception, only survives the move intact if it is pulled through the REST API.
Workaround: Full transcripts only come out through custom scripts against the Intercom REST API, built to work inside the same 90-day windows and 10-second rate limit as the historical export above. Budget the extraction as its own scripted task rather than folding it into a general data pull.
No Ticket Sync at All
Tickets do not move at all: neither the app Intercom built nor the one HubSpot built will sync a ticket across. Anything logged as a formal support case in Intercom needs a route into HubSpot that has nothing to do with either native integration.
Workaround: A third-party migration service such as Help Desk Migration, or custom scripts against both APIs, is what actually carries tickets across as HubSpot tickets. There is no native path to fall back on if that route is skipped.
Intercom Native App Is One-way Only
The app Intercom built only pushes in one direction, Intercom into HubSpot, with no path back. HubSpot's own Data Sync app closes part of the gap by syncing contacts and companies both ways, but conversations sit outside its reach either way, so a change made on the HubSpot side of a conversation never reaches Intercom.
Workaround: Running both apps together covers more ground than either does alone: HubSpot Data Sync for contacts and companies moving in both directions, the Intercom native app for conversations moving the one way it supports. Treat the two as complementary rather than choosing between them.
Flat Conversation Model Vs. Structured Ticket Model
The two platforms model a conversation differently at the root. Intercom keeps it flat; HubSpot expects it structured, tied to a Contact, a Company and a Ticket. A conversation cannot simply be copied across: it has to become a Ticket, its transcript has to become an Engagement Note, and both have to be attached to the correct Contact and Company ID before either means anything in the new system.
Workaround: The mapping logic has to do three things in sequence: create the HubSpot ticket, turn the transcript into an engagement note, and build the association to the correct contact and company record. Skipping the association step is what leaves a technically migrated conversation attached to nothing.
Company Attributes Not Synced via Native App
The native app carries user-level attributes only. Anything held at the company level in Intercom has no route through this app at all, which matters where the attribute that actually decides how a case is handled, industry, entity, contract tier, sits on the company record rather than the individual.
Workaround: Company-level data has to travel through the HubSpot Data Sync app instead, which handles it in both directions rather than the one-way native path.
Lifecycle Stage Locked to 'Lead'
Every contact the native app creates lands in the 'Lead' lifecycle stage by default, and the integration offers no setting to change that. A long-standing customer with years of support history in Intercom can arrive in HubSpot looking, on paper, like a brand-new prospect.
Workaround: A HubSpot workflow has to correct the stage after the fact, reassigning it from other properties on the record. Build that workflow before the first real batch of contacts lands, or the mislabelled stage sits on the record until someone happens to notice.
API Rate Limits Constrain Transcript Extraction
Both limits compound rather than sitting side by side: a 10-second gap enforced between API calls and a 90-day ceiling on the window each call can cover. Set against a support history that has run for years across email and WhatsApp combined, that arithmetic turns extraction into 2 to 3 weeks of dedicated work rather than a weekend job.
Workaround: Plan the timeline around the extraction from the outset rather than discovering it mid-project, and pull the data in incremental 90-day batches rather than attempting it in one pass.
Five Intercom Features HubSpot Cannot Replace
No workaround closes these. Each one is a capability you would be giving up, so decide who in the business can live without it before you commit to a date.
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, and a HubSpot migration will not carry it across: it carries no hours in the estimate. It still needs a decision before cutover, because you are the one giving something up.
Mobile SDK (iOS & Android)
Replacing Intercom's mobile SDK means changes to your app's own code, not a configuration swap, and in-app messaging and push notifications are exactly where the functionality gaps show up once it is gone. Reproducing everything a single Intercom SDK did on iOS and Android can mean stitching together more than one replacement SDK rather than finding a single one-for-one substitute.
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 stages a conversation or ticket passes through from open to closed.
HubSpot: Ticket pipelines and stages
No sync connects the two platforms' pipelines, so this is configured from a blank page. Get it right before anything is imported, since every imported record needs a stage to land in.
Custom User and Contact Attributes
Attributes Intercom keeps on a user, frequently written there by the product rather than typed in by a person.
HubSpot: Custom contact properties
Whatever system writes these attributes today has to be redirected at HubSpot after the move, or the properties land once during migration and then quietly stop updating.
Conversation Tags
Tags used to group conversations for reporting purposes.
HubSpot: A multi-select ticket property
HubSpot has no native tag object to receive these. Any tag that actually drives a report deserves to become a real field rather than free text that reporting then has to parse.
Custom Data Attributes and Events
Events the product records against a user in Intercom, used to target messages.
HubSpot: Custom properties and behavioural events
This sits in the product's own instrumentation, not in CRM data, so no migration script reaches it. The product itself has to be changed to emit events at HubSpot, which is engineering work that belongs with the product team rather than the migration one.
User Segments
Saved definitions of an audience, used to decide who a message reaches.
HubSpot: Active lists
These rebuild as HubSpot list rules. Any segment built on a product event has to wait on the instrumentation work above landing first, so sequence the rebuild accordingly.
Automation
Intercom Workflows
The event-driven automation canvas Intercom builds workflows on, spanning every channel at once.
HubSpot: Workflows
The two platforms automate around different anchors entirely: Intercom around the conversation, HubSpot around the contact and the ticket. Nothing here translates directly, so treat the rebuild as design work with its own timeline, not a mechanical port that happens to take longer.
Custom Bots and Resolution Bot
Flows Intercom uses to answer automatically, keeping a conversation from ever reaching a person.
HubSpot: The chatbot builder
Each flow is rebuilt on its own rather than in bulk, and none of the old resolution outcomes carry across as structured data. Whatever deflection rate the team reported before, the new HubSpot number starts at zero and has to be earned again.
Proactive Messaging Rules
Rules that fire a message at a user because of something they did in the product.
HubSpot: Workflows and chat targeting rules
None of this rebuilds without the underlying product event instrumentation already in place. Confirm that instrumentation exists before the contract is signed, since its absence is not something a migration budget can fix afterwards.
Product Tours
Guided walkthroughs Intercom runs inside the product itself.
HubSpot: No equivalent, needs a third-party product
HubSpot has no in-app tour feature at all. Where onboarding runs through tours today, that is a separate product to buy, and the decision belongs in the conversation before the contract, not discovered afterwards.
Intercom Series
Campaigns built across several steps, mixing email with in-app messages.
HubSpot: Workflows and sequences
The email half of each Series rebuilds without much trouble; the in-app half has nowhere to go in HubSpot. Review every Series individually to see which of its steps actually survive the move.
Assignment Rules and Routing
Rules that decide which teammate a conversation lands with.
HubSpot: Help desk routing rules
This is one of the rare places the move is a genuine upgrade: HubSpot can route on attributes Intercom cannot, tier and language among them, which matters directly for a team splitting a queue between Arabic and English speakers. Design the routing fresh rather than reproducing the old rules.
SLA Policies
Targets set for how fast a response and a resolution should land.
HubSpot: SLA settings
These are defined from nothing, and the order matters: set business hours before the SLA targets, or every measurement runs against a flat 24-hour clock that does not know a Friday from a working Sunday.
Saved Replies
Stock reply text a teammate drops into a conversation.
HubSpot: Snippets
There is no import for these: they are typed back in by hand, so triage the list down to what teammates genuinely use rather than recreating everything that ever existed.
Auto-close and Snooze Rules
Rules that close or postpone a conversation without anyone touching it.
HubSpot: Ticket automation workflows
Snooze does not map onto anything in HubSpot directly, so it is normally rebuilt as a status combined with a delayed workflow. Test that combination against a handful of real conversations before relying on it with live ones.
Reporting
Intercom Analytics
Intercom's own reporting on conversations and on teammate performance.
HubSpot: Custom reports and dashboards
Call this a redesign rather than a rebuild. Intercom's reporting sits on conversations; HubSpot's spans contacts, tickets and revenue together, so some questions come back with a better answer than before and others cannot be asked in the new system at all.
Resolution and Response Time Metrics
Reporting on how fast the team responds and resolves.
HubSpot: Service analytics
The definitions behind these metrics differ between the platforms, so the new numbers will not match the old ones on the same day. Agree the definition with whoever is accountable for reporting it before go-live, not after the first board pack looks wrong.
Bot Performance Reports
Reporting on how much the bot deflects and resolves without a person.
HubSpot: Chatbot analytics
There is no history to inherit here: bot outcomes do not transfer, so this reporting begins again from zero on day one.
Customer Satisfaction Scores
Ratings customers gave a conversation while it was still in Intercom.
HubSpot: Customer feedback surveys
The historical ratings land in a static property, while everything new arrives through surveys instead, so reporting on satisfaction spans two different sources until enough new data accumulates to retire the old one.
Revenue Correlation Reporting
Reporting that connects support activity back to revenue.
HubSpot: Cross-object custom reports
This is genuinely easier to build in HubSpot than it ever was in Intercom, because deals and tickets already sit in the same database rather than two separate systems. Worth flagging to whoever is weighing the move: it is one of the few items on this page that is a straightforward improvement.
Sales And Marketing Config
Messenger Widget and Customisation
The Intercom messenger widget and however it has been branded.
HubSpot: The live chat widget
Swapping the widget itself is quick. The time goes into matching how the Intercom version looked and behaved, colour by colour and interaction by interaction.
Knowledge Base Articles
Help articles already published through Intercom Articles.
HubSpot: Knowledge base
HubSpot's importer reads directly out of Intercom, which makes this one of the less costly items on the list. It runs in batches, so a large article library takes several passes rather than landing in one.
Help Centre
The public-facing help site that sits on top of the articles.
HubSpot: Knowledge base site
This is a separate task from importing the articles themselves: branding, navigation and search configuration are their own build, not something the article import carries along with it.
Outbound Messages
Email and in-app messages sent to users without them asking first.
HubSpot: Marketing email and in-app messaging
The email side rebuilds cleanly in HubSpot. In-app messaging is the part that does not carry across, so review each message individually to see whether it survives the move at all, rather than assuming the whole set does.
Banner and Tooltip Messages
Banners and tooltips shown inside the product, driven by Intercom.
HubSpot: No equivalent, needs a third-party product
This runs into the same wall as product tours above. Where the product genuinely depends on these, replacing them is a purchase decision for whoever holds the budget, not a task a migration team can complete on its own.
Custom Actions and Webhooks
Webhook calls Intercom fires out to other systems.
HubSpot: Workflow webhook actions
Whatever receives these calls today expects Intercom's payload shape specifically, so both the sending and the receiving end typically need rework, not just the sending side.
Users And Permissions
User Roles and Permissions
The access level each teammate holds inside the tool.
HubSpot: Users and permission sets
These are configured from a blank slate. Audit the teammate list before rebuilding it: a dormant account recreated out of habit is a permission nobody remembers granting.
Team Inbox Configuration
The way shared inboxes are divided up between teams.
HubSpot: The conversations inbox and help desk
Inbox structure decides both routing and who can see what, so it needs to be agreed before the routing rules are built, not adjusted around them afterwards. For a team split across more than one Gulf market, that agreement is usually where the market boundaries get drawn.
Business Hours
The hours shown to customers as open, which the SLA clock also runs on.
HubSpot: Business hours settings
This looks like a small setting but touches everything downstream of it: configure it before the SLAs, since a working week set to the wrong days throws off every response target measured against it.
Integrations
App Store Integrations
Apps connecting Intercom to the rest of the toolset around it.
HubSpot: App Marketplace integrations, or Zapier and Make
Inventory what is actually in use before pricing a single replacement. A stack built up over years usually has apps nobody has opened in a year sitting alongside the ones the team depends on daily.
Messenger Home Screen Apps
Custom cards that appear inside the Intercom messenger itself.
HubSpot: No equivalent
HubSpot's chat widget has no matching surface to host these. Wherever a card is doing real work rather than decoration, that function has to be relocated somewhere else in the product entirely.
Custom API Integrations
Code purpose-built against the Intercom API for this account alone.
HubSpot: HubSpot APIs and custom coded workflow actions
This has to be rewritten against a different object model altogether. Scope the effort from the actual code, not from a description of what it does, since the two rarely match after a few years of changes.
The Sequence
Sync First, Then Migrate
Order is the content here. These steps form a dependency chain, and running them out of sequence is a documented way this kind of migration fails.
- 1
Audit the Intercom Data First
conversation volume, custom attributes, how many automations are live, and the size of the knowledge base, so the scope is sized against reality rather than assumption
- 2
Build the HubSpot Infrastructure Before Any Data Moves
ticket pipelines, custom properties, teams and routing rules, all in place ahead of the first import
- 3
Export Contacts and Companies, Either Through the Intercom API or a CSV Export
Export contacts and companies, either through the Intercom API or a CSV export
- 4
Import Contacts and Companies Into HubSpot, With HubSpot Data Sync Available Afterwards to Keep the Two in Bidirectional Sync on an Ongoing Basis
Import contacts and companies into HubSpot, with HubSpot Data Sync available afterwards to keep the two in bidirectional sync on an ongoing basis
- 5
Extract the Conversation History Through the Intercom REST API, Working in 90-day Windows Against a 10-second Rate Limit
plan for 2 to 3 weeks of dedicated extraction time, not a side task
- 6
Map Each Conversation to a HubSpot Ticket
create the ticket, convert the transcript into an engagement note, then associate both with the correct contact and company
- 7
Import the Knowledge Base Through HubSpot's Own KB Importer, Which Reads Intercom Directly, in Batches Capped at 400 Articles Each
Import the knowledge base through HubSpot's own KB importer, which reads Intercom directly, in batches capped at 400 articles each
- 8
Rebuild Every Automation, Bot, Routing Rule and SLA by Hand in HubSpot
none of this carries across with the data
- 9
Rebuild the Messenger Widget as HubSpot Live Chat
Rebuild the Messenger widget as HubSpot live chat
- 10
Run a Parallel Testing Period With Both Systems Live at Once, Before Either Side Is Switched Off
Run a parallel testing period with both systems live at once, before either side is switched off
- 11
Switch the Routing Over
point every channel at HubSpot and disable the Intercom side once the parallel test is clean
- 12
Validate the Result
check that ticket associations hold, that conversation history is complete rather than partial, and that the rebuilt automations behave the way they were designed to
Typically 3-6 weeks is the range to plan around, and data extraction alone can take 2-3 weeks of it once volumes are meaningful, purely because of API rate limits rather than anything about the data itself. Automation rebuild adds another 1-2 weeks on top, depending on how much complexity you are carrying across. 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 sign-up required. The ranges come from the research above: every feature we mapped carries an effort figure, and this totals the ones that apply to your instance.
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. 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 Leave the Conversation Transcript Out Entirely
the REST API is the only route to the full text
Downloading a Transcript by Hand Through the UI Silently Drops Anything Past the 200-line Mark on a Long Conversation
Downloading a transcript by hand through the UI silently drops anything past the 200-line mark on a long conversation
The 10-second API Rate Limit Is What Makes Large-scale Transcript Extraction Slow Rather Than the Data Volume Itself
plan for 2 to 3 weeks
The Export API Caps Every Request at a 90-day Window, However Far Back the History Actually Goes
The Export API caps every request at a 90-day window, however far back the history actually goes
Model Mismatch Is the Core Problem
a flat Intercom conversation has to be mapped onto HubSpot's structured Ticket, Contact and Company relationship before it means anything there
Intercom Workflows Run Event-driven and Cross-channel; HubSpot Workflows Run If/then and Ticket-based. the Two Are Different Approaches at the Root, Not Different Dialects of the Same Idea
Intercom Workflows run event-driven and cross-channel; HubSpot Workflows run if/then and ticket-based. The two are different approaches at the root, not different dialects of the same idea
A Bot's Resolution Outcome Does Not Transfer as Structured Data, So Nothing About What the Bot Solved Before Carries Into HubSpot's Reporting
A bot's resolution outcome does not transfer as structured data, so nothing about what the bot solved before carries into HubSpot's reporting
Activities Pulled Through the API Cannot Be Recreated From a Standard CSV Export Alone
the CSV path simply does not carry them
An Activity Synced by the Native App Cannot Be Linked to a Contact and a Company at the Same Time, Which Is Exactly the Link a Multi-entity Gulf Group Needs to Make Sense of Who Did What for Which Entity
An activity synced by the native app cannot be linked to a contact and a company at the same time, which is exactly the link a multi-entity Gulf group needs to make sense of who did what for which entity
The Knowledge Base Importer Caps Each Batch at 400 Articles, So a Large Library Moves in Passes Rather Than in One Import
The knowledge base importer caps each batch at 400 articles, so a large library moves in passes rather than in one import
Questions
Intercom To HubSpot, Answered
Yes. Data sync, mixed, covering 4 objects. What it will not do is rebuild your configuration: that is the 31 items below.
Typically 3-6 weeks is the range to plan around, and data extraction alone can take 2-3 weeks of it once volumes are meaningful, purely because of API rate limits rather than anything about the data itself. Automation rebuild adds another 1-2 weeks on top, depending on how much complexity you are carrying across. weeks. Complexity is driven by automation and reporting depth, not by record count: the connector moves records, so a large database on its own will not extend the timeline.
Of 51 features we mapped, 25 (49%) carry across directly and 21 (41%) map partially, meaning something is lost or reshaped along the way. 5 have no HubSpot equivalent at any tier, worth raising before sign-off rather than after.
31 items have to be rebuilt by hand, and 8 documented limitations are not surfaced by the connector at all. Both lists are on this page, in full, for whoever is scoping the work.
Free for basic sync. Data Hub Starter+ for custom field mappings.
5: Push Notifications, Tooltips, Product Tours, Checklists (Onboarding), News (Newsfeed). If your team depends on one of these, settle it before you sign rather than discovering it at cutover, when the alternative is a custom build.
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 any estimate you are given. It still needs a decision before cutover, because you are the one giving something up.
Only in one direction. The sync is not bidirectional here, so running both systems means choosing a system of record up front and accepting drift in the other.
Ready to Get Started?
Plan Your Migration
Tell us which platform you are leaving, how much of it is custom, and when you need to be live in HubSpot. We will tell you what transfers directly, what needs rebuilding, and how long the move actually takes.