Zendesk to Intercom migration
DataGrine migrates Zendesk 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 Zendesk into Intercom.
- UsersContacts
- OrganizationsCompanies
- TicketsTickets or conversations
- Public commentsConversation replies
- Private commentsInternal notes
- AttachmentsPart attachments
- Inline imagesConversation part attachments
- Custom ticket fieldsConversation or ticket attributes
- TagsTags
- Ticket statusesTicket states
- Guide articlesHelp Center articles
Why teams make this move
Teams move for Fin and the Messenger, then discover four years of ticket history has to come with them.
Worth planning for
Zendesk tickets are threaded comments with public/private flags; Intercom conversations are parts with a different author model. Getting internal notes to stay internal is where most migrations leak.
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
Zendesk to Intercom, answered.
What does not carry across from Zendesk?
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 Zendesk, 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?
Yes. Intercom's built-in Zendesk importer (Settings > Data > Imports & exports) is for fewer than 150,000 tickets and brings users, organizations, tickets with comments and notes, attachments and inline images (up to 10 of each per ticket), custom field data and assignment; it does not bring tags, side conversations or call recordings, imports everything in one go with no later sync, and needs teams, teammates and ticket types to exist first. Public Guide articles have a separate Zendesk article import. 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 Zendesk?
Zendesk Support API: 200 requests a minute on Team, 400 on Professional, 700 on Enterprise and 2,500 on Enterprise Plus or with the High Volume add-on; incremental export endpoints are limited to 10 requests a minute (30 with High Volume). 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?
Private comments must be written as Intercom notes, never replies, and this needs checking on a sample before the full run. Multiselect and lookup fields have no direct Intercom type and must be flattened to text, which changes how they can be reported on. Teammates, teams and ticket types must exist in Intercom before any history moves, and leavers need a fallback owner.
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: Intercom tickets vs conversations: what should migrated history become? · How to export tickets from Zendesk, with comments and attachments · Migrating into Intercom without duplicate contacts
Other routes
Moving a different pair?
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.
Ecommerce teams moving from Gorgias often need support to cover more than order status, with Fin AI Agent on the front line.
Plan your Zendesk 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