Zendesk to Intercom migration
We migrate Tickets, Users, Organizations, and Help Center articles from Zendesk into Intercom's conversation-centric model, resolving the Tickets-to-Conversations structural shift, preserving SLA and tag metadata, and flagging every Zendesk automation that requires manual rebuild in Intercom's Rules engine before cutover.
FlitStack AI migrates conversations, contacts, companies, admin or teammates and configurations from Zendesk to Intercom, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 3-5 weeks.

What moves from Zendesk to Intercom?
Moving from Zendesk to Intercom is a paradigm shift, not a record copy.
Read the full summary
Zendesk treats every customer interaction as a discrete Ticket with structured status transitions, SLA policies, and a separate Help Center. Intercom treats interactions as ongoing Conversations within a unified Inbox, with Articles embedded in the Messenger and no native SLA management. We map Tickets to Conversations, Zendesk Users to Intercom Contacts, Organizations to Companies, and Help Center sections to Intercom Articles. We flag SLA Policy data that has no destination (Intercom lacks native SLA enforcement) and store it as a custom attribute on the Conversation for agent reference. We do not migrate Triggers, Automations, Macros, Views, or SLA Policies as code; these require manual reconstruction in Intercom's Rules and Operator Inbox configuration. The migration scope covers operational data only — tickets, contacts, companies, attachments, tags, and knowledge base content.
Ticket → Conversation
Zendesk Tickets map to Intercom Conversations.
How it maps
The Zendesk Ticket ID is preserved in a custom Intercom conversation attribute for cross-reference. Ticket status (New, Open, Pending, Solved, Closed) maps to Intercom's open/closed state, with Zendesk Pending mapped to Snoozed. The assignee, requester, group, priority, and tags transfer as conversation attributes. Internal notes on Zendesk tickets become part of the conversation body and are marked as note-type messages in Intercom. Comments from agents and requesters populate as standard conversation messages in chronological order. Status transitions in Zendesk that have no Intercom equivalent are logged as conversation state changes in the attribute history.
User (End-User / Requester) → Contact
Zendesk end-users (requesters) map to Intercom Contacts.
How it maps
We import name, email, phone, custom user fields, organization membership, and creation timestamp. The Zendesk user ID is preserved as a custom attribute for cross-referencing. Role assignment (agent vs. end-user) is handled via Intercom's Contact vs. Admin split: agents become Intercom Admins or Teammates; end-users become Contacts. The requester's organization membership in Zendesk maps to a Company membership in Intercom.
Organization → Company
Zendesk Organizations map to Intercom Companies.
How it maps
Domain names, details fields, and user memberships transfer. The Zendesk organization ID is preserved as a custom attribute on the Intercom Company. Cross-reference between Zendesk users and their organization memberships maps to Intercom's Contact-Company relationship. Organizations with no members still migrate as Company records with a note flagging the orphan for the customer's admin to reconcile.
Agent → Admin or Teammate
Zendesk agents map to Intercom Admins and Teammates.
How it maps
Zendesk role names (admin, agent, light agent, contributor) are preserved in a custom attribute and mapped to the closest Intercom role: Zendesk admins become Intercom Admins; Zendesk agents become Intercom Teammates. Group memberships in Zendesk map to Intercom Teams. We resolve agents by email match against the Intercom destination workspace; any Zendesk agent without a matching Intercom user goes to a reconciliation queue for the customer's admin to provision.
Brand → Configuration (no direct equivalent)
Zendesk Brands have no direct Intercom equivalent.
How it maps
Multi-brand Zendesk accounts require a pre-migration decision: either consolidate all brands into a single Intercom workspace (with brand identity preserved in conversation tags and attributes) or provision separate Intercom workspaces per brand. We document the brand structure during discovery and deliver a written brand mapping plan. Customers who need strict brand isolation in Intercom must configure separate Inboxes per brand and use routing rules; we provide the routing rule specification as part of the handoff documentation.
SLA Policy → Custom Conversation Attribute (no native equivalent)
Intercom has no native SLA enforcement.
How it maps
Zendesk SLA Policies (first-response and resolution targets) cannot be recreated as a native feature. We migrate SLA Policy definitions as custom conversation attributes on each Conversation (e.g., sla_policy_name, first_response_target, resolution_target, plan_tier) and store a written SLA inventory document. The customer's admin or an Intercom integration partner can rebuild SLA tracking using third-party SLA tools (e.g., SLAzen, CAIWA) or a custom webhook-based solution. We do not implement SLA tracking software as part of the migration scope.
- TicketConversation1:1
- UserContact1:1
- OrganizationCompany1:1
- AgentAdmin or Teammatetransformed
- BrandConfigurationtransformed
- SLA PolicyCustom Conversation Attributetransformed
+ 6 more in the mapping below
How Zendesk and Intercom differ
The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.
| Dimension | Zendesk | Intercom |
|---|---|---|
| Core data model | Ticket-centric: discrete cases with formal status transitions (New, Open, Pending, Solved, Closed) | Conversation-centric: ongoing dialogues within a unified Inbox, with open/closed resolution state only |
| SLA policies | Native SLA enforcement with first-response and resolution targets on Professional and Enterprise | No native SLA enforcement; SLA metadata must be stored as custom conversation attributes by agents |
| Multi-brand routing | Multi-brand with up to 5 brands on Growth/Professional and 300 on Enterprise, each with separate email addresses and routing | Single workspace model; brand routing requires separate Intercom accounts or manual inbox rules |
| Custom objects | Custom Objects v2 on Enterprise and Enterprise Plus with user-defined schemas and lookup relationships | No custom object model; custom data must flatten into Contact or Conversation custom attributes |
| Pricing model | Per-agent per-month ($19-$169/agent/mo) with add-ons for Advanced AI ($50), QA ($35), WFM ($25) | Per-seat plus usage: Essential $29/seat, Advanced $85/seat, Expert $132/seat, plus Fin AI at $0.99/resolution |
| Automation engine | Triggers (event-driven) and Automations (time-based hourly) with 500-rule cap and 65KB per rule limit | Rules engine for conversation events, assignment, and routing; no time-based batch automation equivalent |
| Knowledge base | Separate Help Center with Sections, Categories, and Articles; no native full export | Articles built natively into the Messenger with help center and resolution bot integration |
What to watch for in a Zendesk to Intercom migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
Intercom has no native SLA enforcement
Zendesk's SLA Policies (first-response and resolution targets) cannot migrate as a native feature because Intercom has no SLA object or enforcement engine.
How we handle it
Teams relying on Zendesk's SLA compliance tracking will lose that functionality on day one in Intercom unless they implement a third-party SLA tracking tool or a custom webhook solution. We migrate SLA Policy definitions as custom attributes on Conversations and deliver a written SLA inventory so the customer's admin can evaluate replacement tools. This gap is a frequent post-migration surprise for teams that selected Intercom without realizing the SLA feature loss.
Ticket status model incompatibility causes data shape changes
Zendesk's ticket lifecycle uses five named statuses (New, Open, Pending, Solved, Closed) with optional custom statuses on Enterprise.
How we handle it
Intercom uses a binary open/closed state with Snooze as the only intermediate state. A Zendesk ticket that was Pending with a specific reason code (e.g., 'Waiting on customer') loses that granular status in Intercom unless stored as a custom conversation attribute. We preserve the original Zendesk status in a custom attribute, but agents must manually interpret it because Intercom's inbox does not surface pending-reason metadata natively.
Multi-brand Zendesk accounts require workspace strategy
Zendesk Brands (up to 5 on Growth/Professional, up to 300 on Enterprise) enable multi-tenant routing with separate email addresses, help centers, and inbox assignments per brand.
How we handle it
Intercom has no native multi-brand concept within a single workspace. Multi-brand Zendesk customers must either consolidate into a single Intercom workspace (with brand identity preserved in tags) or purchase multiple Intercom workspaces. We document the brand structure and deliver a written workspace strategy recommendation during discovery. The decision has licensing and routing implications that must be resolved before migration begins.
Automations do not migrate and have no Intercom equivalent
Zendesk Automations run hourly in batches of up to 1,000 tickets with a 500-active-automation cap.
How we handle it
Intercom Rules are event-driven only and cannot replicate time-based batch actions. Any Zendesk Automation that closes stale tickets, escalates based on elapsed time, or sends scheduled notifications cannot be recreated in Intercom natively. We audit active automations, deliver a written inventory with an Intercom Rule or third-party workflow tool recommendation for each, and flag any automations with no achievable replacement. The customer's admin rebuilds automation logic manually post-migration.
Custom Objects (Enterprise-only in Zendesk) have no Intercom equivalent
Zendesk Custom Objects v2 (Enterprise and Enterprise Plus only) allow user-defined schemas with lookup relationships to Tickets, Users, or Organizations.
How we handle it
Intercom has no custom object model; any custom data must flatten into Contact or Conversation custom attributes. We audit Zendesk Custom Object schemas during discovery, export all records, and flatten the data into Intercom custom attributes on the appropriate Contact or Conversation object. Relational lookups (e.g., linking a Ticket to a custom Order object) become denormalized text fields in Intercom; the customer's admin must evaluate whether a separate CRM integration handles relational data needs post-migration.
How the migration runs
Discovery and workspace strategy
We audit the source Zendesk account across plan tier, active ticket volume, user count, organization count, brand count, Help Center article count and section hierarchy, active tag taxonomy, SLA policy definitions, automation definitions, and macro definitions.
What this step covers
We pair this with a review of the destination Intercom workspace configuration requirements, including whether multi-brand consolidation is needed and whether Fin AI training is in scope. The discovery output is a written migration scope document and an Intercom workspace configuration recommendation. We confirm ticket field customizations (custom ticket fields, custom user fields) that need to be pre-created in Intercom as conversation or contact attributes before data import begins.
Schema pre-creation and sandbox migration
We provision custom fields in Intercom (Contact attributes and Conversation attributes) to match Zendesk custom field definitions, including field types, labels, and options where applicable.
What this step covers
We create Intercom Teams corresponding to Zendesk Groups. We run a sandbox migration with a representative subset of records to validate the object mapping, confirm the ticket-to-conversation status translation, verify SLA attribute population, and reconcile tag assignments. The customer's team spot-checks 20-30 records in the sandbox before we proceed to production migration.
Help Center article migration
We extract Zendesk Help Center articles, section hierarchy, and translations via the Help Center API.
What this step covers
Articles are transformed to Intercom Article format and published to the corresponding Intercom collection. Article attachments download from Zendesk and upload to Intercom as article file attachments. We flag any articles with content that requires Fin AI training review (e.g., articles that Fin AI should deflect before a human agent responds). The Help Center migration runs before the ticket migration so that articles are live and Fin AI can reference them during the cutover window.
Ticket migration in dependency order
We migrate Tickets in a staged approach: closed tickets first (historical archive), then open tickets with active assignments.
What this step covers
Each Zendesk ticket maps to an Intercom Conversation with the requester as a Contact, the assignee as a Teammate or Admin, the group as a Team, and the status translated to Intercom's open/closed state. SLA policy data, priority, and tags populate as Conversation attributes. Internal notes transfer as note-type messages within the conversation. We batch tickets in groups of 500 and use the Intercom Conversations API with rate-limit handling and retry logic. Attachments download from Zendesk and upload to Intercom as conversation file attachments.
User and organization migration
We import Zendesk Users (requesters and agents) as Intercom Contacts and Admins/Teammates respectively.
What this step covers
Organizations map to Intercom Companies with domain names and user memberships. The Zendesk agent reconciliation queue (agents without matching Intercom users) resolves before production migration begins. Organization membership on users maps to Intercom's Company-Contact relationship. We run a record-count reconciliation across all three object types before closing the migration phase.
Cutover, Fin AI activation, and automation handoff
We freeze Zendesk writes during cutover, run a final delta migration of any tickets modified during the migration window, and enable Intercom as the system of record.
What this step covers
We deliver a written inventory of every Zendesk Trigger, Automation, Macro, View, and SLA Policy requiring rebuild in Intercom, with recommended Intercom Rules equivalents or third-party workflow tool suggestions. We do not rebuild automations as part of the migration scope. We support a five-business-day hypercare window for reconciliation issues. Fin AI activation (training the bot on migrated Articles) is a post-migration step that the customer's team or an Intercom onboarding partner completes independently.
- Connect
- Map
- Sample
- Migrate
- Verify
- Contacts48,210 / 48,210 Done
- Companies9,134 / 9,134 Done
- Deals6,377 / 11,920 In progress
- Before sample runRestore point 01Restore
- Before full migrationRestore point 02Restore
- After verificationRestore point 03Current
How long it takes, and what drives the quote
A quote scales with record volume, Help Center article count, and the number of Zendesk objects requiring manual rebuild mapping. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for Zendesk to Intercom →Why teams move from Zendesk to Intercom
- Per-agent pricing with aggressive feature-gating drives sticker shock at renewal. Zendesk's base price ($55-$169/agent/mo) compounds with Advanced AI ($50/agent), WFM ($25/agent), and QA ($35/agent) add-ons, pushing effective costs 2-3x above the advertised rate. Teams with 10-20 agents report annual bills of $50,000-$80,000 before usage-based API overages. Intercom's per-seat pricing ($29-$132/seat/mo) plus Fin AI at $0.99/resolution is more transparent and often cheaper for teams under 30 agents, particularly where AI deflection reduces resolution volume.
- Teams prioritizing conversational, product-led customer engagement find Zendesk's ticket-centric model mismatched to their workflow. Zendesk excels at structured, high-volume support with formal routing and SLA enforcement, but for product-led SaaS companies where support blends with onboarding, activation, and customer success, Intercom's Messenger-first approach with Fin AI and proactive in-app messaging fits more naturally. G2 reviewers cite this as the primary reason for switching when evaluating Intercom as a Zendesk alternative.
- Setup and configuration complexity on Zendesk frustrates smaller and mid-sized teams. Multiple configuration layers, plan-gated features, and week-long implementation timelines for multi-channel setups push teams toward Intercom's faster time-to-value. Reddit reviewers describe Zendesk as 'outdated' and 'creaky' compared to Intercom's modern interface, while Intercom's implementation can reach a working state in days versus weeks for equivalent Zendesk configurations.
- Zendesk's export restrictions on Team and Essential plans force teams to use API scripting or a migration service to retrieve their own data. Non-Enterprise plans lack a native export UI, which customers perceive as a vendor lock-in tactic. Intercom provides a cleaner exit path with a self-service data export available on all plans, lowering the switching cost and reducing dependency on a migration service for future moves.
- Knowledge base and help center isolation in Zendesk creates friction for teams that want self-service support embedded in the same conversational context as live chat. Zendesk separates Guide from Support with its own permission model and versioning, while Intercom's Articles are natively integrated into the Messenger and immediately available to Fin AI for resolution deflection. Teams seeking a unified support and self-service experience move to Intercom for this architectural simplicity.
Questions, answered
Zendesk to Intercom migration questions
How long does a Zendesk to Intercom migration take?
Most migrations land between three and five weeks for accounts under 15,000 tickets, 5,000 contacts, and a single-brand setup with a straightforward Help Center. Multi-brand Zendesk accounts, Help Centers with over 500 articles, complex custom fields, or extensive tag taxonomies move to eight to twelve weeks because of workspace strategy decisions, Help Center remapping, and the automation rebuild documentation scope. Intercom's Fin AI activation (training the bot on migrated Articles) is a post-migration step that adds 1-2 weeks to the full go-live timeline.
Do Zendesk Triggers, Automations, Macros, and SLA Policies migrate to Intercom?
No. Zendesk's automation engine (Triggers and Automations) has no direct Intercom equivalent; Intercom Rules are event-driven and cannot replicate time-based batch actions or the 1,000-tickets-per-hour processing model. SLA Policies cannot migrate because Intercom has no native SLA object or enforcement feature. Macros require manual conversion from Zendesk's variable syntax to Intercom's {{contact.name}} syntax. We deliver a written inventory of every active Trigger, Automation, Macro, View, and SLA Policy with a recommended Intercom Rules equivalent or a note that no native replacement exists. The customer's admin rebuilds these manually post-migration.
Do we lose ticket status history and SLA compliance data?
Ticket content and timestamps migrate fully. However, Zendesk's granular ticket statuses (New, Open, Pending with reason codes, Solved, Closed) collapse into Intercom's binary open/closed state. We preserve the original Zendesk status in a custom Conversation attribute for agent reference, but Intercom's inbox does not surface it natively. SLA compliance data (first-response and resolution target tracking) cannot migrate as a native feature; we store SLA Policy definitions as custom Conversation attributes and deliver a written SLA inventory document. The customer's admin must implement a third-party SLA tracking solution or webhook-based tool if SLA compliance reporting is required.
Can we keep Zendesk's multi-brand structure in Intercom?
Intercom has no native multi-brand concept within a single workspace. Multi-brand Zendesk customers must choose between consolidating into one Intercom workspace (with brand identity preserved in conversation tags and routing rules) or purchasing multiple Intercom workspaces. We document the brand structure and deliver a written workspace strategy recommendation during discovery. The decision affects licensing (one vs. multiple Intercom accounts), routing configuration, and reporting scope. We do not configure multiple Intercom workspaces as part of the migration scope; that is a separate architecture decision.
How do we handle Zendesk Custom Objects in Intercom?
Intercom has no custom object model. Any Zendesk Custom Objects (Enterprise and Enterprise Plus only) must be flattened into Intercom Contact or Conversation custom attributes. Relational lookups between custom objects and Tickets become denormalized text fields in Intercom. We audit Zendesk Custom Object schemas during discovery, export all records, and map them to Intercom attributes. The customer evaluates whether a separate CRM integration handles relational data needs post-migration. We document the flattened attribute mapping and flag any lookup relationships that cannot be represented in Intercom's schema.
What happens to our Help Center and knowledge base articles?
We migrate Zendesk Help Center articles, section hierarchy, translations, and attachments to Intercom Articles via the Help Center API and Intercom Articles API. Section and category structure maps to Intercom collections. Published, draft, and archived states transfer. After migration, Fin AI can reference the imported Articles for resolution deflection, but Fin AI must be trained on the new content post-migration; this training step is outside the migration scope and is completed by the customer's team or an Intercom onboarding partner. We provide a Fin AI training checklist as part of the handoff documentation.
What data does FlitStack AI NOT migrate from Zendesk to Intercom?
We do not migrate Triggers, Automations, SLA Policies, Views, Macros, Brands, or Custom Objects as code or functional equivalents. These require manual rebuild in Intercom's configuration tools or a third-party workflow solution. We do not migrate Zendesk's Sunshine Conversations data (included with Suite Professional and Enterprise plans purchased after April 13, 2023) as it is a separate messaging product with its own data model. We do not provide post-migration admin support, workflow rebuild, or Fin AI training as standard scope; these are separate engagements with our team or an Intercom-certified implementation partner.
Related migrations
Sources: official documentation
- Import your user data into Intercom — Intercom Help
- Import your customers — Intercom Academy
- Create and track Custom Data Attributes (CDAs) — Intercom Help
- Events limits, troubleshooting and F.A.Q — Intercom Help
- About ticket import — Zendesk help
- How can I bulk update users — Zendesk help
- About custom objects — Zendesk help
Get a quote
Moving from Zendesk to Intercom?
Tell us roughly how many records and objects you have. We scope the mapping and the Intercom setup with you, then send a quote.
Get a quote