
Intercom Alternatives After the Salesforce Deal: 6 Options Compared
11 min read
IntercomZendesk
Migration specialists move your conversations, messages and internal notes into Zendesk, check a sample with you first, and count every record on both sides.
Free sample migration of 100 of your records, plus a fixed quote within 24 hours.
Last updated November 2026 · 14 object types mapped
An Intercom to Zendesk migration turns conversations into tickets, contacts into end users and companies into organizations. The hard part is the read, because Intercom has no bulk export of message text. Intercom stays live until the final delta sync.
What moves
Conversations become tickets, contacts end users, companies organizations and teammates agents, with customer and teammate messages as public comments, internal notes as private comments and Help Center articles as Zendesk articles.
| Intercom | maps to | Zendesk | Status |
|---|---|---|---|
| Contacts (role user) | End usersMatched on email, with the Intercom contact id kept in a user field. | Included | |
| Contacts (role lead) | End usersZendesk has no lead role, so the lead flag is kept in a user field. Leads without an email follow the rule agreed at mapping. | Included | |
| Companies | OrganizationsThe Intercom company_id is stored in an organization field. | Included | |
| Conversations | TicketsOne ticket per conversation, with the subject taken from the conversation title or its first message. The conversation id goes to external_id. | Included | |
| Messages | Public commentsAuthor, original time and body are kept. | Included | |
| Internal notes | Private commentsNotes between teammates stay internal. | Included | |
| Assignments, state changes and bot steps | Text line in a private commentOn request. Otherwise they are left out of the ticket. | Included | |
| Tickets (Customer category) | TicketsThe ticket type becomes a ticket form or a tag, and ticket attributes become ticket fields. | Included | |
| Ticket states | Ticket statusesSubmitted and in progress become open, waiting on customer becomes pending, on hold becomes hold, and resolved becomes solved. | Included | |
| Tags | TagsApplied to the ticket, and to the end user where the Intercom tag sat on the contact. | Included | |
| Data attributes | User, organization and ticket fieldsContact and company attributes become user and organization fields. Conversation and ticket attributes become ticket fields. All fields are created first. | Included | |
| Admins and teams | Agents and groupsAdmins are matched to agents by email. | Included | |
| Articles | Help Center articlesYou choose the author, permission group and user segment before they load. | Included | |
| Collections and sections | Help Center categories and sectionsThe folder tree is rebuilt before any article is loaded. | Included |
Matched on email, with the Intercom contact id kept in a user field.
Zendesk has no lead role, so the lead flag is kept in a user field. Leads without an email follow the rule agreed at mapping.
The Intercom company_id is stored in an organization field.
One ticket per conversation, with the subject taken from the conversation title or its first message. The conversation id goes to external_id.
Author, original time and body are kept.
Notes between teammates stay internal.
On request. Otherwise they are left out of the ticket.
The ticket type becomes a ticket form or a tag, and ticket attributes become ticket fields.
Submitted and in progress become open, waiting on customer becomes pending, on hold becomes hold, and resolved becomes solved.
Applied to the ticket, and to the end user where the Intercom tag sat on the contact.
Contact and company attributes become user and organization fields. Conversation and ticket attributes become ticket fields. All fields are created first.
Admins are matched to agents by email.
You choose the author, permission group and user segment before they load.
The folder tree is rebuilt before any article is loaded.
Looking for another object?Field-level mapping is reviewed with you during scoping.
What does not move
Workflows, Series, bots, macros and Inbox views are configuration with no import path into Zendesk, so each is documented and rebuilt as triggers, automations and macros.
Free sample migration of 100 of your records. Fixed quote within 24 hours.
Scope my migrationTimeline
Estimated total
About 10 business days
end to end
Day 1-2
Scoping call
We agree how bot-authored parts are kept, what happens to contacts without an email, which collections and ticket types move, and the date range of history.
Connect both workspaces
You give us an Intercom access token with read access and a Zendesk admin connection, because the Ticket Import API is open to admins only.
Field and status review
Data attributes to user, organization and ticket fields, Intercom ticket states to Zendesk statuses, and teams to groups. You approve the mapping we send.
Day 3-7
Free sample
100 of your records, picked for the longest threads, the most bot-authored parts and the largest files, loaded into Zendesk end to end.
You review the sample
Your team opens the tickets as an agent and checks comment order, private notes, authors, dates and attachments.
Full load
Organizations and end users first, then tickets with their comments in bulk calls, then Help Center articles, paced to your Zendesk plan.
Delta sync
Conversations that changed in Intercom since the full load are brought across, matched on the conversation id in external_id, so nothing is created twice.
Day 8-10
Reconciliation report
Conversations against tickets by state and year, parts against comments, files against attachments, and every part handled by the bot rule.
Spot checks and sign-off
Your leads check a random sample, and Intercom stays active and read-only until you agree.
An estimate. Record volume, API rate limits and how fast your team reviews the sample all move it.
Known risks
The problem
Intercom releases message text one conversation at a time, with extra paged requests for threads over 500 parts. The Zendesk load runs under its own, separate plan limit.
How we handle it
We list every conversation id first, read threads in parallel within your workspace's rate limit, and bulk-load each completed batch. The free sample times both sides on your data.
Source: Intercom Help Center, checked 15 Nov 2026
The problem
An Intercom thread mixes customer messages, teammate replies, notes, assignments, state changes and messages written by the Fin AI Agent or a bot. Zendesk comments are only public or private.
How we handle it
At mapping we agree one rule for bot-authored parts: a public comment from an Intercom Bot user, a private comment, or left out. Assignments and state changes can be kept as a text line in a private comment.
Source: Intercom developer documentation, checked 15 Nov 2026
The problem
Zendesk assigns every ticket its own id, which cannot be chosen. Without a link back, nobody can find the old Intercom thread from the new ticket.
How we handle it
The Intercom conversation id is written to the Zendesk ticket's external_id, so a search on the old id finds the new ticket.
Source: Zendesk developer documentation, checked 15 Nov 2026
The problem
Intercom keeps leads and anonymous visitors beside signed-up users. Zendesk has no lead role, and an Intercom contact without an email cannot be matched to a Zendesk end user.
How we handle it
Contacts with an email become end users, with the lead flag in a user field. For contacts without one, you choose at mapping between a placeholder identity and leaving the conversation out.
Source: Intercom developer documentation, checked 15 Nov 2026
The problem
Zendesk runs no triggers on an imported ticket that is not closed, until that ticket is next updated, so an open Intercom conversation would land unassigned and outside your SLA policies.
How we handle it
For each open Intercom conversation, the group, assignee and priority are agreed at mapping and set on the Zendesk ticket itself.
Source: Zendesk developer documentation, checked 15 Nov 2026
The problem
Zendesk creates up to 100 users in one call, but bulk user imports are not enabled by default and return a 403 error until Zendesk Customer Support turns them on for the account.
How we handle it
We check it on the scoping call. If it is off, your admin asks Zendesk Customer Support to enable it before the sample, and users are created without a verification email.
Source: Zendesk developer documentation, checked 15 Nov 2026
The problem
Zendesk sets created_at and updated_at on Help Center articles itself. An article's author can be set, but the permission group and user segment must exist before the article loads.
How we handle it
We create the permission groups and segments you choose first, map each Intercom collection to a category or section, and list the original article dates in the reconciliation report. Subscribers are not emailed about the new articles.
Source: Zendesk developer documentation, checked 15 Nov 2026
Technical profile
Intercom hands over message text only one conversation at a time, and Zendesk's Ticket Import API sets original dates but runs no triggers and keeps no metrics or SLAs on what it loads.
Source: Intercom Help Center, checked 15 Nov 2026
Source: Intercom developer documentation, checked 15 Nov 2026
Source: Intercom Help Center, checked 15 Nov 2026
Source: Zendesk developer documentation, checked 15 Nov 2026
Source: Zendesk developer documentation, checked 15 Nov 2026
Source: Zendesk developer documentation, checked 15 Nov 2026
Source: Zendesk developer documentation, checked 13 Nov 2026
Source: Zendesk developer documentation, checked 15 Nov 2026
Facts checked 15 Nov 2026 against Intercom and Zendesk documentation. Each fact links its source.
Still unsure? Ask the engineer who would run this migration, not a sales rep.
Yes. Zendesk's Ticket Import API sets created_at, updated_at and solved_at on each ticket and created_at on each comment. Zendesk keeps no metrics or SLAs on imported tickets, so Intercom reply-time figures do not carry over.
They follow one rule you choose at mapping: a public comment from an Intercom Bot user, a private comment, or left out, because Zendesk comments are only public or private.
Users and leads with an email become Zendesk end users matched on that email, with the lead flag in a user field you can filter on. Contacts without an email get a placeholder identity or are left out, as you choose at mapping.
Yes. Each Intercom internal note becomes a private comment on the Zendesk ticket, with its author and original time, so the requester never sees it.
Yes. Intercom collections and sections become Zendesk Help Center categories and sections. Zendesk sets article dates itself, so the originals are listed in the reconciliation report, and each article needs an author, permission group and user segment chosen first.
No. Zendesk sends no CC notifications on imported tickets and runs no triggers on imported tickets that are not closed. Notifications resume only when a ticket is next updated.
About 10 business days end to end. The read is paced by one Intercom request per conversation, plus extra requests past 500 parts, and the load by your Zendesk plan limits and 100 tickets per bulk import call. The free sample shows the real pace.
The price is set by what moves: conversations and their parts, tickets, contacts, companies, attachments and Help Center size. You get a fixed quote within 24 hours of the scoping call, after a free sample migration of 100 of your records.
How it compares
The same data, moved four different ways. This is what changes between them.
MigrateX
Every object in the mapping on this page, plus the ones you ask for during scoping.
Automated migration software
Tickets and contacts are covered. Linked records, files and knowledge often are not.
Vendor CSV import
One object per file, and only the fields the export template exposes.
In-house scripts
Whatever you have time to build before the cutover date.
MigrateX
Each entry is posted separately, private stays private, public stays public.
Automated migration software
Threads usually arrive, but per-entry author and visibility can be flattened.
Vendor CSV import
Notes collapse into one field on the ticket, if they come across at all.
In-house scripts
Possible, but it is the part teams most often run out of time for.
MigrateX
Uploaded against the right note, and re-hosted with a link when they exceed the Zendesk cap.
Automated migration software
Supported up to the destination cap. Oversize files are skipped.
Vendor CSV import
Not carried by a CSV import.
In-house scripts
Needs its own download, retry and upload pipeline.
MigrateX
Every source id is stored on the destination record and handed back as a map.
Automated migration software
Often kept as a tag or a single text field.
Vendor CSV import
Lost once the file is imported.
In-house scripts
Only if you design the mapping table up front.
MigrateX
Included. Anything created or changed during the bulk pass is synced at cutover.
Automated migration software
Usually a paid upgrade on the top tier.
Vendor CSV import
You would re-export and re-import by hand.
In-house scripts
Requires change tracking and idempotent writes on both sides.
MigrateX
Paced to your plan limits, honours Retry-After, and resumes from a checkpoint.
Automated migration software
Backs off, but a long run can still stall and leave partial records.
Vendor CSV import
Not applicable, and the file size limits bite instead.
In-house scripts
The most common reason a home-grown run dies overnight.
MigrateX
Counts per object and per status on both sides, with every default and placeholder listed.
Automated migration software
A run log and an error list, rather than a reconciliation.
Vendor CSV import
Row counts in a spreadsheet.
In-house scripts
You write the reconciliation queries yourself.
MigrateX
Every write is tagged, so a batch can be reversed without touching your own records.
Automated migration software
Some approaches can clear a migration, some cannot.
Vendor CSV import
Manual cleanup of everything the import created.
In-house scripts
Only if you built the tagging in from the start.
MigrateX
A MigrateX engineer runs it and stays on the cutover call.
Automated migration software
You run the software. Support answers tickets.
Vendor CSV import
Your admins, one file at a time.
In-house scripts
Your engineers, instead of your roadmap.
Guides
Related routes
Independently audited controls over how we handle your data.
Data processing agreement available.
Business associate agreement available.

Free sample migration of 100 of your records, plus a fixed quote within 24 hours.