HubSpot-to-Intercom migrations require remapping a relational CRM to a conversation-centric platform. Plan for 1:1 API calls on the Intercom side, data model redesign, and edge case handling.
Migrating from HubSpot to Intercom presents a fundamental architectural mismatch: HubSpot is a relational CRM where Contacts, Companies, Deals, and Tickets exist as associated objects within a deep object graph, while Intercom is a messenger-first communication platform where Conversations and Contacts are the primary entities. There is no native, point-and-click migration path between the two platforms, and attempting a direct field-level export/import will result in broken conversation threading, misaligned ticket statuses, and lost historical context. HubSpot constructs like Deals, multi-level Engagement objects, and relational Custom Objects have no direct Intercom equivalents and require substantial transformation logic — including object flattening, chronological sequencing of engagement records, and pre-creation of Intercom data structures — before any data can be imported. Custom development work is required to map HubSpot pipelines to Intercom Ticket Types, sequence Engagements into Conversation Parts, and handle entities like Deals that must be either discarded, flattened into Contact attributes, or mapped to Intercom Custom Objects.
Read this first
Pair-specific gotchas that catch teams out. Each one has cost somebody a weekend.
HubSpot Deals have no native home in Intercom
If your migration scope includes pipeline data, you must either map Deals to Intercom Custom Objects (limited), flatten them into Contact attributes, or accept that Intercom is not your CRM — it's your support layer.
Intercom Companies without at least one associated Contact may not be visible in the UI
Import Companies first, then Contacts, then create the associations.
For large migrations, request elevated rate limits from Intercom support before starting
Provide your estimated total API call volume and desired migration window. Intercom typically responds within 2–3 business days.
Intercom's migration guidance warns that message-by-message history replay can multiply
Intercom's migration guidance warns that message-by-message history replay can multiply API volume by 10–100x versus creating a single conversation per ticket. For teams with >50K tickets, the pragmatic compromise is one source ticket = one Intercom Conversation with a consolidated transcript body, rather than every message as a distinct Conversation Part. This trades per-message fidelity for completion speed and API budget. (intercom.com)
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
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 → 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 → Intercom specifics
- Messenger-first support
- Intercom's in-product Messenger with persistent conversation history replaces HubSpot's ticket-pipeline model for teams that want real-time, chat-driven customer engagement. HubSpot's live chat exists but is tethered to the CRM object model — conversations live as Engagements on Contact records rather than as first-class threaded objects.
- Fin AI Agent
- Intercom's LLM-powered AI agent resolves conversations autonomously. As of 2025, Intercom reports Fin resolving up to 50% of support volume for some customers. HubSpot's chatflows are rule-based and tree-structured — they cannot handle open-ended queries or synthesize answers from knowledge base content.
- Proactive messaging and Product Tours
- In-app lifecycle engagement features — targeted banners, tooltips, multi-step product tours — that HubSpot Service Hub doesn't natively offer.
- Simpler agent experience
- Teams moving away from HubSpot's CRM-heavy interface where agents navigate multiple object types, property panels, and association tables to resolve a single ticket.
- Consolidation
- Teams that used HubSpot primarily for support (not sales/marketing) and want a purpose-built support platform rather than paying for a full CRM suite.
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 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 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 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 → 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 → 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.
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.
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 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 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 read-only rather than cancelled — cancelling the old contract on day one removes your only fallback.
HubSpot → Intercom specifics
- Big Bang (recommended for most teams)
- Schedule over a weekend. Freeze HubSpot writes at COB Friday, run delta sync Saturday, validate Sunday, go live Monday. Downside: compressed timeline for troubleshooting.
- Phased (by team/department)
- Move one support team at a time. Requires complex routing rules to direct incoming conversations to the correct platform during the transition period. Only viable if teams have cleanly separated ticket queues.
- Parallel run (2–4 weeks)
- Run both platforms simultaneously with manual reconciliation. Expensive in agent time but lowest risk. Best for enterprises with >500K records or regulated industries.
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 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 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.
-
Rebuild automations
HubSpot Workflows do not migrate. Manually rebuild routing rules, SLAs, and auto-responders in Intercom's Workflow builder. Document each HubSpot workflow, identify its Intercom equivalent, and test before enabling. Confirm that migration-created items do not trigger customer-visible notifications.
-
Configure Fin AI
Point Intercom's Fin AI at your migrated Help Center articles for automated resolutions. Verify that article formatting survived migration — Fin's answer quality depends on clean, well-structured content. Test Fin with 20–30 representative customer questions and compare answers against expected responses.
-
Set up 301 redirects for KB URLs
If your HubSpot KB was publicly indexed, implement redirects from old URLs to new Intercom Help Center URLs. This preserves SEO value and prevents broken links in customer bookmarks, emails, and external documentation.
HubSpot → Intercom specifics
- Train your team
- Intercom's inbox is fundamentally different from HubSpot's ticket view. Key differences agents need to learn:
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.
Contacts Contacts
HubSpot Contacts map directly to Intercom Contacts with well-defined field equivalents, though lifecycle stage classification into User or Lead roles and pre-creation of custom attributes as Data Attributes in Intercom are required before import.
| HubSpot field | Intercom field | Notes |
|---|---|---|
| Primary identifier; required for CSV import | ||
| firstname + lastname | name | Intercom uses a single name field — concatenate |
| phone | phone | Direct map |
| lifecyclestage | role (user/lead) | Map Customer/Opportunity → User; Subscriber/Lead → Lead |
| hs_object_id | external_id | Store HubSpot ID for traceability and dedup |
| Custom properties | custom_attributes.* | Must pre-create as Data Attributes in Intercom |
Companies Companies
HubSpot Companies map to Intercom Companies with most native fields having direct equivalents, though the import order matters — Companies must be created before Contacts and associations established afterward, or Companies may not appear in the Intercom UI.
| HubSpot field | Intercom field | Notes |
|---|---|---|
| name | name | Direct map |
| domain | website | Direct map |
| industry | industry | Direct map |
| numberofemployees | size | Direct map (integer) |
| hs_object_id | company_id | Use as external identifier for dedup and re-runs |
| annualrevenue | monthly_spend | Requires transformation (÷ 12) |
| Custom properties | custom_attributes.* | Pre-create via Data Attributes API |
Tickets Conversations or Tickets
HubSpot Tickets require a pre-migration configuration step to create matching Ticket Types and Ticket States in Intercom, and each pipeline-to-type and stage-to-state mapping must be explicitly defined before any ticket records are transferred.
| HubSpot field | Intercom field | Notes |
|---|---|---|
| Pipeline | Ticket Type | One Ticket Type per HubSpot pipeline |
| Pipeline Stage | Ticket State | Map each stage to submitted/in_progress/waiting_on_customer/resolved |
| subject | Ticket title | Direct map |
| content / first engagement | Initial Conversation message | Oldest engagement becomes first message |
| hs_ticket_priority | Ticket priority attribute | Map High/Medium/Low |
| hubspot_owner_id | admin_id (assignee) | Requires an admin ID mapping table |
Knowledge Base Intercom Articles
HubSpot Knowledge Base articles can be mapped to Intercom Help Center Articles with matching collection and section structures, but unsupported HTML tags must be stripped, URL slugs change and require 301 redirects, and incomplete migration directly degrades Fin AI resolution quality.
| HubSpot field | Intercom field | Notes |
|---|---|---|
| Category | Collection | Create collections first, then assign articles |
| Subcategory | Section (within Collection) | Direct map |
| Article title | Article title | Direct map |
| Article body (HTML) | Article body (HTML) | Intercom supports a subset of HTML; strip unsupported tags |
| Article URL slug | Article URL | Different URL structure — set up 301 redirects |
| Multi-language versions | Translated articles | Intercom supports multi-language Help Centers |
Risk matrix
Per-object risk for this pair. Plan extra validation around anything marked high.
| Object | Risk | Notes |
|---|---|---|
| Contacts | low | HubSpot Contacts map directly to Intercom Contacts with well-defined field equivalents, though lifecycle stage classification into User or Lead roles and pre-creation of custom attributes as Data Attributes in Intercom are required before import. |
| Companies | low | HubSpot Companies map to Intercom Companies with most native fields having direct equivalents, though the import order matters — Companies must be created before Contacts and associations established afterward, or Companies may not appear in the Intercom UI. |
| Tickets | medium | HubSpot Tickets require a pre-migration configuration step to create matching Ticket Types and Ticket States in Intercom, and each pipeline-to-type and stage-to-state mapping must be explicitly defined before any ticket records are transferred. |
| Conversations (Engagements) | high | HubSpot Engagements — Emails, Notes, Calls, Meetings, and Tasks — must be chronologically sequenced and individually mapped to Intercom Conversation Parts or Contact Notes, making this the highest-error-rate step in the migration due to ordering logic, missing associations, and attachment handling failures. |
| Deals | high | HubSpot Deals have no native Intercom equivalent and require a deliberate pre-migration decision to either map to Intercom Custom Objects via API, flatten key fields into Contact attributes, or retain the data outside Intercom entirely, with no option preserving full pipeline and association fidelity. |
| Custom Fields (Data Attributes) | medium | Custom properties from HubSpot Contacts and Companies must be manually pre-created as Data Attributes in Intercom before any records are imported, and any attribute not created in advance will cause import failures or silent data loss. |
| Custom Objects | high | HubSpot Custom Objects with nested sub-objects, pipelines, or multi-level associations cannot be ported directly into Intercom's single-level Custom Object schema and require a full schema redesign, object flattening, and API-based population through Intercom's Data Connectors. |
| Knowledge Base Articles | medium | HubSpot Knowledge Base articles can be mapped to Intercom Help Center Articles with matching collection and section structures, but unsupported HTML tags must be stripped, URL slugs change and require 301 redirects, and incomplete migration directly degrades Fin AI resolution quality. |
| Agent and Owner Assignments | medium | HubSpot owner IDs referenced on Tickets and Engagements do not carry over to Intercom and require a pre-built mapping table that translates each HubSpot owner ID to the corresponding Intercom admin ID before ticket and conversation assignment data can be accurately transferred. |
| Tasks | high | HubSpot Tasks have no equivalent object in Intercom and must either be discarded or rebuilt manually in an external project management tool, meaning task-based workflow history cannot be preserved within the Intercom platform post-migration. |
The hard parts
What makes this specific migration difficult, beyond the mechanics.
Deal Object Has No Equivalent
HubSpot Deals have no native counterpart in Intercom and must be either mapped to Intercom Custom Objects via API, flattened into Contact-level attributes, or retained in HubSpot as a separate system of record, each option requiring deliberate architectural decisions before migration begins.
Engagement Threading Into Conversations
HubSpot stores activities — Emails, Notes, Calls, Tasks, and Meetings — as discrete Engagement objects that must be chronologically sorted and sequenced into Intercom Conversation Parts or Contact Notes, a multi-step transformation process with a high error rate due to ordering failures and missing associations.
Ticket Pipeline and Stage Remapping
HubSpot Ticket pipelines and stages do not map directly to Intercom's Ticket Types and Ticket States, requiring a pre-migration configuration step where Ticket Types are created in Intercom and each HubSpot stage is explicitly mapped to an Intercom state such as submitted, in_progress, waiting_on_customer, or resolved.
Custom Object Schema Incompatibility
HubSpot Custom Objects support full associations, pipelines, and nested sub-objects, whereas Intercom Custom Objects are API-populated, single-level structures with no support for nested objects or multi-level associations, requiring a complete schema redesign rather than a direct port.
Contact Role Classification Required
Intercom distinguishes between Users and Leads at the contact level, requiring each HubSpot Contact to be classified by its Lifecycle Stage before import — a transformation step that, if skipped, will result in incorrect role assignments and corrupted segmentation in Intercom.
Knowledge Base SEO Continuity Risk
HubSpot Knowledge Base articles use a different URL structure than Intercom's Help Center, meaning all article URLs change post-migration and 301 redirects must be explicitly mapped and implemented to prevent search ranking loss and broken Fin AI content references.
What breaks
Known failure modes. Have a recovery plan for each before you cut over.
The "Author" Problem
When migrating historical conversations, Intercom defaults to showing the API key owner as the author of all messages. You must explicitly set the admin_id in the API payload to ensure historical replies are attributed to the correct agents. This requires building a mapping table of HubSpot owner IDs to Intercom admin IDs before starting the load phase.
Inline Images
HubSpot often hosts inline images behind authenticated URLs or on its CDN (f.hubspotusercontent.com). If you migrate the HTML <img> tag as-is, the image will break in Intercom because the agent doesn't have the HubSpot session token, or because HubSpot may expire the URL. You must download and re-host every inline image — either to Intercom's upload endpoint or to your own CDN.
Orphaned Engagements
HubSpot allows engagements (notes, tasks) to exist without a parent ticket. Intercom requires all communication to belong to a Conversation or be a standalone Note on a User profile. Build routing logic: if an engagement has a ticket association, attach to the corresponding Conversation; if it only has a contact association, create as a Note on the Contact; if it has no associations, log to an exceptions table for manual review.
Contacts without email
Intercom CSV import requires email. API import can use external_id instead, but the contact won't be searchable by email in the UI and won't match on inbound emails. Decide whether these contacts are worth migrating.
Duplicate contacts
HubSpot allows multiple contacts with the same email in some edge cases (particularly after imports or integrations). Intercom enforces strict email uniqueness — you'll get 409s. Deduplicate in HubSpot or merge in your transform step before loading. (intercom.com)
Multi-level associations
HubSpot's Company → Contact → Deal → Line Item chains don't translate. Intercom has a flatter model — you'll need to flatten or discard layers. A common approach: store the Company and Contact relationship, flatten Deal data onto the Contact, discard Line Items.
Property history loss
HubSpot tracks property change history on records (e.g., every lifecycle stage transition with timestamp). Intercom does not store property history. You migrate current state only. If you need historical property data for analytics, export it to your data warehouse before migration.
Historical timestamps
Intercom's API accepts created_at when creating conversations, allowing you to preserve original creation dates. However, subsequent Conversation Parts (replies) may default to the API call timestamp depending on the endpoint and API version. Test with a small batch and verify timestamps before running at scale.
Attachment re-hosting
HubSpot engagement attachments must be downloaded and re-uploaded. Intercom conversation replies support attachment URLs, but files hosted on HubSpot's servers may become inaccessible after you decommission HubSpot. Download all attachments during the extract phase and re-host permanently. (developers.intercom.com)
Rich text and HTML formatting
HubSpot emails often contain complex HTML with inline CSS, tables, and custom fonts. Intercom's Conversation Parts support a limited HTML subset. Unsupported tags are stripped silently, which can break formatting. Run a transform step that converts complex HTML to Intercom-compatible markup.
Workflow triggers on migrated data
If Intercom workflows are active during migration, creating conversations via API can trigger auto-replies, assignments, SLA timers, and customer notifications. Disable or add API-source exceptions to all workflows before loading historical data.
Tools used in this playbook
All free, all run entirely in your browser — nothing is uploaded.
FAQ
Can I migrate HubSpot tickets to Intercom using a CSV?
No. Intercom's CSV import covers Users and Leads only — not Companies, Conversations, or Tickets. You must use the Intercom REST API to migrate historical support data, creating each record individually since there is no bulk import endpoint.
Can I migrate HubSpot Deals to Intercom?
Not 1:1. Intercom has no native Deal/Opportunity object. You can map operationally useful deal data to Intercom Custom Objects or Ticket attributes, flatten key data into Contact custom attributes, or keep Deals in HubSpot CRM and use Intercom only for support.
Does Intercom have a bulk import API?
No. Intercom does not offer a bulk create or update endpoint for Contacts, Companies, or Tickets. Every record requires a separate API call. For large migrations, request elevated rate limits from Intercom support before starting.
How long does a HubSpot to Intercom migration take?
A small migration (<10K contacts, no custom objects) can be completed in 1–3 days. Enterprise migrations with 100K+ records, custom objects, and relationship rebuilding typically take 2–4 weeks including validation and testing.
Will I lose HubSpot property change history when migrating to Intercom?
Yes. HubSpot tracks property change history on records. Intercom does not have an equivalent feature. You migrate the current state of each record only. If you need historical data, export and archive it separately before migration.