Switching from Zendesk without losing your ticket history

Most people who think about leaving Zendesk stall on the same question: what happens to the history? Years of tickets hold every promise you've made to a customer, every workaround that worked, every "we said we'd fix this in March". Walking away from that is a real cost, and it's the reason plenty of teams keep paying for a helpdesk they've outgrown or never grew into.

The pricing complaints are well covered, including what the entry tiers actually leave out. This post is about the other half of switching: getting your data out of Zendesk, and what happens to it next.

Get your data out before you cancel

Zendesk can export your tickets, users, and organizations as files. Three things about that export catch people out, and each one is worse to discover late.

First, exports are off by default. The account owner has to contact Zendesk's support and ask for data exports to be enabled. It isn't a toggle in your settings, and it isn't instant: the export itself can take from a few minutes to a day or more, delivered as an emailed download link.

Second, not every Zendesk plan includes exports. Whether the option exists for you depends on which plan your account sits on. Zendesk's own export documentation lists what each plan allows.

Third, and this is the one that actually strands people: once your subscription lapses, there is no way back in. No login, no API, no support ticket that gets your data back. If you are leaving, request the export while the account is live, download the files, and keep them somewhere safe. Do this even if you haven't picked a destination yet. The files keep the option open; cancelling without them closes it.

Which export to request

Once exports are enabled, they live in Zendesk's Admin Center under Account, then Tools, then Reports, on the Export tab. You'll see three formats, and the choice matters more than it looks.

Ask for the full JSON export, and run it twice: once for tickets, once for users. The JSON export is the only one that carries complete conversations at any account size, and it's what a later import feeds on. The CSV export looks tempting because it opens in a spreadsheet, but it contains no ticket comments and no descriptions. As a report on your ticket metrics it's fine; as your history it's a list of subject lines. The XML export does include conversations but stops working at around two hundred thousand tickets, which is exactly when you'd need it most.

A detail worth knowing before you open the files: the JSON arrives as one object per line, not one big array. Some tools choke on that. You don't need to fix or even open it; an importer that understands Zendesk exports reads it as delivered.

How the export arrives

The export runs in the background and Zendesk emails you a download link when it's done. Small accounts take minutes; busy ones can take a day or more. The link fetches a zip that may hold several numbered files for a large account, and on very large accounts the export itself is broken into monthly chunks.

Download it as soon as the email lands. Zendesk only promises the link stays valid for a few days. If the email never arrives, go back to the export page: a "latest" link beside each format fetches the most recent file that was generated, which is usually the one you're waiting for.

Then check what you got. Open the zip, confirm there's a tickets file and a users file, and confirm the sizes look plausible for years of history. A 40 KB file does not hold 30,000 tickets. Finding a problem now costs an email to Zendesk support; finding it after cancelling costs the history.

What moving over actually looks like

AllMy Support imports a Zendesk account's history in one run: the tickets, the full conversations on them including internal notes, the contacts they belong to, and their attachments. There are two ways to feed it, and they end in the same place.

If your Zendesk is still live, you connect it and AllMy Support pulls your history over the API. No export request needed, and it works whatever plan you're on. A big account takes a while, sometimes hours; you can stop and resume without losing your place.

If you've already left, those export files you downloaded are enough on their own. Upload them and the same import runs from the files.

Either way, you see a preview of what's coming before anything is written, and you confirm how agents and custom fields map across. The import doesn't fire your automations and doesn't email your customers. And the detail that matters most in practice: every imported ticket keeps its Zendesk number on record, shown on the ticket and searchable. When a customer writes in about "ticket 14502", you find it.

Help-center articles move too, through a separate article import into the knowledge base, so your public documentation survives the switch alongside your inbox.

What doesn't come across

Two honest limits. Voice call recordings don't survive the trip; the written conversation on those tickets does. And Zendesk configuration, meaning macros, triggers, automations, and views, is not history and doesn't move. You rebuild the handful you actually use with saved replies and automations, which for most small teams takes an afternoon and drops half the cruft.

Agents who left your team years ago are handled sensibly: their tickets stay attributed to them, worked out from who handled what, without you inviting ghosts onto your plan.

The order of operations

If your Zendesk is live: start a free trial, connect the API, and run the import while both systems are up. Nothing about the import touches your Zendesk, so there's no burned bridge; you compare the result against the original while it still exists.

If you're on the way out: request the export first, download the files, then cancel. The import will be waiting whenever you are ready.

The import is part of the plan, not a paid migration service. The bulk import guide has the step-by-step and the full pitfall list, and the pricing page covers what the plan itself costs. Still weighing the move? How AllMy Support compares to Zendesk puts the two side by side. Your history took years to build. Leaving a helpdesk shouldn't mean leaving it behind.