How do we migrate from Zendesk to Intercom—data import, macros/automations, and keeping reporting intact?

Migrating from Zendesk to Intercom is less about “lifting and shifting” tickets and more about designing one connected system—Helpdesk + Fin AI Agent + Messenger + Help Center—that will scale for the next few years. The good news: you can get there in days, not months, if you’re deliberate about what to migrate, how to map automation, and how to preserve (and improve) your reporting.

In this guide I’ll walk through how I approach a Zendesk → Intercom migration as an operator: what data to bring over, how to translate macros and automations, and how to keep your reporting intact so you don’t lose historical performance or forecasting capability.

The Quick Overview

What It Is: A practical framework for moving from Zendesk to Intercom’s Customer Service Suite without losing critical data, automation logic, or reporting continuity.
Who It Is For: Support leaders, system owners, and admins planning to replace Zendesk with Intercom—or run a Fin-first deployment alongside Zendesk before fully cutting over.
Core Problem Solved: You want to modernize your stack with Intercom’s AI-first system, but you can’t afford to break existing workflows, lose historical insight, or confuse customers during the transition.

How It Works

At a high level, a Zendesk → Intercom migration breaks into three phases: design, dual-running, and cutover. You’re not just moving tickets; you’re building a self-improving support system where Fin resolves the majority of queries, humans handle the rest from a shared Inbox, and reporting spans both AI and human performance.

Phase 1 – Design & Mapping:
- Audit your Zendesk instance: ticket fields, macros, triggers, automations, views, SLAs, and tags.
- Decide what data you truly need to migrate (customers, orgs, core ticket attributes, key tags—not every historic ticket).
- Map Zendesk concepts to Intercom primitives: tickets to Intercom tickets/conversations, macros to macros + Workflows, triggers to Workflows, help center to Intercom Help Center, bots to Fin.
Phase 2 – Dual-Run & Configure:
- Install Intercom Messenger on web/product (optionally boot behind consent or for a subset of users).
- Configure your Helpdesk: Inbox, ticket types, rules, SLAs, Help Center, and Workflows that mirror your highest-volume Zendesk flows.
- Train and test Fin on your knowledge base and procedures; deploy on low-risk paths first while Zendesk still runs in parallel.
- Import key users/companies and, if needed, a minimal set of historic tickets for context.
Phase 3 – Cutover & Optimization:
- Switch channels to Intercom (web, email, WhatsApp, Instagram, SMS) with clear routing.
- Turn off or downscope Zendesk triggers/macros to avoid double replies.
- Use Intercom reporting and AI Insights to tune Fin, workflows, and macros—so the system improves week over week.
- Decommission Zendesk once contractual/operational dependencies are cleared, retaining exports for compliance and long-term trend analysis where needed.

Features & Benefits Breakdown

Here’s how Intercom’s core capabilities replace (and usually improve on) Zendesk components during migration:

Core Feature	What It Does	Primary Benefit
Helpdesk & Inbox	Centralizes all conversations (Messenger, email, WhatsApp, SMS, Instagram, etc.) with tickets, customer context, SLAs, and automation in one place.	Gives agents a single, AI-powered workspace—so they resolve complex queries faster without switching tools.
Fin AI Agent & Workflows	Resolves most customer queries using your content and procedures, triggers workflows, and hands off seamlessly to humans when needed.	Replaces shallow “deflection” bots with true resolution—so volume rises without breaking your team.
Macros, Help Center & Reporting	Combines reusable replies, a no-code Help Center, and deep reporting on topics/channels/AI vs human performance.	Preserves and enhances your reporting—so you can compare pre- and post-migration performance and continuously optimize.

Planning Your Zendesk → Intercom Migration

Before touching data, design the operating model you want in Intercom. This ensures you’re migrating with intent, not replicating legacy constraints.

1. Decide your migration strategy

I typically choose one of three patterns:

Big bang cutover: For smaller teams or simpler setups. You configure Intercom, run an internal pilot, and then switch all channels on a defined date.
Channel-by-channel: Migrate web/Messenger first, then email, then messaging channels. This reduces risk and lets you tighten workflows incrementally.
Fin-first alongside Zendesk: Keep Zendesk as your primary helpdesk but deploy Fin + Intercom Messenger as the AI front door. Once Fin and workflows are solid, migrate the helpdesk itself.

If you rely heavily on Zendesk reporting or have many channels, I recommend channel-by-channel or Fin-first. It keeps blast radius small and your reporting comparable.

2. Map Zendesk concepts to Intercom primitives

Use this mapping as your base:

Tickets (Zendesk) → Conversations + Tickets (Intercom)
- Simple interactions can live as conversations only; more complex or multi-step issues use Intercom tickets.
Organizations → Companies in Intercom
Users → Users / Leads in Intercom (depending on auth state)
Ticket fields → Ticket attributes / custom attributes in Intercom
Tags → Tags + attributes + Inbox views
Macros → Macros + Workflows + Fin responses
Triggers & Automations → Workflows (plus rules, SLAs, and routing)
Views → Inbox views + reporting dashboards
Help Center (Guide) → Intercom Help Center
Answer Bot / Bots → Fin AI Agent + Workflows

Build a simple spreadsheet with columns for “Zendesk Object,” “Intercom Object,” “Must Have,” and “Notes/Logic” so the team has a shared map.

Data Import: What to Bring and How

You don’t usually need every historic ticket in Intercom to run effectively. You need enough customer context for current work, plus exports for compliance and long-term trend analysis.

1. Decide on your data scope

I split data into three categories:

Operationally critical to migrate into Intercom:
- Active and recently closed tickets (e.g., last 3–6 months) for high-value customers.
- Current customers/organizations (companies) with relevant attributes (plan, MRR, lifecycle, region).
- Key ticket fields you rely on for routing or SLAs (priority, product area, category, severity).
Nice to have in Intercom (depending on size):
- Tags that meaningfully drive workflows or reporting.
- SLA breach status or backlog flags you still need to work through.
Archived outside Intercom:
- Older tickets that don’t inform daily operations but are needed for compliance or historical analysis.
- Detailed channel-by-channel performance that you’ll keep in a data warehouse or BI tool via Zendesk exports.

Important: Intercom’s value doesn’t depend on having 5+ years of tickets inside it. The system learns from your knowledge base, procedures, and recent patterns—so focus on clean, high-signal data.

2. Prepare your Zendesk exports

From Zendesk, export:

Users & organizations: Include identifiers you’ll also track in Intercom (email, external IDs, company domains, plan IDs).
Tickets & comments: At minimum: ticket ID, requester, assignee, status, created/updated dates, subject, channel, tags, key custom fields.
Help center content: Category/section/article structure, article titles, body HTML/Markdown, labels, language.

Clean before import:

Normalize field values (e.g., statuses, priorities, categories).
Remove stale or deprecated values you don’t want in the new system.
Decide on a consistent tag and category taxonomy going forward.

3. Import into Intercom

You have three main paths for importing:

CSV imports: For users, companies, and structured attributes. Ideal for most teams starting out.
APIs / Data connectors: If you already centralize customer data in your own backend or a CDP, connect that source-of-truth to Intercom first—so imports stay in sync and updates are automatic.
Targeted ticket import: Use APIs to sync open/high-priority tickets and map fields to Intercom tickets. Given Intercom is built for “day one” impact, I usually favor importing only:
- All open tickets.
- Recently solved tickets for top-tier accounts (e.g., last 60–90 days) where backstory matters.

Note: Keep Zendesk as read-only for a period after cutover, and export everything you might need into your data warehouse or storage, so you can answer audit questions later without keeping Zendesk live.

Migrating Macros and Automations

The heart of your migration is translating Zendesk macros/triggers/automations into Intercom macros + Workflows + Fin logic.

1. Audit your Zendesk macros

Group macros into:

Top 20–50 high-use macros: These almost always deserve a direct Intercom macro equivalent.
Obsolete or niche macros: Use the migration as a clean-up; don’t blindly replicate every macro.
Decision-heavy macros: Macros that combine replies and field updates, or rely on prior conditions, are often better expressed as Workflows or Fin paths.

For each macro, capture:

The reply text.
Any field updates (status, priority, assignment).
Tagging logic.
Required conditions (e.g., current status, requester type).

2. Rebuild macros in Intercom

In Intercom:

Create macros for:
- Standard replies agents should still send (e.g., troubleshooting steps, return policies).
- Internal-only “playbooks” for complex issues (these can be used by humans, while Fin learns from structured content).
Include:
- Dynamic content snippets where relevant (e.g., customer name, product name).
- Tagging or ticket updates when applied.

Tip: Use Fin and Copilot to reduce the number of macros over time—agents can ask Copilot to draft answers based on current content, instead of maintaining hundreds of static macros.

3. Translate triggers and automations into Workflows

Zendesk’s triggers and automations usually map to Intercom Workflows and rules. Start with the ones that materially affect speed, routing, or SLAs:

Common migrations:

Routing rules:
Zendesk: Trigger “if ticket_channel is email and subject contains ‘invoice’ then assign to Billing.”
Intercom: Workflow “New inbound email” → condition on subject/body/recipient → route to Billing team or assign a ticket + SLA.
Auto-acknowledgements:
Zendesk: Trigger on ticket creation to send “We’ve received your request” email.
Intercom: Workflow triggered by new conversation/ticket, sending an immediate, personalized Messenger or email reply with expected response time.
Status changes & follow-ups:
Zendesk: Automation to reopen tickets on customer reply or close after X days.
Intercom: Rules and Workflows that move tickets between states, reassign if customer re-engages, and notify owners.
Escalation & SLAs:
Zendesk: Automations based on time-to-first-reply and time-to-solve.
Intercom: SLAs and Workflows that:
- Set target first response and resolution times by queue or ticket type.
- Notify or reassign when SLAs are at risk.

Important: Don’t just copy your old triggers. Intercom’s one connected system (Helpdesk + Fin + Messenger) allows smarter flows—for example, Fin can attempt resolution first, then a Workflow escalates to humans only if needed.

4. Integrate Fin AI Agent into your flows

Instead of using triggers to “deflect” tickets like older bots, use Fin to resolve and route:

Train Fin on:
- Help Center content.
- Internal procedures and policies.
- Product FAQs and troubleshooting guides.
Test Fin in a staging-like environment before launch:
- Use Intercom’s testing tools to simulate queries and review answers.
- Define guardrails for sensitive topics (billing changes, PII updates, cancellations).
Deploy Fin across channels:
- Web Messenger and in-product.
- Email via Workflows (“If question matches X topics and is low-risk, let Fin answer, else route to team.”).
- Messaging channels (WhatsApp, Instagram, etc.) where appropriate.

Use Fin’s AI Insights weekly to see what it’s failing on, what it’s handing off, and which topics you need to cover better in your knowledge base or procedures.

Keeping Reporting Intact (and Making It Better)

You’re migrating systems, but your leadership still needs continuous views of volume, response times, and CSAT.

1. Preserve Zendesk historical reporting

Before decommissioning Zendesk:

Export:
- Ticket-level data with timestamps, channels, agents, SLAs, CSAT, tags.
- Any custom reports you rely on (by product area, region, segment).
Load into your BI or data warehouse and label it clearly as “Zendesk era.”
Define side-by-side dashboards:
- Pre-migration (Zendesk).
- Post-migration (Intercom).
- Overlap period where both systems may be live.

This gives you intact trendlines without forcing Intercom to be your single source of history from day one.

2. Configure Intercom reporting and dashboards

In Intercom, set up:

Volume & performance dashboards:
- Total conversations and tickets by channel (web, email, WhatsApp, Instagram, SMS).
- Median/average first-response and resolution times.
- Backlog and SLA performance by team or queue.
AI vs human performance:
- Fin’s resolution rate (Intercom customers see an average of 66%, improving ~1% per month).
- Copilot impact on agent throughput (customers see agents closing ~31% more conversations daily with Copilot testing).
Topic-based reporting:
- Which categories drive most volume and slowest resolution times.
- Which topics Fin handles well vs hands off.

Recreate your critical Zendesk views where possible, but go further—topic/channel insights plus AI performance will let you systematically reduce effort and improve outcomes.

3. Bridge the reporting gap during cutover

During the dual-run phase:

Tag or label interactions by system and channel (e.g., “ZD_email,” “ICM_messenger”) in your warehouse.
Set a clear “Intercom as system of record” date per channel; from then on, treat Zendesk data as historical only.
Communicate to leadership:
- When to expect data discontinuities (e.g., volume shift from Zendesk chat to Intercom Messenger).
- New KPIs enabled by Intercom (Fin resolution rate, self-serve engagement in Help Center, article attach rate).

Ideal Use Cases

Best for teams replacing Zendesk entirely: Because you can map macros, workflows, and SLAs into one connected Intercom system—so AI, Messenger, and Helpdesk all work together from day one.
Best for teams layering AI onto an existing helpdesk first: Because Fin can sit in front of Zendesk as the first line of support—so you can prove AI resolution and refine procedures before fully migrating the helpdesk.

Limitations & Considerations

Historic ticket parity:
Importing every historic Zendesk ticket into Intercom isn’t practical or necessary. Treat Zendesk exports + your data warehouse as your long-term archive, and import only high-value recent tickets into Intercom.
One-to-one automation mapping:
Not every Zendesk trigger or macro has a direct one-to-one equivalent. Take advantage of the migration to simplify and upgrade flows using Workflows and Fin—don’t recreate every edge-case rule just because it exists today.

Pricing & Plans

Intercom’s pricing depends on the mix of capabilities (Helpdesk, Fin AI Agent, Messenger, Help Center) and your volume/user counts. From a migration perspective, think in terms of which teams and channels you’re bringing over initially and how aggressively you plan to deploy AI.

Common patterns:

Core Support Suite: Best for support teams needing a fully featured Helpdesk, Inbox, Messenger, and Help Center—with optional Fin to start resolving a meaningful share of queries from day one.
AI-First Suite: Best for teams that want Fin as the front line across web, email, and messaging channels, with advanced automation (Workflows, Data connectors, Fin Tasks/Procedures) and deep reporting, and plan to migrate or consolidate legacy helpdesks over time.

For exact pricing, you’ll want to talk to Intercom sales or use the pricing page, as it depends on seats, volume, and AI usage.

Frequently Asked Questions

Do we need to migrate all historic Zendesk tickets into Intercom?

Short Answer: No—migrate only what you need operationally; archive the rest via exports.

Details:
For most teams, importing every historic Zendesk ticket into Intercom adds noise and complexity without improving outcomes. I recommend:

Importing all open tickets and recent high-value tickets (e.g., last 3–6 months) where context matters for ongoing relationships.
Importing users/companies and key attributes for routing and personalization.
Exporting all Zendesk history into your data warehouse or storage for compliance and long-term trend analysis.

Intercom’s effectiveness comes from current procedures, knowledge, and AI, not sheer ticket count.

How do we avoid breaking automation when we switch channels from Zendesk to Intercom?

Short Answer: Run a short dual period, rebuild critical flows as Intercom Workflows, then cut Zendesk triggers once Intercom is fully tested.

Details:
To avoid double replies or dropped conversations:

Rebuild and test key flows in Intercom:
- Routing, auto-acknowledgement, SLAs, escalation, and high-volume macros.
- Fin flows for common questions.
Run channels in parallel briefly:
- For example, move Messenger/web chat to Intercom first while keeping email in Zendesk.
- Use Intercom’s reporting to verify that volume and resolution patterns look healthy.
Switch MX records / channel connectors:
- Point support email and messaging channels (WhatsApp, Instagram, SMS) to Intercom.
Disable Zendesk triggers/automations for migrated channels:
- Keep Zendesk accessible as read-only or limited-use until you’re confident everything routes correctly.

This approach gives you a controlled cutover without disrupting customers or losing automation.

Summary

A successful Zendesk to Intercom migration isn’t just about data import—it’s about designing a modern support system where Fin resolves most queries, humans handle the complex ones from a shared Inbox, and you get clear reporting across both. Focus on:

Mapping core objects (tickets, users, organizations, macros, triggers) to Intercom primitives.
Importing only the data you need for day-one operations and reporting continuity.
Rebuilding your best automations as Intercom Workflows and macros, with Fin at the front line.
Preserving Zendesk history in your warehouse while building forward-looking dashboards in Intercom.

Done well, you’ll end up with faster responses, higher resolution rates, and a single system that gets smarter every week instead of a collection of disconnected tools.

Next Step

Get Started