HubSpot Service Hub to Intercom migration requires 3–5 API calls per ticket for extraction, has no dedicated bulk import API on Intercom's side, and takes 6–10 weeks for a typical team.
There is no native migration path from HubSpot Service Hub to Intercom. The two platforms differ fundamentally: HubSpot uses a CRM-integrated service model where tickets are separate containers linked to engagements via an Associations API (requiring 3–5 API calls per ticket to reconstruct a thread), while Intercom uses a messenger-first conversation parts model with no dedicated bulk import API for conversations. Custom API-based extraction, engagement-to-conversation-part transformation, property pruning, and routing logic (Conversations vs. Intercom Tickets) are all required, making this one of the most technically demanding helpdesk migration paths available.
Read this first
Pair-specific gotchas that catch teams out. Each one has cost somebody a weekend.
Do not assume the native HubSpot app gives you bidirectional CRM sync
Intercom's HubSpot app is documented as one-way from Intercom to HubSpot. It surfaces HubSpot data in the Inbox and logs Intercom conversations to HubSpot, but bidirectional sync requires HubSpot's Data Sync app or middleware. (intercom.com)
Critical order of operations
Custom attributes must be created with typed definitions BEFORE loading data. Contacts and companies must exist in Intercom BEFORE creating conversations. The timestamp test must happen before committing to full migration.
The runbook
Work top to bottom. Tick steps as you go — your progress is saved in this browser.
01 Discovery Establish why you are moving, what "done" means, and who signs off.
Objective A written scope with agreed success criteria, a named owner per workstream, and a budget approved by finance.
Keep these open
-
Pull the real numbers out of HubSpot Service Hub
Export counts for tickets (open and closed separately), contacts, organisations, attachments, macros, triggers, automations, views and SLA policies. Note the oldest ticket date — history depth drives the whole timeline. Estimating from memory is the single most common cause of a blown migration window.
Data Profiler Get real record counts instead of estimating from memory -
Decide what history actually moves
Agree a cut-off with the support lead: all history, last 24 months, or open tickets plus a read-only archive. Every extra year of closed tickets adds API time and cost without adding much agent value. Get this in writing — it is the decision people relitigate mid-cutover.
A "move everything" default is what turns a two-week migration into a two-month one.
COI & ROI Calculator Build the 36-month business case you will need for sign-off -
Confirm Intercom can hold your support model
Walk your current workflow through Intercom: multi-brand, business hours, SLA targets, CSAT, side conversations, public vs internal notes, and any channel you depend on (voice, chat, WhatsApp, social). List anything with no native equivalent — those are project risks, not configuration details.
-
Build the business case
Model licence delta, migration effort, agent retraining, and the cost of staying put (Cost of Inaction). Executives approve a number, not a plan, and you will be asked for it again at the go/no-go.
Helpdesk Migration Planner Turn ticket volume into a dated HubSpot Service Hub → Intercom timeline -
Name owners and set the go/no-go date
One named owner each for data, configuration, integrations, and agent enablement, plus a decision-maker who can call a rollback. Put the go/no-go meeting in calendars now, 48 hours before the freeze.
HubSpot Service Hub → Intercom specifics
- Intercom's Messenger
- for in-product communication with persistent conversation history.
- A simpler agent experience
- moving from HubSpot's CRM-heavy interface (too many objects, properties, and CRM noise for agents who only handle support) to Intercom's conversation-focused Inbox.
- CRM-integrated service vs. messenger-first CDP
- HubSpot's contact model is CRM-shaped (lifecycle stages, deals, marketing attribution). Intercom's is engagement-shaped (last seen, custom events, session data). The migration translates between paradigms, not just platforms.
- Engagement model vs. conversation parts model
- HubSpot separates the ticket container from content (engagements linked via Associations API). Intercom keeps the thread inside the conversation as parts. Each HubSpot engagement becomes an Intercom conversation part with type-specific transformation.
- Cross-object Workflows vs. conversation-scoped Workflows
- HubSpot Workflows span objects — trigger on a contact property change, update a ticket. Intercom Workflows are conversation-scoped. Cross-object automation has no Intercom equivalent.
Don't move on until
- Record counts confirmed for tickets, contacts, organisations and macros
- Success criteria signed off by the support lead
- Freeze window provisionally booked with the business
02 Data Audit Find out what is actually in the data before you try to move it.
Objective A profiled, cleaned export with every quality defect either fixed at source or explicitly accepted.
Keep these open
-
Take a full HubSpot Service Hub export and profile it
Export to CSV or JSON and profile every file: row counts, null rates per column, distinct values, and type consistency. Compare row counts against the API totals from Discovery — a gap here means your export is silently truncated, usually by pagination.
Data Profiler Profile the HubSpot Service Hub export for nulls, outliers and type drift -
Validate file structure before anyone writes a transform
Check delimiters, quoting, encoding (expect UTF-8, watch for BOMs and Latin-1), duplicate headers, and embedded newlines in ticket bodies. Ticket descriptions with raw newlines and commas break naive CSV parsers and silently shift columns.
A single unescaped quote in one ticket body can shift every subsequent column without any error.
CSV Validator Catch broken headers and ragged rows in the raw export -
Inventory PII and set retention
Scan for emails, phone numbers, payment card fragments, national IDs and anything else regulated in ticket bodies and custom fields — support tickets are where customers paste things they should not. Decide what gets migrated, masked, or dropped, and record the legal basis.
Ticket bodies and attachments routinely contain card and ID data that never appears in a structured field.
PII & Compliance Scanner Find regulated fields before they land in a new system -
Quantify duplicates, orphans and dead references
Count duplicate contacts (same email, different casing), tickets whose requester no longer exists, organisations with no members, and attachments whose parent ticket is gone. Fix these in HubSpot Service Hub where you can — migrating them just moves the mess.
Data Cleaner Strip empty rows, stray whitespace and dead columns -
Clean and normalise the export
Trim whitespace, drop empty rows and columns, normalise casing on emails and tags, and standardise every timestamp to UTC ISO 8601. Timezone drift is invisible at load time and shows up weeks later as SLA reports nobody can reconcile.
-
Produce a masked copy for sandbox work
Generate a realistic but fake version of the export for testing and for any vendor who needs sample data. Loading real customer PII into a sandbox is a breach in most jurisdictions, and sandboxes are rarely covered by your DPA.
PII Masker Generate a safe copy for sandbox and vendor testing
Don't move on until
- Export parses cleanly with no ragged rows or encoding errors
- PII inventory complete and retention decisions recorded
- Duplicate and orphan records quantified and triaged
03 Field Mapping Turn two schemas into one signed-off mapping spec.
Objective A reviewed field-level mapping covering every object, with an explicit decision for every field that has no target.
Keep these open
-
Generate the first-pass HubSpot Service Hub → Intercom field map
Start from an automated match on both schemas, then review every row by hand. Automated matching gets the obvious 70% right and is confidently wrong on the rest — especially anything named "type", "status" or "custom_field_1".
Schema Mapper Opens pre-loaded with the HubSpot Service Hub → Intercom field pair -
Map status, priority and channel values, not just field names
Enumerate every value in each picklist on both sides and map them explicitly. Value-level mismatches are the defect class that survives all the way to production because the field itself mapped fine — a ticket that should be "Pending" arriving as "Open" reopens SLA clocks.
Statuses with no target equivalent (on-hold, pending-customer) need a policy decision, not a best guess.
-
Decide how custom fields land
Create the target custom fields first, matching type exactly (a dropdown mapped to free text can never be mapped back). Where Intercom has no equivalent, decide between a new custom field, a tag, or a note appended to the ticket body — and record which.
-
Resolve identity and threading
Decide how source IDs are preserved — most platforms will not let you set the primary key, so keep the original ID in a custom field. Without it, reconciliation becomes fuzzy matching and every future support question about an old ticket is unanswerable.
Losing the original ticket ID makes reconciliation and rollback effectively impossible.
-
Plan attachments, inline images and threading order
Confirm size limits, allowed MIME types, and whether inline images survive as attachments or need rehosting. Decide the comment ordering and author attribution rules: comments loaded out of order, or all attributed to the API user, destroy the conversation history agents rely on.
-
Freeze and sign off the mapping spec
Version the spec, walk the support lead through it row by row, and get explicit sign-off. Any change after this point goes through change control — mid-flight mapping edits are how partial loads happen.
HubSpot Service Hub → Intercom specifics
- Intercom Tickets
- (distinct from Conversations) handle tracked, async issues with explicit operational states (submitted/in_progress/resolved/waiting_on_customer). If you choose Intercom Tickets, create ticket types first — Intercom requires them as a prerequisite. (developers.intercom.com)
- Multiple ticket-contact associations
- HubSpot tickets can be associated with multiple contacts. Intercom conversations have one contact. Pick the primary requester and document others as internal note parts.
- Attachment size limits
- Intercom enforces a 20 MB per file attachment limit and restricts certain file types (executables, scripts). HubSpot attachments exceeding these limits will silently fail during bulk load unless you pre-filter. Download attachments from HubSpot File Manager, validate size and type, then re-upload to Intercom, updating URLs in conversation bodies.
Don't move on until
- Every source field is mapped, deliberately dropped, or parked in a custom field
- Status, priority and channel value maps agreed with the support lead
- Mapping spec version-controlled and signed off
04 Test Migration Prove the pipeline on a small, representative slice.
Objective A pilot load into a Intercom sandbox that reconciles cleanly and has been reviewed by real agents.
Keep these open
-
Stand up a Intercom sandbox that matches production config
Create the custom fields, groups, brands, business hours and SLA policies first. A pilot into a default sandbox tests nothing, because the failures you care about are all configuration mismatches.
-
Pick a deliberately nasty pilot sample
Take 500-1000 records chosen for difficulty, not convenience: the longest ticket threads, tickets with the most attachments, non-Latin character sets, merged and split tickets, deleted requesters, and every status value. A clean random sample proves only that easy records are easy.
-
Run the load with masked data and instrument everything
Log every API request and response with its source record ID. When 40 records fail out of 10,000 you need to know exactly which ones and why, without re-running the whole batch.
PII Masker Never load real customer PII into a sandbox -
Measure real throughput against the rate limit
Record achieved records-per-hour under Intercom's actual rate limits, including retries and backoff. Extrapolate to the full volume: if the maths says the full load exceeds your freeze window, you fix that now, not on cutover night.
Published rate limits are ceilings, not throughput. Assume real-world rates are meaningfully lower once retries and backoff are counted.
-
Reconcile the pilot and triage every failure
Diff source against target on record counts and field-level values. Every discrepancy gets a root cause and a fix — "probably fine" at pilot scale becomes thousands of broken records at full scale.
Migration Validation Tool Diff the pilot batch against source before scaling up -
Put real agents in front of the pilot data
Have two or three agents work sample tickets end to end in the sandbox. They find the things reconciliation cannot see: unreadable threading, missing context, macros that no longer make sense. Fix the mapping, then re-run.
HubSpot Service Hub → Intercom specifics
- Store original dates in custom attributes
- (e.g., original_created_at) — timestamps visible to agents but not in conversation sort order.
- Prepend original date to conversation body
- visible in the thread but not machine-readable.
- Author attribution
- Customer messages show as contact-authored parts, agent messages as admin-authored parts. Check for the "Migration" fallback admin — if it appears on too many conversations, the owner mapping has gaps.
- Agent UAT
- Have 2–3 agents work in Intercom Inbox for 1–2 days. Test CRM context sufficiency (is the sidebar data enough?), Conversation/Ticket distinction (do agents understand which is which?), Fin handoff behavior, and macro/Saved Reply adequacy.
- Long-thread spot check
- For tickets with 20+ engagements, verify from both the HubSpot source count and the Intercom UI or paginated API read. The 500-part retrieval ceiling can make a correct migration look incomplete during validation.
Don't move on until
- Pilot batch reconciles to 100% on record counts
- Agents have reviewed sample tickets and confirmed they are workable
- Measured throughput extrapolates to a viable full-load window
05 Cutover Execute the switch inside a controlled, reversible window.
Objective All in-scope data live in Intercom, agents working in the new system, and a rollback path that stayed available throughout.
Keep these open
-
Pre-load history before the freeze
Load closed tickets and contacts days or weeks ahead while HubSpot Service Hub stays live. Only open tickets and the final delta need to move inside the freeze — this is the single biggest lever on window length.
Helpdesk Migration Planner Size the freeze window from Intercom's real API limits -
Publish the runbook with times, owners and abort criteria
A timed sequence: freeze start, final export, delta load, channel switch, smoke test, go/no-go, agent switch. Name who does each step and the explicit condition that triggers a rollback. Decide the abort criteria before the night, when nobody wants to be the one to call it.
-
Freeze HubSpot Service Hub and take the final delta
Stop new ticket creation, let agents finish in-flight replies, then export everything changed since the pre-load. Announce the freeze to the whole business, not just support — someone always tries to raise a ticket during it.
Tickets created during an unenforced freeze land in the old system and are the most common source of permanently lost data.
-
Load the delta and open tickets
Run the delta load, then reconcile counts before touching any channel. Do not repoint email until the delta has verified — an inbound ticket arriving mid-load is far harder to untangle than a few extra minutes of freeze.
Migration Validation Tool Confirm the final delta landed before you reopen -
Repoint channels and verify with live traffic
Switch email forwarding and MX or connector settings, update chat widgets and web forms, and re-authorise integrations. Then send real test tickets through every channel and confirm each lands, routes and triggers the right automation.
Email forwarding changes can take up to a full DNS TTL to propagate — check the TTL days in advance and lower it if needed.
Cron Expression Builder Schedule the delta syncs that run through the freeze -
Run the go/no-go and switch the agents
Walk the exit criteria with the decision-maker, call it explicitly, then move agents over with a named person on hand for the first few hours. Keep HubSpot Service Hub read-only rather than cancelled — cancelling the old contract on day one removes your only fallback.
HubSpot Service Hub → Intercom specifics
- Rollback plan
- Keep HubSpot Service Hub accessible for 8–12 weeks post-migration. Rollback procedure: revert email forwarding rules to HubSpot, remove Intercom Messenger snippet, reactivate HubSpot chatflows, notify agents to return to HubSpot Inbox. Rollback should be executable within 2–4 hours.
Don't move on until
- Full historical load complete and counts matched
- Inbound channels repointed and verified with live test tickets
- Rollback decision point passed explicitly, not by default
06 Validation Prove the migration is complete, then close it out.
Objective Documented evidence that data, workflow and reporting all survived, and a signed acceptance.
Keep these open
-
Run the full reconciliation
Compare source and target on every object: total counts, counts by status, counts by group, attachment counts, and field-level spot checks on a random sample. Produce one report you can hand to an auditor.
Migration Validation Tool Reconcile HubSpot Service Hub and Intercom record-for-record -
Verify field completeness, not just record counts
Re-profile the loaded data and compare null rates per field against the source profile. Matching record counts with a field that silently arrived empty is the failure mode counts alone will never catch.
Data Profiler Prove field completeness held up through the load -
Rebuild reporting and compare against baselines
Recreate your core dashboards — volume, first response time, resolution time, CSAT — and compare to pre-migration figures for the same period. Explain every variance; a changed SLA calculation is a real finding, not a rounding error.
SLA and first-response metrics are usually recalculated from the loaded timestamps, so they will differ if any timestamp mapping was approximate.
-
Test the workflow layer end to end
Fire every trigger, automation, SLA escalation, macro and notification with a live ticket. Workflow does not migrate — it gets rebuilt — so it is untested until someone has actually watched it run.
-
Confirm compliance and produce the audit trail
Re-scan the loaded data for regulated fields, confirm retention and deletion policies are configured in Intercom, and file the evidence with your PII decisions from the audit phase.
PII & Compliance Scanner Produce the compliance evidence your auditor will ask for -
Sign off, then decommission on a schedule
Get written acceptance against the Discovery success criteria. Keep HubSpot Service Hub read-only for an agreed period (30-90 days is typical), take a final archive export, and only then cancel. Diarise the decommission date so it does not quietly renew.
-
Record-count reconciliation
Tickets exported from HubSpot vs. conversations + tickets created in Intercom. Engagement counts may differ if sparse types were discarded — document the delta and the reason.
HubSpot Service Hub → Intercom specifics
- Engagement assembly verification
- For a sample of 50+ conversations (stratified by ticket age and engagement count), compare the HubSpot ticket timeline against Intercom conversation parts. Verify every email appears as a reply part, every note as a note part.
- Timestamp verification
- Confirm conversations show original HubSpot dates, not migration-date timestamps. Verify per-part timestamps on both the initial message and subsequent replies.
- Attachment verification
- Verify attachments render correctly. Check for broken image links (CID references, expired HubSpot CDN URLs).
- HubSpot integration app validation (decoupled)
- Verify the sidebar shows correct CRM data for a sample of conversations. Test that new Intercom conversations log back to HubSpot contact records.
- Fin AI validation
- Submit your top 20 most common customer questions and verify resolution quality. Identify article gaps. Test handoff behavior — confirm Fin routes to the correct team when it can't resolve.
Don't move on until
- Full reconciliation report attached to the project record
- Reporting baselines match pre-migration figures within agreed tolerance
- Formal acceptance signed and archive retention scheduled
Field mapping reference
The field-by-field mapping for each object. Use this as the starting point for your mapping spec.
HubSpot Service Hub Intercom Object
| HubSpot Service Hub field | Intercom field | Notes |
|---|---|---|
| Tickets | Conversations AND/OR Tickets | Route by pipeline: "Support" → Conversations, "Engineering Escalation" → Tickets. Create ticket types first if using Intercom Tickets. |
| Engagements (email) | Conversation Parts (reply, public) | Preserve HTML body, map HubSpot Owner → Intercom Admin ID, Contact → Contact ID. Carry over timestamp. |
| Engagements (note) | Conversation Parts (note, internal) | Map author, preserve timestamp and body. |
| Engagements (call) | Conversation Parts (note, internal) | Include call metadata: duration, recording URL, disposition. |
| Contacts | Contacts (role = "user" or "lead") | Core identity fields map directly. CRM fields (lifecycle stage, lead status) → custom attributes or stay in HubSpot. |
| Companies | Companies | Name and domain map directly. CRM properties (revenue, employee count) → custom attributes or stay in HubSpot. |
| Ticket Pipelines | No direct equivalent | Pipeline stages → Intercom conversation state (open/closed/snoozed) + custom attributes for stage granularity. |
| Properties (custom) | Custom Attributes | Intercom types: string, integer, boolean, date, list. Calculated and score properties migrate as static values only. |
| Knowledge Base | Articles | Categories → collections, subcategories → sections, articles → articles. |
| Snippets | Macros | Macros can include actions: assign, tag, snooze, close. |
| Workflows | Workflows (conversation-scoped) | See Workflow decomposition section below. |
Risk matrix
Per-object risk for this pair. Plan extra validation around anything marked high.
| Object | Risk | Notes |
|---|---|---|
| Tickets | high | Each ticket requires multi-endpoint extraction (3–5 API calls) and a routing decision between Intercom Conversations and Tickets, with no bulk import path on the Intercom side. |
| Engagements (Emails, Notes, Calls) | high | Engagements must be individually transformed into typed conversation parts with correct timestamps and author mapping, and the create-conversation endpoint does not support HTML in the body. |
| Contacts | low | Core identity fields map directly and contacts can be imported via CSV, though CRM-specific fields like lifecycle stage require classification as custom attributes or exclusion. |
| Companies | medium | Intercom's CSV import does not support company data, so companies must be loaded via API or the integration app, and CRM properties like revenue translate awkwardly to custom attributes. |
| Custom Fields/Properties | medium | HubSpot instances often have 50–200+ custom properties that must be audited, pruned, and recreated as typed custom attributes in Intercom before data loading; calculated and score fields migrate as static values only. |
| Knowledge Base Articles | low | Categories map to collections and articles map directly, though Intercom limits collection nesting to three levels which may require restructuring deep hierarchies. |
| Workflows/Automations | high | Cross-object HubSpot Workflows have no Intercom equivalent since Intercom Workflows are conversation-scoped, requiring full decomposition and partial rebuilds with potential middleware. |
| Ticket Pipelines | medium | Intercom has no pipeline Kanban view, so pipeline stages must be flattened into conversation states (open/closed/snoozed) plus custom attributes to preserve stage granularity. |
| Attachments | medium | Intercom enforces a 20 MB per file limit and restricts certain file types, so oversized or disallowed attachments will silently fail unless pre-filtered and re-uploaded. |
| Snippets/Macros | low | HubSpot Snippets map to Intercom Macros with added action capabilities, though Playbooks have no direct equivalent and must be recreated as Saved Replies or Workflow-based paths. |
The hard parts
What makes this specific migration difficult, beyond the mechanics.
Multi-Endpoint Ticket Extraction
Reconstructing a complete HubSpot ticket thread requires 3–5 API calls per ticket across the Tickets, Associations, and legacy Engagements endpoints, each with separate rate limits and pagination.
No Bulk Conversation Import
Intercom lacks a dedicated bulk import API for conversations, forcing sequential API writes where each engagement must be transformed into a typed conversation part (reply, note) with individual calls.
Cross-Object Workflow Loss
HubSpot Workflows that span objects—such as triggering on a contact property change to update a ticket—have no equivalent in Intercom's conversation-scoped Workflow engine and must be decomposed or rebuilt with middleware.
CRM-to-CDP Data Model Translation
HubSpot's CRM-shaped contact model (lifecycle stages, deals, marketing attribution) must be translated into Intercom's engagement-shaped CDP model (roles, custom events, session data), requiring property pruning and paradigm remapping rather than a lift-and-shift.
Tickets vs. Conversations Routing
HubSpot tickets must be routed to either Intercom Conversations or Intercom Tickets based on pipeline and type, with Intercom Tickets requiring pre-created ticket type definitions as a prerequisite.
Multi-Contact Association Flattening
HubSpot tickets can be associated with multiple contacts, but Intercom conversations support only a single contact, requiring primary requester selection and documentation of additional contacts as internal notes.
What breaks
Known failure modes. Have a recovery plan for each before you cut over.
Engagement types with no body
Some HubSpot call and meeting engagements have minimal metadata (duration and timestamp only). Importing these as Intercom parts creates sparse entries. Decide whether to import them for the metadata or discard them. Recommendation: discard if fewer than 5% of total engagements; import as notes if they contain recording URLs.
Multiple ticket-contact associations
HubSpot tickets can be associated with multiple contacts. Intercom conversations have one contact. Pick the primary requester (the contact who created the ticket, or the most recent email sender) and document others as internal note parts.
HubSpot Owner → Intercom Admin mapping
Map each HubSpot Owner ID to an Intercom Admin ID. Former owners who no longer exist as Intercom admins require a fallback (e.g., a generic "Migration" admin account). Create this admin before migration and use it as the default author for unmatched owners.
Long-thread QA
A single Intercom conversation GET returns at most 500 conversation parts. Long-thread validation cannot rely on one API read — paginate or verify from both sides. (developers.intercom.com)
HTML rendering drift
Imported bodies render differently between the create-conversation and reply/note endpoints. Normalize HTML before bulk load (strip unsupported tags like <style>, <script>, and HubSpot tracking pixels) and test on a sample first. (developers.intercom.com)
Inline images in email engagements
HubSpot email engagements often contain inline images as CID references. These won't render in Intercom unless converted to hosted image URLs during transformation.
Tools used in this playbook
All free, all run entirely in your browser — nothing is uploaded.
FAQ
How long does a HubSpot Service Hub to Intercom migration take?
Decoupled model with full history: 6–10 weeks. Full departure: 8–12 weeks. Clean-break: 4–7 weeks. The conversation history migration phase (5–15 days) is the longest and most variable.
Can I keep my full HubSpot ticket history in Intercom?
Yes, but only with an API-led migration. Intercom's Conversations API supports a created_at parameter for setting original timestamps on conversations, and reply/note endpoints also support it. Test this in week 1 to verify behavior on your plan.
What data is lost when migrating from HubSpot Service Hub to Intercom?
Cross-object Workflows, the unified CRM activity timeline, Playbooks, NPS/CES surveys (unless using Intercom's Surveys product), calculated/score properties (become static), Kanban pipeline views, deal associations on tickets, and HubSpot task objects.
Can I keep HubSpot CRM and just move service to Intercom?
Yes — this is the decoupled model and the most common approach. Install Intercom's HubSpot app to surface CRM context in the Inbox sidebar. The native app is one-way (Intercom to HubSpot) — bidirectional sync requires HubSpot Data Sync or middleware.
Why is HubSpot to Intercom migration harder than HubSpot to Zendesk?
Zendesk has a dedicated Ticket Import API with guaranteed timestamp preservation — Intercom does not. Intercom also has two interaction objects (Conversations and Tickets) requiring a routing decision that doesn't exist with Zendesk's single-object model.