HubSpot to Intercom migration
DataGrine migrates HubSpot to Intercom: companies, contacts, tickets with their replies, notes and attachments, tags and knowledge base articles. Every field is mapped in writing and a sample of your own records is signed off before the full run. Run it yourself on the DataGrine platform or have the DataGrine team run it end to end, with 24/7 premium support either way.
What moves
From HubSpot into Intercom.
- ContactsContacts
- CompaniesCompanies
- TicketsTickets or conversations
- Thread messagesConversation replies
- Thread comments and ticket notesInternal notes
- AttachmentsPart attachments
- Ticket propertiesTicket or conversation attributes
- Pipelines and stagesTicket types and states
Why teams make this move
Teams keep HubSpot as the CRM but move support to Intercom for Fin AI Agent, the Messenger and a dedicated support Inbox.
Worth planning for
In HubSpot, tickets and the conversations inbox are separate objects tied together by associations to contacts, companies and deals. Each ticket has to be rebuilt as one Intercom conversation from the threads associated with it, without losing the link to the company that owns it.
Decided with you in the written mapping, before anything moves.
How it runs
Self-serve or fully managed. Same steps, same checks.
- 01
Connect and map
Read-only access to your old helpdesk. Every field and value mapped before anything moves.
- 02
Sample run
A sample of your own records lands in the new helpdesk for you to check and sign off.
- 03
Full migration
The full move at the fastest pace both platforms allow, while your team keeps working.
- 04
Delta at cut-over
Anything created or changed since the full run, moved on go-live day.
- 05
Reconcile
Counts checked object by object against the source, and every run can be rolled back.
- Read-only access to the source
- Rollback per run
- 24/7 premium support
Questions
HubSpot to Intercom, answered.
What does not carry across from HubSpot?
Configuration such as automations, macros and views is not data, so it is set up again in Intercom. Anything with no equivalent in Intercom is listed in the written mapping, and you choose what happens to it before anything moves.
Can we run it ourselves?
Yes. Run it self-serve on the DataGrine platform, or let our migration team handle it end to end. Either way you get 24/7 premium support until the migration is signed off.
Does our team have to stop working?
No. We only read from HubSpot, so your team keeps working during the full run, and a delta sync at cut-over moves anything created or changed since.
Can we use the built-in importer instead?
None. Intercom's HubSpot app is a one-way sync from Intercom to HubSpot (leads, company name and conversation transcripts as activities) and cannot pull HubSpot data, including tickets, into Intercom. A migration adds a written mapping, a sample run on your own data, a delta sync at cut-over and rollback.
How fast can data come out of HubSpot?
HubSpot privately distributed apps: 100 requests per 10 seconds and 250,000 a day on Free and Starter, 190 per 10 seconds and 625,000 a day on Professional, 190 per 10 seconds and 1,000,000 a day on Enterprise; an API limit increase raises the burst to 250 and adds 1,000,000 a day. The daily limit is shared by all apps on the account. Runs are paced to stay inside that limit, which is why large accounts move in a full run first and a delta at cut-over.
What needs deciding before the move?
Tickets and inbox threads are separate objects linked by associations, so each ticket's conversation has to be assembled before it can move. Internal notes live in two places since HubSpot's September 2026 Help Desk change, and missing either set loses internal history. Pipelines and stages need an agreed Intercom ticket type and state model before the run.
What does it cost?
It depends on how many records move and whether you run the migration yourself or have the DataGrine team run it. You get a quote once the records in scope are counted, before anything moves.
Further reading: What is a helpdesk migration? What moves, what does not, and how it runs
Other routes
Moving a different pair?
Teams move for Fin and the Messenger, then discover four years of ticket history has to come with them.
Teams moving from Freshdesk often need more flexible routing, workflows and AI-powered support.
Teams moving from Help Scout often need more advanced routing, SLAs and AI-powered support.
Plan your HubSpot to Intercom move.
Tell us where you are moving from and to. Run it yourself on the DataGrine platform or let our migration team handle it end to end, with 24/7 support either way.
- A written mapping document before anything moves
- A sample migration you review before the live run
- Delta sync at cut-over and rollback per run
- 24/7 premium support until you sign off