Intercom to HubSpot
Customer service platform with inbox, tickets, Help Center, workflows and the Fin AI agent.
Intercom data can move into HubSpot, landing mainly in Service Hub. 3 of 8 mapped objects move directly (Users and Leads (contacts), Companies and Tickets); 4 items need manual work and 2 do not move. Plan roughly 2-3 weeks for a small move and 8-14 weeks for a large one.
Migration checklist for Intercom
Three phases, specific to this system. Tick steps off as you go.
Before
0 of 5 doneDuring
0 of 5 doneAfter
0 of 5 doneWhat will it take?
No price list: cost follows volume, custom objects and how much logic must be rebuilt. Answer four quick questions for a planning range.
The three scenarios
Small migration
under 5k contacts, under 10k conversations
Mostly contacts and basic tickets.
Mid migration
5k-50k contacts, 10k-100k conversations
Attachments and automation rebuild.
Large migration
over 50k contacts, over 100k conversations
Multiple workspaces, long threads and custom reporting.
What moves the number
Timeline ranges are planning estimates, not a quote. A partner confirms scope after discovery.
Access, mapping and limits
Start with how data leaves Intercom: what you need to get in, what lands in HubSpot, and what will not.
REST over HTTPS, JSON, with a pinned Intercom-Version header and cursor pagination
Access token generated in Settings > Developers, or an OAuth app.
Default 10,000 calls/min per app and 25,000/min per workspace, enforced in 10-second windows. Data Export API: 90-day window and 1 concurrent job.
Choose your route
How will you move the data?
No native connector was found.
- You need: Access token generated in Settings > Developers, or an OAuth app.
- Permission: To confirm
Native imports often bring over only some data, so check coverage per object in the mapping below.
Export each object, clean it, then import it into HubSpot.
- Conversations API (list, then fetch each conversation for its parts)
- Data Export API for message content stats (90-day window)
- CSV export of saved Views (metadata only)
- Reports dataset export (metadata)
- S3/GCS cloud storage export (JSON, no transcripts)
- Inbox bulk export (about 200-300 conversations per operation)
- Single conversation export as text/PDF
Limits: Default 10,000 calls/min per app and 25,000/min per workspace, enforced in 10-second windows. Data Export API: 90-day window and 1 concurrent job.
Migration and sync tools can move more than a plain import. Confirm which objects each one supports before you choose.
Best when volume is high, custom objects are many or automation is heavy. That is the Large scenario: 8-14 weeks, usually phased.
Talk to a partnerWhere each object lands
In Intercom
In HubSpot
Hover or tap anything on the left to see where it lands.
| Source object | In HubSpot | Moves | Notes |
|---|---|---|---|
| Users and Leads (contacts) | Contacts | yes | Dedupe on email. Users vs Leads map to lifecycle stage. Contacts without email become orphans. |
| Companies | Companies | yes | Match on company_id or domain. Use the API for multi-company links, because the CSV export keeps only the latest company. |
| Conversations | Tickets | partial | One ticket per conversation, with parts as Notes/Emails. Pipeline and stage must be set. The API returns only the latest 500 parts. |
| Tickets | Tickets | yes | Subject, status, priority, assignee, tags, comments and timestamps are mapped by a migration tool. |
| Admins/teammates | Users | partial | Mapped to HubSpot users for ticket ownership. Teams and roles may need manual setup. |
| Custom data attributes | Contacts | partial | Custom fields are mapped to properties. Create the properties first. |
| Attachments and inline images | Files | partial | Migration vendors attach inline images and call recordings to tickets. Verify the export path. |
| Help Center articles | Custom objects | manual | Articles are readable via the API. The HubSpot knowledge base target and import path are unconfirmed. |
What to expect
The REST API gives no pagination for parts inside one conversation.
These exports contain metadata only, so transcripts need the REST API.
Automation logic does not export as HubSpot workflows.
SLA semantics differ, so SLA targets must be recreated in HubSpot.
These are rebuilt by hand.
Orphaned records need skip, placeholder or merge rules.
Find long threads early and archive their full export separately.
Back off using the Retry-After header and de-duplicate on id.
Pilot a sample of conversations with images before the full run.
Run a delta pass after cutover.
Data governance and compliance
Decide what is allowed to move before anything is exported. Tick each gate once it is agreed.
How we researched this page
How much to trust each section, and where it comes from.
API, rate limits and export paths are backed by secondary guides, and Intercom's own docs appeared only for rate limits. No HubSpot doc on this migration was found. Object mapping rests on migration-vendor guides. Help Center articles, SLAs and attachments are not confirmed.
Sources
Related migrations
Frequently asked questions
How do I migrate Intercom to HubSpot?
1. Generate an Intercom access token and note the workspace region (US, EU or AU base URL). 2. Count contacts, companies, conversations, tickets and Help Center articles. 3. Audit custom data attributes and create matching HubSpot properties. 4. Decide pipelines and stages for tickets, and the handling of contacts without email.
What data can move from Intercom to HubSpot?
These objects move directly: Users and Leads (contacts), Companies and Tickets. Check the mapping table for partial and manual items.
What does not move from Intercom to HubSpot?
Conversation parts beyond the 500 returned by the API and Transcripts via CSV or S3 export. Plan to rebuild or retire these.
How long does a Intercom to HubSpot migration take?
Small (under 5k contacts, under 10k conversations): 2-3 weeks. Mid (5k-50k contacts, 10k-100k conversations): 3-8 weeks. Large (over 50k contacts, over 100k conversations): 8-14 weeks. These are planning estimates, not a quote.
What access do I need to export from Intercom?
Access token generated in Settings > Developers, or an OAuth app.
What compliance issues apply when moving Intercom data?
Check: Support chats may contain health, financial or minors' data. Agree consent, retention and access rules before exporting.
Moving Intercom into HubSpot?
A network of 153+ tiered HubSpot partners and 1,800+ accounts of experience. Tell us what you are moving and which hub matters most.
Talk to a partner