Skip to content

Migrating from Zendesk to an AI-First Platform: A 2026 Checklist

A Zendesk exit checklist: inventory tickets, macros and channels, check export formats, rebuild what will not import, and test cutover and rollback.

Asad AliFounder & CEO
Updated
Reading time
15 min read

Moving off Zendesk is mostly an inventory and rebuild project. Zendesk lets eligible accounts export tickets, users and organizations as JSON, CSV or XML, and its APIs return help-center articles, macros and other configuration. Rules such as macros, triggers, automations, views and SLAs do not run in another product, so you rebuild the ones you still need by hand. This checklist covers what to inventory, how Zendesk's own exports work, what an AI-first tool such as Chatsy can and cannot import, and how to cut over one channel at a time with a rollback plan.

Disclosure: Chatsy publishes this guide and is one possible destination. The Zendesk export steps apply whichever product you move to. The Chatsy sections say what Chatsy imports today and what it does not.

How this guide was put together

This is desk research. On November 12, 2026 we read Zendesk's official help-center article on exporting ticket, user, or organization data and the developer references for incremental exports, Help Center articles and macros. Zendesk prices come from the Zendesk pricing page on the same date. Chatsy capabilities come from Chatsy's product and pricing page. We have not timed a migration for this article, so there are no duration, deflection or success-rate figures here. Test each step on your own account.

Decide the scope first

"Leaving Zendesk" can mean two different projects:

  1. Full replacement. Every channel, ticket workflow and help-center article moves to a new help desk. This needs a destination with ticketing, routing, SLAs and the channels you use today.
  2. AI front door, Zendesk stays. You add an AI agent to your website or email first, and keep Zendesk for ticketing until the new setup proves itself.

Chatsy fits the second project better than the first. It offers an AI agent trained on your content, live chat handoff, a forwarding-based email mailbox with numbered tickets, and a help center on paid plans. It does not offer Zendesk's routing rules, SLAs, phone, social or messaging channels, or ticket-history import. If you need full replacement, pick a full help desk as the destination. Our Zendesk review and Zendesk alternative page can help with that shortlist.

Step 1: Inventory what you have in Zendesk

List every item, decide whether it still matters, and record how you will move or replace it.

ItemWhere it lives in ZendeskHow to get it outWhat usually happens to it
Tickets and commentsSupportAdmin Center data export or incremental export APIArchive. Most tools do not import history as live tickets
Users and organizationsSupportAdmin Center export or APIRe-create only if the new tool needs customer records
Help-center articles, sections, categoriesGuideHelp Center API (GET /api/v2/help_center/articles)Re-host or re-create, then review for accuracy
Article images and attachmentsGuideCheck article bodies for Zendesk-hosted filesDownload and keep your own copies before you cancel
MacrosSupportMacros API (GET /api/v2/macros)Rebuild the ones still in use as saved replies
Triggers, automations, viewsSupportTicketing API (JSON)Rebuild by hand or retire
SLAs and routing rulesAdmin CenterDocument manuallyRebuild in a help desk that supports them
Custom ticket and user fieldsAdmin CenterTicketing APIMap field by field or retire
Channels: email, chat, messaging, phone, socialAdmin CenterDocument addresses, numbers and accountsRepoint one channel at a time
Marketplace apps and integrationsAdmin CenterDocument what each sends and receivesReplace, rebuild or drop

Two questions trim the list quickly:

  • Which macros are still used? The Macros API can sideload usage counts (include=usage_7d or usage_30d). Zendesk's docs say these sideloads need the Support Professional or Suite Growth plan or above.
  • Which rules still fire? Review active triggers and automations with the people who own them. Retire anything nobody can explain.

Step 2: Export from Zendesk (vendor steps)

These steps come from Zendesk's own documentation as of November 12, 2026. Check the linked pages again before you run them, because plan names and limits change.

Admin Center data export (tickets, users, organizations).

  • Formats: JSON, CSV or XML. Zendesk recommends JSON for accounts with more than 200,000 tickets.
  • Plan availability: the article says the export tools "are not available on Team plans", and support-only accounts need Professional or Enterprise. Accounts without the export tools can still use the REST API.
  • Exports are disabled by default. The account owner asks Zendesk Customer Support to turn them on.
  • Size limits: XML exports max out at 500 MB (about 200,000 tickets). Accounts above one million tickets download JSON in 31-day increments. If a single ticket holds more than 1 MB of data, its comments are left out of the JSON file. CSV exports never include ticket comments or descriptions.
  • Delivery: Zendesk emails a download link to a zip file. The link is valid for at least three days, so download and store it promptly.

Incremental export API (large archives).

  • Up to 1,000 results per page.
  • "You can make up to 10 requests per minute to these endpoints." The users cursor export has its own limit (20 requests per minute, or 60 with the High Volume API add-on).
  • Zendesk encourages cursor-based pagination for consistent performance.
  • The incremental ticket export returns ticket records, not comment threads. The ticket events export includes full comment text only with the comment_events sideload; without it, each comment appears only as true/false flags.

At 1,000 tickets per page and 10 requests per minute, the ticket list alone for 100,000 tickets takes at least 100 requests, or about 10 minutes of rate-limited calls. Comment exports add more requests on top. Plan for a script that can resume after errors.

Help-center articles. List articles with GET /api/v2/help_center/articles, using cursor pagination. Each article includes its HTML body, section_id, locale and user_segment_id (who can see it). Export sections and categories too, so you can rebuild the structure, and export each brand's help center if you run more than one.

Step 3: Check what the destination can import (Chatsy)

This is where migrations go wrong: a vendor's "import" can mean very different things. Here is what Chatsy accepts today.

Zendesk dataChatsy import todayWhat to do instead
Public help-center articlesNo Zendesk importer. Chatsy can read public web pages: one page, a list of up to 500 links, or a whole-site crawl (Hobby and above)Crawl the public help-center URLs, or upload exported article HTML as files
Exported filesUploads of TXT, HTML, PDF, DOC, DOCX, MD or CSV, up to 25 MB eachUpload cleaned article exports and policy documents
Articles you want to host on ChatsyChatsy help center (Hobby and above), then "Import help articles" into the agentRe-create or paste the articles you keep, then import them as knowledge
Short answers from macrosNo macro importRebuild key macros as saved replies, or add them as written question-and-answer sources
Ticket historyNo ticket or conversation importKeep it in Zendesk or in your archived export
Users and organizationsNo customer-record importKeep them in Zendesk, your CRM or the export
Triggers, automations, views, SLAs, routingNo equivalent featuresKeep them in a help desk that supports them, or retire them
Zendesk account connectionNo working connection today: the dashboard does not offer Zendesk setup, and agent execution through Zendesk templates is unavailable. There are no routing rules, automatic tagging, field mapping or two-way reply syncDo not plan workflows that depend on Chatsy acting in Zendesk

What Chatsy does provide once content is in place:

  • An AI agent that answers from your sources, installed with one script tag before </body>. See train an AI agent.
  • Live chat handoff on Hobby and above: the agent escalates to a human queue, and teammates claim, release, resolve or hand back to the bot. See human handoff.
  • An email mailbox on Hobby and above. You verify your support address, forward it to a Chatsy address, and replies go out from Chatsy with numbered tickets, statuses, priorities, assignees, tags and saved replies. See connect your support email.
  • A public help center on Hobby and above. See publish a knowledge base.

Do not assume parity with Zendesk's inbox, history, automation or reporting. Chatsy's analytics cover conversations, messages, first-reply time, top questions, helpful ratings, handoff rate and knowledge gaps. They do not include CSAT, SLA or agent performance reports.

Before you move any customer data, agree on what is allowed to move.

  • Minimize. Train the AI agent on help articles and policies, not on raw ticket exports. Ticket text contains names, emails, order details and sometimes payment or health data.
  • Check your privacy notice and contracts. Moving customer data to a new processor may require notice to customers or updates to your data processing agreements.
  • Check the destination's security scope. Chatsy encrypts integration credentials with AES-256-GCM. It does not offer SOC 2, a HIPAA BAA or SSO, publishes no named subprocessor list, and its dashboard has no complete account export or self-serve account deletion. If you handle regulated data, confirm requirements with Chatsy before you move anything.
  • Decide where history lives. If your retention policy says to keep tickets for a set period, keep them in Zendesk or in an archive you control, not in a tool that cannot import them.

Step 5: Test with real questions before any cutover

Pull a sample of real customer questions from recent tickets and remove personal details. Include easy questions, policy questions and the awkward edge cases your team knows about.

  1. Add your cleaned help-center content to the new agent.
  2. Ask each sample question in the private preview and record whether the answer was correct, partly correct or wrong.
  3. Fix gaps by editing the source content, not by adding one-off answers for every case.
  4. Re-run the sample after each content change.
  5. Check the "Questions it struggled with" list and the knowledge-gaps view for patterns.

There is no standard pass mark. Decide in advance what accuracy and handoff behavior your team will accept on each channel.

Step 6: Check the handoff path

An AI agent is only safe to launch if the hard cases reach a person.

  • Who sees escalations? In Chatsy, escalated chats go to the live chat queue whether or not anyone is online. There is no staff presence status.
  • How are people alerted? Escalation alerts can be posted to a connected Slack workspace (outbound alerts only). Chatsy does not email staff on escalation, so connect Slack or keep someone watching the dashboard.
  • What happens out of hours? Visitors can leave an email for follow-up. The request goes to the chatbot owner's email address.
  • Can customers still create tickets? With the mailbox on, the agent gets a "Create Support Ticket" tool. Test that the ticket arrives in the right mailbox.

Step 7: Cut over one channel at a time, with rollback

Start with the lowest-risk channel, usually the website widget, and keep Zendesk handling everything else.

ChannelCutover stepRollback step
Website chatReplace the Zendesk widget snippet with the Chatsy script on a few pages, then site-wideRestore the Zendesk snippet
Support emailPoint your support address's forwarding to the Chatsy mailbox after verificationPoint forwarding back to Zendesk
Help centerPublish the new help center and redirect old article URLs where your domain setup allows itKeep the Zendesk help center live until redirects are confirmed
Phone, social, messagingChatsy does not support these channelsKeep them in Zendesk or move them to a help desk that supports them

Document every DNS, forwarding and snippet change so anyone on the team can reverse it. Do not cancel Zendesk on launch day. Customers will keep replying to old ticket threads, and you will find edge cases after the first weeks.

Step 8: Keep access to history

Choose one of these before you cancel:

  • Keep a reduced Zendesk subscription for read access during your retention period. Check Zendesk's current plans for the cheapest option that still includes what you need.
  • Archive the exports. Store the Admin Center export files and API dumps somewhere access-controlled, with a note of what each file contains and the date range it covers.
  • Test the archive. Pick a few old tickets and confirm you can find them, including comments, before you close the account.

What you pay while both systems run

During a parallel run you pay for both tools, so plan the overlap. Zendesk's pricing page lists, per agent per month: Support Team $19 billed yearly or $25 monthly, Suite Team $55 or $69, Suite Professional $115 or $149, with Enterprise quoted by sales. Zendesk AI agents use automated resolutions: 5 per agent per month on Support Team and Suite Team, 10 on Suite Professional, then $1.50 each committed or $2.00 pay-as-you-go. See the full Zendesk pricing breakdown.

Chatsy plans are flat monthly prices with a fixed number of seats: Hobby $40 (1 seat), Standard $150 (3 seats), Pro $500 (5 seats), annual equal to ten monthly payments. AI usage is counted in credits per AI response, 1 to 30 credits depending on the model. A credit is spent per reply, not per resolution, so do not compare it one-to-one with a Zendesk automated resolution.

Example overlap for a five-person team, both billed monthly:

ItemUnitCalculationMonthly cost
Zendesk Suite Professional5 agent seats5 × $149$745
Zendesk AI agents above allowanceAutomated resolutionsAllowance 5 × 10 = 50, then $2.00 each pay-as-you-goDepends on volume
Chatsy Pro5 seats, 15,000 creditsFlat$500
Chatsy AI repliesCredits per replyUp to 14,999 replies on a 1-credit model, or 499 on a 30-credit modelIncluded up to the allowance

When not to migrate away from Zendesk

Stay on Zendesk, or move only to another full help desk, if any of these apply:

  • You depend on Zendesk custom objects for data modelling.
  • You run a multi-brand setup with shared agents and brand-specific routing.
  • You have contractual SLAs that need Zendesk's policy structure.
  • Phone (Zendesk Talk), social or messaging channels are core to your support.
  • You use workforce management or quality assurance tools inside Zendesk.
  • Agents need full ticket history inside the tool they answer from.

When Chatsy is not the right destination

  • You need ticket routing, SLAs, views or automations like Zendesk's.
  • You need phone, WhatsApp, social or SMS channels.
  • You need more than 10 seats, SSO, SOC 2 or a HIPAA BAA.
  • You want the AI agent to create or update Zendesk tickets. Chatsy has no working Zendesk connection today.
  • You need CRM integrations. HubSpot and Salesforce are planned, not available.

Frequently asked questions

How long does a Zendesk migration take?

It depends on the number of channels, the amount of history you must keep and how many rules you rebuild. A single-channel AI front door with a clean help center is a much smaller project than a full multi-brand replacement. Build your timeline from your Step 1 inventory rather than from a generic estimate.

Can I export everything from Zendesk?

You can export tickets, users and organizations through the Admin Center export on eligible plans, or through the REST API where the export tools are not available. Help-center articles and macros come out through the API. Triggers, automations, views and SLAs come out as configuration data that no other product can run, so they must be rebuilt.

Can Chatsy import my Zendesk tickets or macros?

No. Chatsy has no ticket, conversation, macro or trigger import. It learns from web pages, uploaded files, written answers and Chatsy help-center articles. Keep ticket history in Zendesk or in your archived export.

Can I keep Zendesk and add Chatsy?

Yes. You can put the Chatsy widget on your website and keep Zendesk for email and other channels. Escalated chats are handled in Chatsy's live chat inbox. Chatsy cannot create or update Zendesk tickets today, because it has no working Zendesk connection.

Should I train the AI on old tickets?

Be careful. Raw tickets contain personal data and outdated answers. Start from reviewed help articles and policies, and use anonymized ticket questions only as a test set.

Want a place to evaluate without a sales call? Start with Chatsy. The Free plan (40 credits, one agent) is enough to test answers from a sample of your content. Live chat handoff, the email mailbox and the help center need Hobby or above. Current prices and limits are on the pricing page. Keep the existing support path in place until the new workflow passes your checks.

All articles
  • Comparisons

    Migrating from Intercom to an AI-First Platform: A 2026 Checklist

    Plan an Intercom exit: inventory each export format, rebuild workflows by hand, test AI handoff in parallel and keep a read-only archive before you cancel.

    May 16, 2026 · 16 min read

  • Comparisons

    Chatsy vs Fin AI (2026): Pricing, Deployment and Limits

    Fin bills $0.99 per outcome on Intercom or on your current help desk, while Chatsy bills credits per AI reply. See the cost math for 3- and 5-seat teams.

    May 20, 2026 · 14 min read

Build an agent from your support content

Add approved help content, test its answers, and decide when a person takes over.

No credit card required