Intercom to Zendesk Data Migration

Moving from Intercom to Zendesk? Settle automates the mapping between Intercom's conversation model and Zendesk's ticket architecture — preserving chat history, contact data, company records, and help center content.

Working with enterprise teams on active migration programs

settle — IntercomZendesk
SourceTarget
ConversationTicket
Conversation PartTicket Comment
UserUser (end user)
LeadUser (filtered)
CompanyOrganization
+6 more objects mappedEvery row validated
See full mapping →

Days

to production-ready mappings

Roughly half

the cost of consulting-led delivery

Every row

validated before go-live

Enterprise migrations routinely run months behind schedule. Yours doesn't have to.

This guide is for VPs of IT, data architects, and migration leads at companies moving data from Intercom to Zendesk — whether you're scoping, planning, or mid-program.

Intercom stores support data in conversations with user and lead records, company associations, and a help center with articles and collections. Zendesk uses tickets with user and organization records, custom fields, and a Help Center with categories and sections. Settle translates Intercom's conversation-first model to Zendesk's ticket-based architecture automatically.

Based on the founding team's enterprise migration experience

Last updated July 2026

How Settle automates your Intercom to Zendesk migration

  • Settle converts Intercom conversations to Zendesk tickets — classifying each conversation part as a public comment or internal note based on message type, preserving timestamps and author attribution.

  • Users and Leads are profiled — Settle recommends which Intercom Leads have enough data quality to become Zendesk users vs. which should be filtered out. Users are matched to Companies for Organization association.

  • Custom attributes are mapped to Zendesk custom fields with type translation — text, number, date, dropdown — based on actual data content analysis.

  • Help Center content migrates with collection-to-category structure mapping, article content preservation, and metadata translation.

See how Settle works end-to-end →

Get your Intercom to Zendesk mapping analysis — see results in under an hour

Migration timeline: manual vs. Settle

Traditional approach

Timeline

1–3 months

Estimated cost

$75K–$250K

Team size

1–2 consultants

Typically requires

×Manual field mapping in spreadsheets

×Custom ABAP/SQL extraction scripts

×3–5 mock migration cycles

×Dedicated source system consultants

×Manual reconciliation testing

With Settle

Enterprise benchmarks

Timeline

Days

Estimated cost

A fraction of consulting cost

Team size

1 internal resource

Included

Schema profiling & analysis

AI-generated field mappings

Transformation SQL

Validation & readiness reports

Production-ready load files

Common challenges migrating from Intercom to Zendesk

Conversation to ticket model translation

Intercom conversations are unified message threads combining chat, email, and in-app messages. Zendesk tickets separate comments by type (public reply, internal note) with channel tracking. Converting Intercom's conversation parts to Zendesk's comment model requires classifying each message as public or internal and preserving timestamps and author attribution.

Explore related migrations →

User and Lead distinction

Intercom separates Users (identified, logged-in) from Leads (anonymous or unidentified visitors). Zendesk has no lead concept — all contacts are users. Intercom Leads must either be converted to Zendesk users or filtered out. Settle analyzes lead data quality to recommend which records to migrate.

Explore related migrations →

Custom attributes to custom fields

Intercom's custom attributes on conversations, users, and companies use flexible typing. Zendesk custom ticket and user fields have stricter type requirements. Each attribute needs analysis of actual data content, not just declared type.

Explore related migrations →

Help Center to Help Center

Intercom's Help Center uses collections and sections. Zendesk's Help Center uses categories and sections. The structures are similar but article metadata, access permissions, and content formatting differ. Multi-language article handling also varies.

Explore related migrations →

Intercom to Zendesk field mapping — what data moves

11 data objects typically migrated

Source ObjectTarget Object
ConversationTicket
Conversation PartTicket Comment
UserUser (end user)
LeadUser (filtered)
CompanyOrganization
Admin / TeammateUser (agent)
TeamGroup
Custom AttributesCustom Fields
TagsTags
Help Center ArticleHelp Center Article
Help Center CollectionHelp Center Category

Typical enterprise migrations include 500K–10M+ records across these objects. Settle handles profiling and mapping at enterprise scale.

The cost of manual Intercom to Zendesk migration

Intercom to Zendesk migrations happen when companies need dedicated help desk capabilities beyond Intercom's messaging-first approach. While Intercom excels at conversational support and product tours, companies with complex support workflows — multi-tier escalation, SLA management, advanced ITSM features, or deep reporting — often move to Zendesk. This migration is also common when companies separate product engagement (keeping Intercom) from customer support (moving to Zendesk).

The technical challenge is translating Intercom's conversation model to Zendesk's ticket model. Intercom conversations are messaging threads that combine chat, email, and in-app messages into a single thread. Zendesk tickets use a different model with separate comment types (public replies, internal notes) and distinct channels. Intercom's user and lead distinction doesn't exist in Zendesk — all become users. Custom attributes map to custom ticket fields differently.

Companies typically use Zendesk's data migration tools or manual CSV exports. The conversation-to-ticket translation, user matching, and help center content migration require manual effort.

Consulting-led delivery for migrations in this class typically runs $75K–$250K. Settle prices it fixed and scoped — read the full cost breakdown.

Explore all migration paths →

Frequently asked questions

A typical Intercom-to-Zendesk migration takes 1–3 months. The conversation-to-ticket translation and Help Center migration are the most complex parts. Settle runs the same migration in days — every row validated before load.

Exceptions surface before the first load, not after the third.

Built by the team that ran Fortune 500 migrations by hand. Currently onboarding enterprise design partners on active migration programs.

Ready to migrate from Intercom to Zendesk?

Tell us about your migration and we'll show you how Settle can help.

No commitment required. We'll review your migration scope and share a preliminary assessment within 48 hours.

✓ No credit card✓ 48-hour response✓ Free initial assessment

We'll review your migration scope and follow up within 48 hours to discuss next steps.

Or book a demo call →