Intercom to HubSpot Service Hub migration
We migrate Contacts, Companies, Conversations, and Tickets from Intercom into HubSpot Service Hub with the conversation-to-ticket transformation handled via REST API (since S3 exports exclude transcripts), help center articles mapped to the HubSpot knowledge base, and admin-to-user ownership resolved before record import begins.
FlitStack AI migrates contacts, companies, tickets, ticket comments and ticket internal notes from Intercom to HubSpot Service Hub, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 4-6 weeks.

What moves from Intercom to HubSpot Service Hub?
Moving from Intercom to HubSpot Service Hub is a data-model migration, not a simple record copy.
Read the full summary
Intercom organizes around a conversation-centric model where messaging threads are the primary support unit; HubSpot Service Hub uses structured Tickets as the core support object. We transform Intercom Conversation threads into HubSpot Tickets with message history preserved through the REST API retrieve-conversation endpoint, since Intercom's native S3 export deliberately omits conversation transcripts. Admin accounts map to HubSpot Users, Teams map to Teams, and Tags map to HubSpot Labels. We do not migrate Intercom Outbound workflows, Custom Bots, Operator automations, or the help center article public URLs as code; we deliver a written inventory of these for the customer's admin to rebuild in HubSpot's workflow builder and knowledge base editor.
Contact (User and Lead) → Contact
Intercom Users and Leads map directly to HubSpot Contacts.
How it maps
Standard fields (email, name, phone, custom attributes) transfer 1:1. HubSpot Contact records are created before any Conversation import so that the ContactId reference is satisfied at ticket creation. Custom attributes on Intercom Contacts map to HubSpot custom Contact properties identified during schema audit.
Company → Company
Intercom Companies map to HubSpot Companies with the same field mapping: name, domain, plan, monthly_spend, and custom attributes.
How it maps
The company-contact association is preserved via HubSpot's association API so that tickets opened against a Contact carry the related Company automatically. Company deduping uses domain as the primary key.
Conversation → Ticket
Intercom Conversations map to HubSpot Tickets as the core transformation in this migration.
How it maps
Each Conversation becomes a Ticket with its subject, status (open, closed, snoozed), priority, and assigned team mapped to HubSpot's ticket properties. The Conversation ID is preserved in a custom field intercom_conversation_id__c for audit and cross-reference. Note that Intercom's S3 JSON export omits conversation transcripts entirely; we retrieve full thread content via the REST API retrieve-conversation endpoint and populate the HubSpot Ticket with message history as Ticket Comments.
Conversation Part (Message) → Ticket Comment
Intercom Conversation Parts (message type) become HubSpot Ticket Comments in chronological order.
How it maps
We retrieve body text, attachments, author type (admin, user, bot), and delivery metadata via the Intercom REST API. Attachments transfer as HubSpot file attachments linked to the Ticket Comment. Redacted or inaccessible message bodies are flagged in the reconciliation report.
Conversation Part (Note) → Ticket Internal Note
Intercom internal notes (conversation parts with author_type=admin and part_type=note) migrate to HubSpot Ticket Internal Notes.
How it maps
Internal notes are scoped to the agent who authored them and are not visible to end customers, matching Intercom's privacy model.
Conversation Part (Assignment) → Ticket Owner Assignment
Intercom assignment events (part_type=assignment) are mapped to HubSpot Ticket Owner changes.
How it maps
The assigned admin email resolves to the corresponding HubSpot User ID via the admin-to-user mapping established during scoping. If the HubSpot User does not yet exist, the assignment is held in a reconciliation queue for the admin to provision.
- ContactContact1:1
- CompanyCompany1:1
- ConversationTicket1:1
- Conversation PartTicket Comment1:1
- Conversation PartTicket Internal Note1:1
- Conversation PartTicket Owner Assignmenttransformed
+ 7 more in the mapping below
How Intercom and HubSpot Service Hub differ
The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.
| Dimension | Intercom | HubSpot Service Hub |
|---|---|---|
| Core support object | Conversation threads (messages, notes, assignments in a single inbox thread) | Structured Tickets with pipeline stages, SLA policies, and resolution status |
| AI billing model | Fin AI at $0.99 per resolution on top of seat costs; Copilot at $29/agent/month | Breeze Customer Agent bundled into Professional and Enterprise tiers; no per-resolution fee |
| Data model philosophy | Messaging-first: inbox and conversation are the product, CRM is an enrichment layer | CRM-first: every ticket ties to a Contact, Company, and optionally a Deal in the shared CRM |
| Custom objects | Custom Objects available from Advanced ($85/seat) with API access | Custom Objects available from Enterprise tier ($120/seat); Professional limited to standard objects plus custom properties |
| Help center | Native Articles and Collections with integrated article URLs tied to the Intercom workspace | HubSpot Knowledge Base as a separate object; article URLs require rebasing post-migration |
| Automation | Outbound, Operator, and Custom Bots; workspace-isolated and not exportable | Workflows with CRM-based triggers; rebuilt in HubSpot's workflow builder post-migration |
| Pricing model | Seat-based with per-resolution AI fees, channel add-ons, and Pro/Copilot extras compounding monthly | Per-seat from Starter ($15/seat) to Enterprise ($120/seat) with feature tiers; AI included at Professional+ |
What to watch for in a Intercom to HubSpot Service Hub migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
S3 export omits conversation transcripts entirely
Intercom's native Data Export to Amazon S3 stores conversation metadata and message bodies but explicitly excludes transcripts.
How we handle it
Any migration plan that relies solely on the S3 JSON export will produce Tickets in HubSpot with no message history, defeating the primary value of migrating conversation data. We address this by pulling full conversation content via the Intercom REST API retrieve-conversation endpoint for every Conversation record, which includes all message parts, attachments, and author metadata. This adds API call volume proportional to conversation count and must be accounted for in rate-limit planning and timeline estimates.
Conversations do not map to a native HubSpot Tickets object by default
Intercom Conversations are conversation threads with mixed message types (user messages, agent replies, notes, assignments); HubSpot Tickets are structured support records with a single subject, pipeline, stage, and comment thread.
How we handle it
There is no automatic one-click mapping. We transform each Conversation into a Ticket by extracting the subject from the first user message or conversation title, mapping the current state (open, resolved, snoozed) to HubSpot Ticket status, and collapsing all subsequent message parts into Ticket Comments. The transformation logic must be defined and validated during scoping, because Intercom conversations often contain informal subjects that require normalization for HubSpot's ticket subject field.
Workspace isolation prevents workflow migration
Intercom workspaces operate in isolation — Outbound workflows, Operator, Custom Bots, and help center content cannot be exported or moved to HubSpot.
How we handle it
Teams planning this migration must rebuild all automation logic in HubSpot's workflow builder. We do not migrate Intercom automation as code. We deliver a written inventory of every active Intercom workflow with its trigger, conditions, actions, and recommended HubSpot workflow equivalent, plus the help center article list for the customer's admin to recreate in HubSpot Knowledge Base. This rebuild scope is the most significant post-migration admin effort and should be estimated separately.
Two-year conversation history cap on Intercom's REST API
Intercom's historical data retrieval via the REST API is scoped to two years of conversation data by default.
How we handle it
Teams with longer support histories cannot retrieve older conversations through the standard API endpoints. We scope and document how much historical volume falls outside the two-year window during discovery, and present options: accept the gap for the migration scope, pursue a separate archival approach for older records, or evaluate whether the Intercom S3 export (despite missing transcripts) provides metadata for records outside the window.
Private app rate limits share workspace quota
Private apps installed in an Intercom workspace share a 25,000 API calls per minute workspace-level rate limit.
How we handle it
During migration, our API pipeline competes with any other active Intercom integrations for the shared quota. We monitor X-RateLimit-Remaining and X-RateLimit-Reset headers and dynamically throttle ingestion to stay within available quota. We coordinate with the customer on scheduling migration windows when other integration activity is minimal, and we batch requests to reduce per-call overhead.
How the migration runs
Discovery and schema audit
We audit the source Intercom workspace across plan tier (Essential, Advanced, Expert), workspace configuration, admin count, team structure, conversation volume, custom attributes, custom objects, active tags, and help center article count.
What this step covers
We pull the full Data Attributes list via the Intercom API to generate the complete field inventory. We pair this with a HubSpot edition check (Starter at $15/seat for basic tickets, Professional at $90/seat for SLA and knowledge base, Enterprise at $120/seat for custom objects and advanced automation) and document the conversation-to-ticket transformation logic including subject extraction rules, status mapping, and comment threading strategy. The discovery output is a written migration scope with object-level mapping, a HubSpot edition recommendation, and the automation inventory template.
Schema preparation in HubSpot
We pre-create the HubSpot environment with the migrated schema: custom Contact and Company properties matched to Intercom custom attributes, Ticket pipelines and stages mapped from Intercom conversation states (open, resolved, snoozed), Team structures aligned to Intercom Teams, Labels for the tag migration, and a Knowledge Base section if articles are in scope.
What this step covers
If the destination is Professional tier, we flatten any Intercom Custom Objects into standard objects plus custom properties during this phase. All schema changes are deployed to a HubSpot test portal first for validation before production migration begins.
Conversation transcript retrieval and ticket creation
We retrieve full conversation content via the Intercom REST API retrieve-conversation endpoint for every Conversation record in scope, since S3 exports exclude transcripts.
What this step covers
Each conversation is transformed into a HubSpot Ticket with subject extracted from the first user message, status mapped from the Intercom state, and priority from the conversation priority field. Message parts are threaded as Ticket Comments in chronological order. Admin assignments resolve via the admin-to-user email mapping. Attachments transfer as HubSpot file objects linked to the relevant Ticket Comment. We sequence retrieval in batches with rate-limit handling to stay within the 25,000 calls/minute workspace quota.
Contact, Company, and admin-to-user migration
We migrate Contacts (Users and Leads), Companies, Admins, Teams, Tags, and Segments in dependency order before finalizing ticket migration.
What this step covers
Contacts are created first so that the HubSpot ContactId reference is available when Conversations are converted to Tickets. Companies are created with domain deduping. Admins are matched to HubSpot Users by email and held in a reconciliation queue for any without a matching User account. Tags are migrated to HubSpot Labels for later application to the migrated records.
Help center article migration and URL mapping
We migrate Intercom Help Center Articles to HubSpot Knowledge Base articles, including titles, bodies, authors, collection hierarchy, and publication states.
What this step covers
Article content transfers directly. Public article URLs require rebasing because HubSpot knowledge base URLs are workspace-scoped. We deliver a URL mapping document listing each original Intercom article URL and the corresponding HubSpot knowledge base URL, so the customer's admin can configure redirects in their DNS or CMS layer post-migration.
Sample migration, validation, and production cutover
We run a sample migration of up to 100 random Conversation-to-Ticket pairs plus associated Contacts and Companies into a HubSpot staging portal.
What this step covers
The customer's support operations lead reviews the sample for accuracy (message threading, subject extraction, owner assignment, tag application) and signs off before production migration begins. We run a delta migration window during cutover to capture any records modified between the initial extraction and the production migration start. We deliver the automation and help center rebuild inventory to the customer's admin team for post-migration rebuild.
- Connect
- Map
- Sample
- Migrate
- Verify
- Contacts48,210 / 48,210 Done
- Companies9,134 / 9,134 Done
- Deals6,377 / 11,920 In progress
- Before sample runRestore point 01Restore
- Before full migrationRestore point 02Restore
- After verificationRestore point 03Current
How long it takes, and what drives the quote
A quote scales with conversation volume, custom attribute complexity, and the decision to migrate or rebuild automation. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for Intercom to HubSpot Service Hub →Why teams move from Intercom to HubSpot Service Hub
- Intercom's Fin AI pricing ($0.99 per resolution) creates unpredictable monthly bills as automation improves. Teams that achieve high automation rates are charged more for doing better, a model that compounds with volume. HubSpot Service Hub Professional ($90/seat) and Enterprise ($120/seat) bundle Breeze Customer Agent without per-resolution fees, giving teams predictable AI costs regardless of how many inquiries the AI handles. Reviewers on comparison sites consistently cite this pricing unpredictability as the tipping point for migration.
- Intercom is a messaging-first platform where the inbox is the product. Support tickets live alongside marketing messages and sales conversations in the same thread model. HubSpot Service Hub ties every ticket to a Contact, Company, and Deal in the shared CRM, so support reps see deal context, lifecycle stage, and marketing history without switching tools. Operations leads moving from chat-heavy SaaS support to structured customer success cite this unified context as the primary driver.
- Intercom's workspace isolation means automation rules, Custom Bots, Outbound workflows, and the help center cannot be moved between environments or duplicated for staging. Teams planning a migration must rebuild all automation logic from scratch in HubSpot. HubSpot workflows live inside the CRM and can be exported via HubSpot's API and template tools, giving teams a starting point for rebuild rather than a blank slate.
- HubSpot Service Hub Professional ($90/seat) includes SLA tracking, 15 ticket pipelines, a help desk workspace, a knowledge base, NPS and CSAT surveys, and customer health scoring. Intercom gates SLA management behind the Expert plan ($132/seat) and does not offer native NPS, CSAT, or health scoring as standard tools. Mid-market teams moving from Intercom Advanced ($85/seat) to HubSpot Professional gain features that Intercom reserves for its top tier, at a lower per-seat price.
- HubSpot's ecosystem includes over 550 integrations versus Intercom's roughly 300. Teams running HubSpot CRM for sales and marketing gain a native Service Hub that shares the same contact, company, and deal records without a third-party sync. The operational overhead of maintaining a separate Intercom workspace with its own contact duplicates disappears when support moves into the unified HubSpot platform.
Questions, answered
Intercom to HubSpot Service Hub migration questions
How long does an Intercom to HubSpot Service Hub migration take?
Most migrations land between four and six weeks for accounts under 10,000 Contacts, 5,000 Companies, and 20,000 Conversations with no custom objects or help center migration. Migrations with custom objects, high-volume conversation histories (over 100,000 threads requiring individual REST API retrieval), or help center article migration requiring URL rebasing move to eight to twelve weeks because of transcript retrieval overhead, schema flattening for Professional tier, and knowledge base content mapping.
Do Intercom workflows, bots, and automations migrate to HubSpot?
No. Intercom Outbound workflows, Operator, Custom Bots, and help center article logic do not migrate as code. These automation systems are workspace-isolated in Intercom and have no export mechanism. We deliver a written inventory of every active Intercom workflow with its trigger conditions, actions, and recommended HubSpot workflow equivalent. The customer's admin rebuilds these in HubSpot's workflow builder post-migration. Help center articles migrate as content but without the publication state automation or article-specific URLs, which are documented in our URL mapping deliverable for manual redirect configuration.
Will we lose conversation message history during migration?
No, provided the migration plan accounts for the transcript retrieval gap. Intercom's native S3 JSON export deliberately excludes conversation transcripts. We retrieve full conversation content via the REST API retrieve-conversation endpoint for every Conversation record, including all message parts, attachments, author metadata, and internal notes. Each message becomes a Ticket Comment in HubSpot in chronological order. If the conversation count is large (over 50,000 threads), transcript retrieval adds measurable API time and is the primary driver of longer timelines for high-volume migrations.
How do we handle Intercom Fin AI resolution data in HubSpot?
Fin AI resolution records (showing which conversations were resolved by the AI agent) have no direct HubSpot equivalent. We migrate the conversation metadata including resolution status but do not replicate the per-resolution billing model. If the customer needs AI resolution tracking in HubSpot, we recommend using Breeze Customer Agent (bundled into Professional and Enterprise) as the replacement AI service and setting up a custom Ticket property to track resolution source (human vs AI) going forward.
Can we keep Intercom for chat while moving support tickets to HubSpot Service Hub?
This is technically possible using the HubSpot-Intercom integration, but it creates a dual-inbox situation that most teams find operationally difficult. Maintaining Intercom for live chat alongside HubSpot for ticket management requires the integration to sync messages bidirectionally, which adds latency and can result in duplicate records if not configured carefully. Teams that choose this path do so during a transition period and plan to migrate chat to HubSpot'sConversations Inbox as a second phase. We do not scope dual-platform migrations as standard; we scope the full Intercom exit migration and note the dual-platform option as a phased approach.
How are Intercom Custom Objects handled if we are on HubSpot Professional?
Intercom Custom Objects are available from Advanced plan ($85/seat) and are commonly used by mid-market teams. HubSpot Custom Objects require Enterprise tier ($120/seat). If the destination is Professional tier, we flatten Intercom Custom Object instances into HubSpot standard objects (Contact, Company, or Ticket) using custom properties. This requires a schema design session during scoping to define which standard object receives the custom data and how lookup relationships are preserved without a custom object API name. The customer may choose to upgrade to Enterprise for the migration if custom object fidelity is a hard requirement.
What happens to our Intercom Tags and Segments after migration?
Intercom Tags migrate to HubSpot Labels, which are applied to the corresponding Contact and Ticket records post-import. Tags that applied to Contacts become Labels on Contact records; tags that applied to Conversations become Labels on Ticket records. Segments are migrated as static HubSpot Lists capturing the membership snapshot at migration time. Dynamic recomputation of segment membership based on future contact behavior is not migratable; the customer's admin rebuilds dynamic segmentation using HubSpot's list filters or CRM-based audience logic in HubSpot.
Related migrations
HubSpot implementation
Set up HubSpot Service Hub and migrate into it as one engagement.
See the service → Freshdesk to HubSpot Service HubMapping · history · rollbackSalesforce Service Cloud to HubSpot Service HubMapping · history · rollbackZendesk to HubSpot Service HubMapping · history · rollback Intercom to ZendeskMapping · history · rollbackIntercom to FreshdeskMapping · history · rollbackSources: official documentation
- Format import files — HubSpot Knowledge Base
- Batch limits — HubSpot Knowledge Base
- Batch read associations — HubSpot Knowledge Base
- Import knowledge base articles — HubSpot Knowledge Base
- Import your user data into Intercom — Intercom Help
- Import your customers — Intercom Academy
- Create and track Custom Data Attributes (CDAs) — Intercom Help
Get a quote
Moving from Intercom to HubSpot Service Hub?
Tell us roughly how many records and objects you have. We scope the mapping and the HubSpot Service Hub setup with you, then send a quote.
Get a quote