Skip to content
DataGrine home

Intercom migration

Migrate to Intercom, history and all.

Companies, contacts, tickets, conversations, attachments and help centre articles, moved into Intercom from any helpdesk. Run it self-serve or let our migration team do it end to end, with 24/7 support.

What moves

Your history, with its relationships intact.

Every field is mapped in writing before anything moves, and a sample of your own records lands in Intercom first so you can check it there.

  • Companies, with their contacts and conversations still attached
  • Contacts, matched on email or external ID so nobody is duplicated
  • Tickets as Intercom tickets or as conversations, your choice
  • Every reply and internal note in order, with its author and attachments
  • Custom fields mapped to ticket, conversation, contact or company attributes
  • Help centre articles into Intercom collections

Routes into Intercom

Where you are moving from.

Zendesk→Intercom

Teams move for Fin and the Messenger, then discover four years of ticket history has to come with them.

See this route
Freshdesk→Intercom

Teams moving from Freshdesk often need more flexible routing, workflows and AI-powered support.

See this route
Help Scout→Intercom

Teams moving from Help Scout often need more advanced routing, SLAs and AI-powered support.

See this route
Gorgias→Intercom

Ecommerce teams moving from Gorgias often need support to cover more than order status, with Fin AI Agent on the front line.

See this route
Front→Intercom

Teams that grew up in a shared inbox move to Intercom when they need routing, SLAs and an AI agent in front of the queue rather than more people behind it.

See this route
Kustomer→Intercom

Teams leave Kustomer for Intercom when Fin AI Agent and the Messenger matter more than a CRM-style customer timeline.

See this route
Zoho Desk→Intercom

Teams on Zoho Desk move to Intercom for the Messenger, conversational support and Fin AI Agent, usually as the product side of the business outgrows a ticket queue.

See this route
Freshchat→Intercom

Teams move from Freshchat to Intercom to put chat, email and tickets in one Inbox with Fin AI Agent answering first.

See this route
Drift→Intercom

Clari + Salesloft is gradually sunsetting Drift, so teams move their chat history to Intercom, where the Messenger and Fin AI Agent take over website conversations.

See this route
HubSpot→Intercom

Teams keep HubSpot as the CRM but move support to Intercom for Fin AI Agent, the Messenger and a dedicated support Inbox.

See this route
Salesforce Service Cloud→Intercom

Support teams move from Salesforce Service Cloud to Intercom for a faster agent experience and Fin AI Agent, often keeping Salesforce as the system of record for accounts.

See this route

Questions

Migrating to Intercom, answered.

Which helpdesks can you migrate to Intercom from?

Any helpdesk with an API or an export: Zendesk, Freshdesk, Help Scout, Front, Gorgias, Kustomer, Zoho Desk, Freshchat, HubSpot, Salesforce Service Cloud, and in-house or legacy tools.

Tickets or conversations?

Intercom has both. Each migrated record can land as a ticket of the type you choose or as a plain conversation. You decide in the mapping, before anything moves.

Will our team have to stop working during the migration?

No. The full run happens while your team keeps working in the old helpdesk, and a delta sync at cut-over carries what was created or changed since.

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.

Let’s move your data forward.

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