Intercom to Zendesk migration
We migrate Contacts, Companies, Conversations, and Help Center articles from Intercom into Zendesk with the conversation-to-ticket model resolved up front, message threading preserved through the REST API, and every Intercom custom attribute mapped to a typed Zendesk field before cutover.
FlitStack AI migrates end users, organizations, tickets, ticket comments and agents from Intercom to Zendesk, 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 Intercom to Zendesk?
Moving from Intercom to Zendesk is a data-model migration, not a simple record copy.
Read the full summary
Intercom organizes around a conversation-first model where Contacts and Companies hold context and message threads live as nested Conversation Parts; Zendesk uses a ticket-first model where all context is attached to a Ticket record with an Organization and User lookup. We resolve that structural difference during scoping by flattening Intercom conversation threads into Zendesk ticket comments, mapping Conversation state to Ticket status, and preserving the original conversation ID as a reference field for audit. Help Center Articles migrate as Guide articles, but Collections require decomposition into Zendesk Sections and Categories. We do not migrate Intercom workflows, custom bots, or Outbound sequences as code; we deliver a written inventory of every active automation for the customer's admin to rebuild in Zendesk.
Contact (User) → End User
Intercom Contacts (Users) map directly to Zendesk End Users.
How it maps
Email, name, custom attributes, and created_at timestamps migrate 1:1. The intercom_user_id is preserved as a custom field zendesk_migration_source_id for audit and cross-referencing. Intercom Leads are treated as Contacts with a custom attribute lead_status__c to preserve source classification.
Company → Organization
Intercom Companies map to Zendesk Organizations.
How it maps
The company domain becomes the Organization's domain field. We preserve the company-contact association so that all migrated End Users are linked to their parent Organization. plan and monthly_spend from Intercom migrate to custom fields on the Organization record.
Conversation → Ticket
Intercom Conversations map to Zendesk Tickets.
How it maps
Each conversation becomes a single Ticket with the conversation subject or first message body as the Ticket subject. Conversation state (open, closed, snoozed) maps to Zendesk Ticket status (open, pending, solved, closed). The original intercom_conversation_id is stored as a custom field for audit. Multiple Intercom conversations from the same Contact can optionally be merged into a single Zendesk Ticket using a conversation-grouping rule defined during scoping.
Conversation Part (Message) → Ticket Comment
Intercom Conversation Parts (messages, notes, assignments, rating submissions) merge into a single Zendesk Ticket as sequential Comments.
How it maps
Message body, author (agent or contact), and timestamp are preserved. Internal notes in Intercom map to Zendesk internal Comments. Part type (comment, note, assignment, close, rating) is stored as a comment attribute. We use the Intercom retrieve-conversation endpoint to pull full transcript content because the S3 JSON export excludes message bodies.
Admin → Agent
Intercom Admins map to Zendesk Agents.
How it maps
We match by email address. Agent role (admin, agent, viewer) maps to Zendesk role. Intercom away/available states do not transfer; agents set availability in Zendesk on first login. We flag any Admin without a matching Zendesk User for the customer's admin to provision before the production migration phase.
Team → Group
Intercom Teams map to Zendesk Groups.
How it maps
Group membership migrates so that ticket routing rules defined in Zendesk reference the correct Groups. If Intercom's team-based routing is configured via Inbox rules, we document the routing logic for manual reconstruction in Zendesk Triggers or Automations.
- ContactEnd User1:1
- CompanyOrganization1:1
- ConversationTicket1:1
- Conversation PartTicket Commentmerged
- AdminAgent1:1
- TeamGroup1:1
+ 6 more in the mapping below
How Intercom and Zendesk 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 | Intercom | Zendesk |
|---|---|---|
| Core data model | Conversation-first: threads of Parts attached to Contacts and Companies | Ticket-first: all context attached to Tickets with Organization and User lookups |
| Agent hierarchy | Teams of Admins with inbox routing | Groups of Agents with views and SLAs |
| AI billing | Fin AI at $0.99 per resolution, compounding with automation success | Zendesk AI at $1.50 committed or $2.00 pay-as-you-go, flat per-agent bundles available |
| Workflow model | Custom Bots, Outbound, and Operator automation rules | Triggers, Macros, and Automations in the Zendesk platform |
| Help center structure | Articles inside Collections inside a single workspace Help Center | Articles inside Sections inside Categories across multiple Guide locales |
| Custom attributes | Data Attributes scoped to Contacts, Companies, and Conversations | Custom Fields on Tickets, Users, and Organizations with typed field definitions |
| Workspace isolation | No cross-workspace migration of workflows, bots, or content | Cross-brand migration supported in Enterprise; Global Export available |
What to watch for in a Intercom to Zendesk migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
Conversation-to-ticket flattening loses threading context
Intercom conversations are deeply nested threads of Parts with context (assignments, notes, ratings, internal comments) interleaved with customer messages.
How we handle it
Zendesk Tickets are flat comment threads where internal notes are a visibility flag rather than a separate Part type. We flatten Intercom Part sequences into Zendesk Comments in chronological order and flag the Part type in a custom attribute, but the threaded conversation tree structure in Intercom does not render identically in Zendesk. Teams should review sample ticket output during the sandbox migration phase to confirm that the flattened view meets their audit and customer communication needs.
S3 JSON export excludes conversation transcripts
Intercom's native Data Export to Amazon S3 stores conversation metadata and message bodies but explicitly excludes transcripts.
How we handle it
Teams relying on S3 export for migration will have empty message fields. We pull full conversation content via the Intercom REST API retrieve-conversation endpoint, which includes the full transcript body, author, and timestamp. This requires one API call per conversation rather than one bulk download, so migration timelines scale with conversation volume and API quota availability. We monitor X-RateLimit-Remaining headers and throttle dynamically to avoid quota exhaustion.
Intercom workflows and custom bots do not migrate to Zendesk
Intercom's Outbound, Operator, and custom bot automations are structurally incompatible with Zendesk Triggers, Macros, and Automations.
How we handle it
The workspace isolation constraint also means that even if a technical mapping existed, Intercom workspaces cannot export automation logic. We deliver a written automation inventory listing every active Intercom workflow, its trigger conditions, actions, and routing logic, with a Zendesk Trigger or Macro equivalent for the customer's admin to rebuild. This is a separate configuration effort outside the data migration scope.
Custom attributes require pre-creation in Zendesk before data migration
Intercom custom attributes are discovered at the workspace level and apply to Contacts, Companies, and Conversations.
How we handle it
Zendesk custom fields must be created as typed field definitions (text, number, date, dropdown, checkbox) on the target object (User, Organization, Ticket) before any records are imported. If custom fields are missing, the import job will silently drop or error on attribute values. We audit the full attribute schema during scoping, define Zendesk field types, and deploy the schema before production migration begins. This pre-creation step adds one to two weeks to the timeline.
Two-year historical export limit may exclude older conversations
Intercom's historical data export is capped at two years of conversation retrieval.
How we handle it
Teams with support histories exceeding two years cannot export older conversations through the native export feature. We use the REST API with date-range filtering to retrieve whatever historical data is accessible and document the gap explicitly during scoping so the customer can decide whether to accept the data loss window or pursue a separate archival approach. Historical data outside the two-year window is flagged as unmigrated and remains accessible in Intercom for audit purposes if the subscription is maintained.
How the migration runs
Discovery and scoping
We audit the source Intercom workspace across Admins, Teams, Contacts, Companies, Conversations (open and closed), Help Center Articles and Collections, Custom Attributes, Segments, and any Ticket objects in use.
What this step covers
We pull conversation volume by date range to confirm how much history falls inside or outside the two-year export window. We pair this with a Zendesk configuration survey covering the target brand, Guide locale structure, Group and Agent provisioning plan, and any existing Zendesk custom fields that must be preserved. The discovery output is a written migration scope with object counts, a custom attribute mapping table, and a recommendation on full-switch versus staggered migration strategy.
Zendesk schema pre-creation
Before any data moves, we create the Zendesk destination schema.
What this step covers
This includes provisioning Groups from Intercom Teams, setting up Agent roles and availability settings, creating Organization fields for Intercom Company attributes, creating User fields for Intercom Contact custom attributes, and creating Ticket fields for Intercom Conversation custom attributes and custom Ticket attributes. For the Help Center, we map Intercom Collections to Zendesk Sections and Categories. Custom Object definitions in Zendesk Sunshine are created with equivalent attribute schemas to the Intercom Custom Objects being migrated. All schema creation happens in the production Zendesk environment with the migration user's admin credentials.
Sandbox migration and reconciliation
We run a sample migration into the live Zendesk environment using a representative slice of data: 200-500 closed conversations, 50-100 open conversations, 50 contacts, 20 companies, and 10 articles.
What this step covers
The customer's support operations lead reviews the output against the source Intercom data and validates that conversation threading is readable, custom attributes are populated, agent assignments are correct, and article content is complete. Any mapping corrections are documented and applied to the production migration scripts before the full run begins.
Conversation migration with transcript retrieval
We migrate Intercom Conversations to Zendesk Tickets in dependency order: first, closed conversations (no urgency, full timeline available), then open conversations on cutover day.
What this step covers
Because the S3 export excludes message bodies, we pull full transcript content per conversation using the retrieve-conversation endpoint. Each Conversation Part becomes a Zendesk Comment with Part-type metadata preserved. Internal notes in Intercom become internal comments in Zendesk. Conversation state maps to Ticket status. We batch conversations by date range to manage API quota and monitor rate limit headers throughout the run. Any conversation that returns a 429 or 5xx response is retried with exponential backoff.
Cutover and delta migration
On the agreed cutover date, we pause new conversation creation in Intercom by routing inbound messages to a holding queue or enabling Zendesk as the primary channel first.
What this step covers
We run a final delta migration of any conversations created or modified during the migration window. Zendesk becomes the system of record once the delta migration completes and the customer confirms ticket visibility in Zendesk. We deliver the automation inventory document (workflows, bots, Outbound sequences) to the customer's admin team for rebuild planning. We do not rebuild Intercom automations inside the migration scope.
Hypercare and post-migration handoff
We support a five-business-day hypercare window following cutover.
What this step covers
During this period we resolve any data quality issues raised by the support team (incorrect agent assignments, missing custom attributes, article formatting breaks). We do not provide Zendesk admin training or workflow rebuild as part of the standard scope; these are separate engagements. The automation inventory document and the field mapping spreadsheet serve as the handoff artifacts for the customer's Zendesk admin to proceed 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 conversation volume, custom attribute count, and whether a staggered or full-switch migration strategy is chosen. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for Intercom to Zendesk →Why teams move from Intercom to Zendesk
- Teams move from Intercom to Zendesk when they outgrow chat-first support and need structured SLA management with ticket priorities, escalation paths, and first-response and resolution targets. Zendesk's SLA engine is native and configurable per plan tier, whereas Intercom's SLA tooling requires the Pro add-on at $99/month and offers less granular policy control. Reviewers on Capterra and G2 who cite SLA management as a reason for switching note that Zendesk enforces SLA breaches at the workflow level whereas Intercom relies on agent attention.
- Intercom pricing compounds unpredictably with seat count, Fin AI resolution fees ($0.99 each), Copilot add-ons ($29/agent/month), and channel-based charges for SMS, WhatsApp, and Phone. Teams report monthly bills jumping from $4k to $9k without corresponding volume changes. Zendesk's tier-based pricing ($19-$169/agent/month across Support Team through Suite Enterprise) is more predictable at scale because AI resolution fees are bundled or absent, and channel costs are included in higher tiers.
- Intercom's S3 JSON export deliberately excludes conversation transcripts, and the two-year historical retrieval window limits access to older support history. Zendesk's data model stores ticket comments inline, and the API exposes full audit history without a transcript extraction gap. Teams migrating long-running customer relationships lose message body context in Intercom's S3 export and must compensate with REST API calls per conversation, which adds API quota pressure during migration.
- Zendesk's Help Center supports multilingual content, advanced search, and Community forums natively across locales, whereas Intercom's help center is scoped to a single workspace with no built-in multilingual routing. Teams operating in multiple languages cite Zendesk's Global Export and multi-locale Guide as a reason for switching, particularly when article volume exceeds 200 and localization workflow integration matters.
- Intercom workspaces operate in isolation, preventing any migration of workflows, custom bots, Outbound sequences, or help center content between environments. This means a staging-to-production migration requires a full rebuild of all automation logic. Zendesk supports sandbox environments in Enterprise and Global Export for moving configuration between brands, which reduces rebuild scope for teams with multi-environment Zendesk setups.
Questions, answered
Intercom to Zendesk migration questions
How long does an Intercom to Zendesk migration take?
Most migrations land between three and five weeks for accounts under 50,000 conversations, no custom objects, and a straightforward collection-to-section help center structure. Migrations with large custom attribute schemas (over 50 custom fields), help center article counts exceeding 500, or staggered cutover strategies requiring a delta migration phase move to six to ten weeks because of Zendesk schema pre-creation time, per-conversation API calls for transcript retrieval, and the additional validation window before cutover.
Do Intercom workflows, custom bots, and Outbound sequences migrate to Zendesk?
No. Intercom's automation stack (Outbound, Operator, and custom bot workflows) is architecturally incompatible with Zendesk Triggers, Macros, and Automations. Additionally, Intercom workspace isolation prevents exporting automation logic even if a mapping existed. We do not migrate them as code. We deliver a written automation inventory listing every active Intercom workflow, its trigger conditions, routing actions, and recommended Zendesk equivalent (Trigger or Macro). The customer's Zendesk admin rebuilds the automation logic post-migration. Sequences and sales engagement cadences do not migrate and require a separate rebuild or a sales engagement tool adoption.
Do we lose historical conversation transcripts during migration?
No, if we use the REST API. Intercom's S3 JSON export deliberately excludes conversation message bodies and transcripts. We pull full transcript content via the Intercom REST API retrieve-conversation endpoint for each migrating conversation. This is the correct approach for audit and customer communication continuity, but it means migration timelines scale with conversation volume and API quota. We monitor rate limit headers and throttle dynamically. The two-year historical export window may exclude conversations older than two years; we document the gap during scoping and the customer decides whether to accept the window or pursue a separate archival approach.
How are Intercom Segments handled during migration?
Intercom Segments are dynamic rule-based audience definitions that recompute in real time based on Contact attributes and behavior. These cannot migrate as live dynamic queries because Zendesk does not support the same rule engine. We take a membership snapshot at migration time and create Zendesk Saved Searches (Views) with equivalent filter criteria so that the same audience can be reviewed in Zendesk. The customer reconciles whether any migrated Saved Searches need to become dynamic (recomputed) after migration, which requires Zendesk Explore reporting or a third-party segmentation tool.
Can we run Intercom and Zendesk in parallel during migration?
Yes. A staggered migration strategy runs Zendesk alongside Intercom for a defined period, migrating all closed conversations first without impacting live support. On cutover day, we migrate open conversations and redirect inbound channels to Zendesk. This approach is recommended for teams with high daily ticket volume where a full-switch migration window would create a support gap. We coordinate the channel redirection with the customer's technical team to minimize disruption. The parallel period adds one to two weeks to the timeline but eliminates pressure on the migration window.
What happens to Intercom's Fin AI agent data during migration?
Fin AI resolution history, deflection metrics, and training feedback are Intercom-specific and do not have a direct equivalent in Zendesk. Resolution records can be exported as data but cannot be recreated in Zendesk's Intelligent Triage or Answer Bot without retraining. We recommend exporting Fin AI deflection statistics as a reference report before cutover. Zendesk AI is configured separately post-migration using the migrated help center articles as the knowledge base. We do not transfer Fin AI training data or conversation logs as they are tied to the Intercom workspace and not accessible via API in a reusable format.
How does the Intercom Help Center map to Zendesk Guide?
Intercom Articles map to Zendesk Guide Articles with title, body HTML, author, publication state, and URL slug transferred. Intercom Collections map to Zendesk Sections, and top-level categorization maps to Zendesk Categories. If Intercom Articles have multiple language versions, each version migrates as a separate locale in Zendesk Guide. Article-specific public URLs do not transfer because Zendesk generates its own article slug system. Custom article attributes migrate as article custom fields in Zendesk Guide, which requires pre-creation of the field schema before article migration begins.
Related migrations
Sources: official documentation
- About ticket import — Zendesk help
- How can I bulk update users — Zendesk help
- About custom objects — Zendesk help
- Bulk importing user data with the data importer — Zendesk help
- Import your user data into Intercom — Intercom Help
- Import your customers — Intercom Academy
- Create and track Custom Data Attributes (CDAs) — Intercom Help
Get a quote
Moving from Intercom to Zendesk?
Tell us roughly how many records and objects you have. We scope the mapping and the Zendesk setup with you, then send a quote.
Get a quote