How to Migrate Away from Zendesk: A Step-by-Step Guide for Support Teams

Migrating away from Zendesk is a project, not a button press. Tickets, knowledge base articles, and customer data transfer through APIs and third-party tools. Macros, triggers, automations, SLA policies, and routing rules do not. They have to be rebuilt from scratch on whatever platform you choose.

That distinction, between records that move and logic that stays behind, is the single most important thing to understand before you commit engineering time and budget to a migration.

This guide covers the full process: confirming that migration is actually the right move, auditing your current setup, exporting your data, choosing where to go, executing the transition, and rebuilding what does not port automatically. It also includes a dedicated section on migrating to Intercom specifically, for teams that want AI-first customer service in a single platform.

Key Takeaways

• Not every Zendesk frustration requires a full migration. If your primary pain is AI performance, evaluate whether a different platform's AI resolves more before committing to a switch.
• Ticket data, customer records, and knowledge base articles can be exported. Macros, triggers, automations, and SLA policies cannot. Plan to rebuild those manually.
• Budget 60% of your migration effort for pre-transfer work: auditing data, mapping fields, cleaning records, and configuring the target platform.
• Run both platforms in parallel for two to four weeks before cutting over. Use a single channel first to validate.
• Third-party migration tools like Help Desk Migration handle bulk data transfers for roughly $100 per 1,000 records, saving significant engineering time over DIY API scripts.

Before You Migrate: Confirm the Platform Is Actually Your Problem

Teams leave Zendesk for four main reasons: escalating costs, underwhelming AI, configuration complexity, and limited modern channel support. Each of these has a different solution, and not all of them require a migration.

Escalating costs. Zendesk Suite plans run from $55 to $169 per agent per month on annual billing. Add-ons stack on top: Copilot at $50 per agent, Quality Assurance at $35 per agent, Workforce Management at another per-agent fee. A 15-agent team on Suite Professional with Copilot and QA can reach $36,000 per year before any AI resolution charges. If pricing is the primary issue, right-sizing your Zendesk plan (dropping unused features, converting light agents, renegotiating at renewal) can cut costs 20-40% with zero migration risk.

Underwhelming AI. Zendesk's AI agent capabilities arrived through the acquisition of Ultimate AI in April 2024 and Forethought in March 2026. The result is bolted-on rather than purpose-built. In independent head-to-head testing, Fin provides a better answer 80% of the time, handles 2x more complex queries, and achieves 96% accuracy on questions requiring multiple sources versus Zendesk's 78%. If AI resolution rates are the primary frustration, a platform migration may well be justified.

Configuration complexity. Zendesk's flexibility is a double-edged sword. Small teams without a dedicated admin often find themselves buried in configuration they cannot maintain. If this resonates, simpler platforms like Help Scout or Freshdesk may be the right target.

Channel gaps. Native support for Slack, Discord, and modern B2B messaging channels is limited or absent in Zendesk. If your customers are in Slack workspaces or community channels, you are likely stitching together workarounds that break regularly.

The honest test: if you migrated tomorrow and rebuilt every workflow identically on a new platform, would your problem be gone? If the answer is no, the platform is not the issue and migrating will not fix it.

Step 1: Audit Your Current Zendesk Setup

Before exporting anything, document what you have. This audit determines your migration scope, timeline, and cost.

Data inventory

Count the following:

• Tickets: Total volume, including closed tickets. This affects migration tool pricing and transfer time.
• Agents and admins: Number of seats, roles, and permission levels. Map these to the target platform's role structure.
• End users and organizations: Customer records, company data, and custom attributes.
• Knowledge base articles: Total count, number of languages, category/section hierarchy, and embedded media.
• Custom fields: Ticket fields, user fields, organization fields. Document field types (dropdown, text, checkbox) and values.
• Tags: Active tags used in routing, automation, and reporting.
• Macros: Saved replies your agents use daily. These will need to be recreated.
• Triggers and automations: Rules that fire on ticket creation, update, or time-based conditions. Document the logic, as these do not port.
• SLA policies: Response and resolution targets by priority, channel, or customer segment.
• Integrations: Connected apps, API connections, webhooks, and third-party tools.

Configuration audit

Document the business logic that lives inside Zendesk:

• Routing rules: How are conversations assigned to teams and agents?
• Escalation paths: What triggers a handoff from AI to human, or from Tier 1 to Tier 2?
• Business hours and schedules: Different hours for different teams or regions?
• Views and filters: How do agents organize their queues?
• Reporting: What dashboards, saved reports, and metrics does leadership track?

This documentation becomes your rebuild checklist on the new platform.

Step 2: Choose Your Migration Path

Two main options, each with different tradeoffs in cost, speed, and long-term value.

Option A: Full platform migration

Replace Zendesk entirely with a new helpdesk. This gives you the most control and eliminates the ongoing Zendesk contract, but requires the most effort.

Common targets include Intercom (for teams that want AI-first support and a modern helpdesk in one system), Freshdesk (for budget-conscious teams), Salesforce Service Cloud (for enterprises already on Salesforce), and HubSpot Service Hub (for teams on HubSpot CRM).

Timeline: 2-6 weeks for small to mid-market teams. Longer for enterprise setups with complex automation, multi-brand configurations, or hundreds of thousands of historical tickets.

Option B: Phased approach

Migrate in stages rather than all at once. A common pattern is to move the knowledge base and AI configuration first, run both platforms in parallel on a single channel, then complete the full cutover once confidence is established. This reduces risk by avoiding a hard cutover during a busy period.

Step 3: Export Your Data from Zendesk

Zendesk provides several export methods, each with different scope.

What exports cleanly

What does not export

Export methods

Full-account JSON export. Available under Admin Center > Account > Tools > Reports. Exports all tickets, users, and organizations as JSON. Good for archival purposes and bulk analysis.

Incremental Export API. Pages forward by timestamp, making it the right tool for multi-year archives with large ticket volumes. Use cursor-based pagination for reliable handling of datasets above 10,000 records.

Help Center API. Exports articles, sections, categories, and translations. Returns HTML content that you can import into most knowledge base tools.

CSV export. Available for users, organizations, and basic ticket data through Admin Center. Limited scope but useful for quick reference.

Third-party migration tools

For most teams, a dedicated migration service is faster and less risky than building custom API scripts.

Help Desk Migration (Relokia) is the most widely used service. It connects to both platforms via API, maps fields automatically, and handles bulk transfers. Pricing starts at approximately $100 per 1,000 records and scales non-linearly (10,000 records costs roughly $514). A free demo migrates 20 tickets plus 20 knowledge base articles so you can validate before committing. They support 90+ platforms and include features like delta migration (catching updates after initial transfer) and interval migration (pausing during business hours).

Import2 offers a cloud-based service with a free sample migration of up to 100 tickets. They have served 50,000+ customers since 2011.

Step 4: Prepare the Target Platform

Before transferring data, configure the destination. This is where 60% of the migration effort happens.

Pre-migration configuration checklist

• [ ] Create custom fields that match your Zendesk data types (dropdowns, text, checkboxes)
• [ ] Set up agent accounts with correct roles and permissions
• [ ] Configure team inboxes and assignment rules
• [ ] Rebuild SLA policies with response and resolution targets
• [ ] Set up business hours and schedules
• [ ] Create email forwarding rules or update DNS records
• [ ] Configure any integrations your team depends on (CRM, billing, product tools)
• [ ] Import or create your knowledge base content
• [ ] Set up saved replies, canned responses, or macros
• [ ] Build automation workflows for routing and assignment

Knowledge base migration

Knowledge base content is the foundation of AI agent performance. Clean, well-structured articles directly determine how well any AI agent can resolve customer queries.

Treat migration as an opportunity to audit and improve your content:

• Remove outdated articles that reference deprecated features or old policies
• Merge duplicate articles covering the same topic
• Restructure content so each article answers a single, clear question
• Add context to terse FAQ-style answers (a one-word "yes" or "no" response does not give an AI agent enough information to resolve a query)
• Replace internal jargon with language your customers use

This cleanup work compounds. Every article you improve makes your AI agent more effective and reduces the volume of queries reaching human agents.

Step 5: Run the Migration

Sequence

1. Run a sample migration. Transfer a small batch (20-100 tickets) and validate that fields map correctly, conversation threads are intact, and attachments transfer.
2. Fix mapping issues. Adjust field mappings, status translations, and priority levels based on the sample results.
3. Run the full migration. Execute the bulk transfer. Most tool-based migrations run over the API while both platforms stay live, so there is no hard outage.
4. Run a delta migration. After the bulk transfer, run a delta pass to catch any tickets created or updated during the main migration window.
5. Validate results. Spot-check 50-100 tickets across different categories. Verify conversation threads, attachments, custom field values, and agent assignments.

Cutover

• Update email forwarding rules so new inbound emails route to the new platform
• Update DNS records if you are changing support email domains
• Run both platforms in parallel for two to four weeks on a single channel
• Monitor the new platform for issues before expanding to all channels
• Communicate the timeline to your team clearly: when to stop working in Zendesk, when the new platform goes live

Step 6: Rebuild What Did Not Port

This is the step teams underestimate most. Rebuilding macros, triggers, automations, and routing rules takes real time, and it is also your opportunity to simplify.

Do not replicate everything. After years on Zendesk, most teams have accumulated triggers and automations that no longer serve a purpose. Review each rule and ask: does this still match how we actually work? Migration is the right time to trim the fat.

Prioritize by impact. Rebuild the workflows your team uses daily first: routing rules, assignment logic, and your most-used macros. Leave edge-case automations for later.

Test before going live. Run test conversations through every rebuilt workflow. Verify that routing, assignment, SLA tracking, and escalation all behave as expected.

If you are moving to a platform with AI agent capabilities, many of the workflows you are rebuilding may be unnecessary. An AI agent that resolves 70%+ of conversations reduces the volume of tickets that need complex routing, prioritization, and assignment logic. Focus your automation effort on the conversations that reach human agents.

Step 7: Train Your Team and Monitor Performance

The technical migration is only half the project. Your team needs time to learn the new platform.

• Schedule hands-on training sessions before cutover, not after
• Create a quick-reference guide covering the five actions your agents perform most often
• Assign a migration lead who is available to answer questions during the first two weeks
• Track response times, resolution rates, and CSAT closely during the first 30 days
• Hold a retrospective at 30 days to identify remaining friction points

Migrating from Zendesk to Intercom

For teams that want AI-first customer service and a modern helpdesk in one platform, Intercom is a common Zendesk migration target. Fin, Intercom's AI agent, averages a 76% resolution rate across 8,000+ businesses, handles complex multi-step queries through Procedures, and operates across voice, email, chat, WhatsApp, Slack, and 10+ channels. Unlike Zendesk's AI, which arrived through acquisitions and sits on top of the helpdesk, Fin is built into the platform from the ground up.

Here is what the migration process looks like end to end.

What transfers and what you rebuild

Transfers cleanly:

- Tickets, including conversation threads, internal notes, and attachments

- Customer and organization records with custom field values

- Knowledge base articles, categories, and section hierarchy

- Tags and ticket metadata

Requires rebuilding in Intercom:

- Macros become Saved Replies in Intercom

- Triggers and automations become Workflows in Intercom's visual workflow builder

- SLA policies are reconfigured under Intercom's SLA settings

- Views become Inbox views in Intercom

- Business hours and routing rules are rebuilt in Settings

The effort to rebuild logic is real, but Intercom's Workflows builder is visual and significantly more accessible than Zendesk's rules engine. Most teams find they can rebuild their core automation in a day or two.

Migration steps specific to Intercom

1. Set up your Intercom workspace. Create your account, configure team inboxes, and invite agents with the correct roles. Intercom uses a seat-based model with role types (inbox, lite, and collaborator seats) that map differently from Zendesk's agent/light agent structure. Map your Zendesk roles to Intercom equivalents before importing users.

2. Migrate knowledge base content. Export articles from Zendesk's Help Center API and import them into Intercom's Knowledge Hub. Intercom supports articles, internal notes, snippets, and external URLs as knowledge sources. If you are using Help Desk Migration (Relokia), they handle this transfer directly. Clean up content during this step: remove outdated articles, expand terse answers, and consolidate duplicates. Fin draws on this content to resolve queries, so quality here directly determines AI performance.

3. Configure Fin. Once your knowledge base is in Intercom, configure Fin:

- Enable Fin and point it at your knowledge sources

- Set Guidance rules for tone, policy boundaries, and escalation triggers

- Connect Data Connectors if Fin needs to pull live data from external systems (your CRM, billing platform, or ecommerce stack)

- Configure Procedures for complex multi-step workflows (returns, account changes, refund processing)

- Test using Fin's built-in Simulations before going live

4. Migrate tickets. Use Help Desk Migration or Import2 to transfer historical tickets. Both tools have native Zendesk-to-Intercom connectors. Run a sample of 20-100 tickets first, validate field mappings, then execute the full transfer. Intercom uses Conversations rather than Tickets as the primary record type; the migration tools handle this translation automatically.

5. Rebuild Workflows. Recreate your Zendesk triggers and automations as Intercom Workflows. Start with your highest-volume rules: assignment logic, SLA triggers, and escalation paths. Intercom's Workflows are built visually with a drag-and-drop editor, which most teams find faster to work with than Zendesk's text-based rules. This is also the moment to simplify: with Fin handling 70%+ of conversations autonomously, many routing rules become redundant.

6. Configure channels. Add each channel your team supports. Intercom handles email, live chat, WhatsApp, Instagram, Facebook, SMS, phone (via Fin Voice), Slack, and Discord from a single inbox. Update email forwarding rules to route inbound support emails to your Intercom address. If you are deploying the Messenger widget, add the Intercom snippet to your website or product.

7. Run parallel for two to four weeks. Redirect a single low-volume channel (typically email) to Intercom first. Monitor resolution rates, response times, and agent experience. Once stable, expand to all channels and stop routing new conversations to Zendesk.

Timeline expectations

The data transfer itself is usually the shortest part. Preparation, knowledge base cleanup, Workflow rebuilding, and parallel running account for the majority of the timeline.

Intercom's migration support

Intercom offers a Competitor Compete program for teams migrating from Zendesk, which includes free platform usage for the remainder of your Zendesk contract and migration assistance. Professional Services can also be engaged to handle configuration, Workflow setup, and Fin training for teams that want a managed migration rather than a self-serve one.

"Fin fundamentally changed our support strategy. It helped us scale instantly, resolve over 50% of conversations, and save more than 1,700 hours in the first month." - Isabel Larrow, Product Support Operations, Anthropic

Frequently Asked Questions

How long does it take to migrate away from Zendesk?

Timelines depend on data volume and complexity. Small teams with straightforward setups can complete a migration in 2-3 weeks. Mid-market teams with custom automations, multiple brands, and large ticket archives typically need 4-6 weeks. Enterprise migrations with complex integrations can take longer. The actual data transfer often completes within days. Preparation and testing take the majority of the time.

What data gets lost during a Zendesk migration?

Ticket records, customer data, and knowledge base articles transfer cleanly with proper tooling. What does not port: macros, triggers, automations, SLA policies, views, business hours, and routing rules. These are platform-specific configurations that must be rebuilt. Additionally, original Zendesk ticket IDs are replaced with new IDs on the target platform (store originals in a custom field for reference), and ticket metrics like first reply time and first resolution time do not import through standard APIs.

How much does a Zendesk migration cost?

Direct costs include migration tool fees (roughly $100 per 1,000 records for Help Desk Migration), the new platform subscription, and any professional services. Indirect costs include engineering time for API work, the effort to rebuild automations and macros, agent training, and a temporary productivity dip during transition. For a 10-agent team with 50,000 historical tickets, expect direct migration tool costs of roughly $500-$1,000, plus 2-4 weeks of part-time engineering and operations effort.

Should I migrate during peak season or wait?

Wait if possible. Migrations introduce temporary friction, and your team will be slower on a new platform for the first few weeks. Schedule migrations during your lowest-volume quarter. If a contract renewal or critical pain point forces the timeline, consider a phased approach: move knowledge base content and AI configuration first, then complete the full cutover once you have validated the new setup.

What is the difference between migrating to Intercom versus other Zendesk alternatives?

The primary difference is how AI is integrated. Intercom's Fin AI agent is built into the platform rather than bolted on, which means AI resolution, human agent workflows, knowledge management, and reporting all share the same data. Platforms like Freshdesk or Help Scout are solid helpdesks but rely on third-party or acquired AI. For teams where AI resolution rate is a primary reason for leaving Zendesk, Intercom's native integration matters.