How to Export Your Data from Zendesk (Step by Step)

This guide walks through every method, in plain order, with the exact navigation paths, file formats, plan requirements, and the gotchas that trip people up. Everything below is verified against Zendesk's own documentation as of June 2026 — but Zendesk revises its UI and plan tiers periodically, so confirm the labels in your own account before you rely on them.

First, pick the right export method

Five methods, five jobs. Here's the quick map so you can jump to the one you need:

The big one — the export most people mean by "Zendesk account export" — is Method 1. Start there if you want everything.

Method 1 — Full account data export (tickets, users, organizations)

This is the heavyweight: a complete dump of your account's ticket, user, and organization data. It's how you take a full backup of your Zendesk data, hand records to a new platform during a migration, or pull a historical archive for compliance.

Where it lives and how to run it

The path, per Zendesk's data export documentation:

1. In Admin Center, click Account in the sidebar.
2. Select Tools → Reports.
3. Click the Export tab (some accounts show export options directly; older layouts use a separate tab).
4. Choose your format — CSV, XML, or JSON.
5. For a JSON export, pick a date range and the object type (tickets, users, or organizations), then click Export.
6. Wait. The export is generated asynchronously — Zendesk emails you a download link when it's ready, and that link stays valid for at least three days.

A genuine first-hand note on screenshots: on our test Zendesk instance, the dedicated Account → Tools → Reports → Export page isn't provisioned (data export is off by default and the Export tab doesn't appear until Zendesk enables it — more on that below), so the steps above are described accurately from Zendesk's documentation rather than staged. In Zendesk, the data export lives at Admin Center → Account → Tools → Reports → Export — the Account section where you generate full XML, CSV, or JSON exports of your tickets, users, and organizations.

The three formats — and what each leaves out

The format you choose changes what you get, not just the file extension:

• CSV — ticket data in a clean, spreadsheet-friendly table. The catch most people miss: multi-line text fields, multi-select fields, and custom date fields are excluded from CSV exports. They are included in JSON and XML. CSV is great for a quick analysis in Excel or a BI tool; it's a poor choice for a faithful, complete backup.
• XML — a fuller export including tickets, users, and organizations. Note the ceiling: an XML export has a maximum file size of 500MB, which works out to roughly 200,000 tickets. Larger than that and you'll want JSON.
• JSON — the most complete option, including full comment history alongside tickets, users, and organizations. Zendesk delivers it as NDJSON (newline-delimited JSON) so systems can stream one record at a time, and it's the recommended format for accounts with more than 200,000 tickets. Accounts over one million tickets are downloaded in 31-day increments.

Rule of thumb: CSV for a quick look, JSON for a real backup or migration, XML only if a legacy system on the receiving end demands it.

Plan gating (read this before you go looking)

This is where people get stuck. Two gates stand between you and the Export tab:

1. It's disabled by default. To protect account data, Zendesk turns these export tools off out of the box. The account owner must contact Zendesk Customer Support to enable data export — there's no self-serve toggle. If you open Account → Tools → Reports and see no Export tab, this is almost always why.
2. It's plan-gated. Per the availability box on Zendesk's export article, the export tools are available on Suite Growth, Professional, Enterprise, and Enterprise Plus, and on Support Professional and Enterprise. They are not available on Team plans — Team customers must use the API instead (Method 4).

One honesty flag worth your attention: you'll see older guides (and Zendesk's own legacy 2019-era article) claim the full XML/JSON export is Enterprise-only, or that only CSV is available below Enterprise. The current official article gates all three formats together at Suite Growth / Support Professional and up — the tiering appears to have moved down over time. Because plan packaging shifts, verify the exact entitlement on your own plan before you promise anyone a JSON backup.

Finally, role matters: you must be an administrator (or a custom agent role granted export permission) to run an account export.

Method 2 — Export a view to CSV

Sometimes you don't want the whole account — you want these tickets: everything in "Solved last week" or "Escalated — Tier 2." For that, export a view to CSV:

1. In Support, click Views in the sidebar.
2. Click the view's name to open it.
3. Click Export CSV in the upper right — or, depending on the view, Actions → Export as CSV.
4. Zendesk emails you the file when it's ready.

The CSV contains a row per ticket with that view's ticket metadata. Two limits to keep in mind:

• Large views can fail. Zendesk's doc warns that "larger views might fail to export, even though they display correctly in the Support console," and recommends narrowing the view (tighter date range, fewer columns) or using the Views API. The widely community-reported practical ceiling is around 1,000 tickets per export — treat that as a community figure, not an official published cap, and split big views by date range to stay under it.
• It's metadata, not the conversation. A view CSV gives you ticket fields — subject, status, assignee, dates, tags — not the comment thread or attachments. If you need the full conversation, that's a JSON account export (Method 1) or the API.

For exporting a hand-picked subset of tickets, Zendesk's guidance is the same: build a view that filters to exactly those tickets, then export it — there's no "select these 12 rows and export" button.

Method 3 — Export a report or dashboard from Explore

If the data you want already lives in a chart — ticket volume by channel, CSAT by group, resolution time trends — don't re-export raw tickets. Export it straight out of Zendesk Explore, where you built the report:

1. Open the report in Explore.
2. Click the dropdown arrow next to Save, then Export.
3. Choose a format: CSV, Excel, Image, or PDF.

A few format specifics from Zendesk's Explore export docs:

• CSV exports the underlying data only — any visual formatting is dropped.
• Excel preserves the report's formatting but is capped at 50,000 rows and 16,000 columns. Export a whole dashboard tab and each report lands on its own sheet in the workbook.
• PDF / Image are for sharing a snapshot; with PDF you can pick the quality and size.
• Filters aren't included in an export. If you need a filtered view captured, use your browser's print-to-PDF on the report instead.

Bumping the 50,000-row Excel ceiling? Use an Explore dataset export, which produces CSV files without that row limit and is built for feeding third-party BI tools.

Method 4 — API and incremental exports (for scale and automation)

When you need exports that are large, recurring, or automated — a nightly sync into a warehouse, a feed into Power BI — the UI exports stop being the right tool. Use the Zendesk REST API, which (notably) is available on every plan, including Team.

For ongoing pulls, Zendesk recommends the Incremental Exports endpoint. You pass a start_time and get back only what changed since then, so you're not re-downloading your entire history every run:

GET /api/v2/incremental/tickets.json?start_time=1332034771

We won't go deep on implementation here — it's a developer task — but the takeaway is simple: if you're on Team (no UI export), or you need exports on a schedule, the incremental API is the answer rather than clicking Export by hand every morning.

Method 5 — Exporting (or deleting) a single user's data

A GDPR or DSAR (data subject access) request usually isn't about your whole account — it's about one person. Zendesk handles this separately from the bulk tools:

• Export one user's data. You can export an individual end user's data to JSON, either through the agent interface or the Users API for a portability request, per Zendesk's privacy and data protection guidance. The JSON can be handed over or imported elsewhere.
• Delete one user's data. The flip side of a "right to be forgotten" request is forgetting a user in Zendesk: a user must be soft-deleted first, then permanently deleted. At scale, the API's DELETE /api/v2/users/destroy_many.json?ids={user_ids} accepts up to 100 user IDs at a time.

Don't reach for a full account export to satisfy a single-user request — it's slower, over-collects data, and creates its own privacy headache.

Retention, timing, and the gotchas that bite

A consolidated list of what actually trips teams up:

• Export is off until you ask. The single most common "where's the export option?" cause: it's disabled by default and only the account owner can have Customer Support switch it on. Sort this before a deadline, not during one.
• Exports are asynchronous. Account and view exports aren't instant — Zendesk generates them in the background and emails a link. For the account export, that link is valid at least three days, so download promptly.
• CSV silently drops fields. Multi-line, multi-select, and custom date fields don't make it into a CSV account export. If those matter, use JSON or XML.
• View exports cap out. Large views may fail or truncate (community-reported ~1,000 tickets). Split by date range, or use the API.
• Excel report exports cap at 50,000 rows. Use an Explore dataset export for more.
• Plan and role gate everything. No Team-plan UI export; admin (or export-permission) role required. Confirm your tier — packaging changes.
• Big accounts chunk automatically. Over ~200k tickets, prefer JSON; over a million, exports arrive in 31-day increments.

Where AI fits in

Here's an angle worth naming, because it's the reason a lot of teams export tickets in the first place: they want to learn from their support history. They pull a year of resolved tickets into a spreadsheet to find the repeat questions, the patterns, the answers worth turning into macros or help-center articles. That's slow, manual data-mining — and the export is stale the moment it lands.

That history — your resolved tickets, your knowledge base, your past replies — is exactly the data an AI agent learns from to answer future tickets. That's the layer Macha adds. Macha isn't a help desk and it isn't a Zendesk replacement; it's an AI agent layer that runs on top of your existing Zendesk. Instead of you exporting ticket history to figure out what customers keep asking, Macha reads your Zendesk knowledge and past conversations directly and uses them to resolve incoming tickets — drafting answers, tagging, routing, and escalating with full context when it isn't confident.

The honest framing: Macha doesn't replace your export workflow for backups, migrations, or compliance — you'll still use the methods above for those. What it removes is the manual mining of exports to understand and answer your volume. On cost, Macha bills per AI action — each automated step it takes, like drafting a reply, tagging, or routing — not per resolved ticket, because most automation is work done along the way, not a tidy "resolution." If a meaningful slice of your tickets are repeat questions your existing knowledge could answer, that's the work it takes off your queue. You can try it free — 7-day free trial, no credit card required.

Frequently asked questions

Where is the data export option in Zendesk? Admin Center → Account → Tools → Reports → Export tab. If you don't see the Export tab, data export almost certainly isn't enabled yet — it's off by default, and only the account owner can ask Zendesk Customer Support to turn it on. It's also unavailable on Team plans (use the API instead).

How do I export Zendesk tickets to CSV? Two ways. For a filtered slice: Support → Views, open the view, and click Export CSV. For your whole account: Admin Center → Account → Tools → Reports → Export, choose CSV. Remember CSV omits multi-line, multi-select, and custom date fields — use JSON or XML if you need those.

What's the difference between CSV, XML, and JSON exports? CSV is clean ticket metadata for spreadsheets but drops several field types. XML is fuller (tickets, users, organizations) but caps at 500MB / ~200,000 tickets. JSON is the most complete — it includes full comment history, streams as NDJSON, and is recommended for accounts over 200,000 tickets. Use JSON for a true backup or migration.

Which plans can export data from Zendesk? The UI export tools are available on Suite Growth, Professional, Enterprise, and Enterprise Plus, and on Support Professional and Enterprise — not on Team. Every plan, including Team, can export via the REST API. Plan packaging changes over time, so verify on your account.

How do I back up my entire Zendesk account? Run a full account export in JSON (Admin Center → Account → Tools → Reports → Export → JSON) for the most complete copy, including comment history. Have the account owner enable export first if needed, and use the incremental API if you want recurring, automated backups.

How long does a Zendesk export take, and how long is the link valid? Exports are generated asynchronously and emailed to you when ready — timing scales with account size. The account-export download link is valid for at least three days, so grab it promptly.

How do I export one customer's data for a GDPR request? Export that single end user's data to JSON via the agent interface or the Users API — don't run a full account export for one person. To delete their data, soft-delete then permanently delete the user (or use the API's destroy_many endpoint for up to 100 users at once).

The bottom line

There's no single "export" in Zendesk — there are five, and picking the right one is the whole game. For a complete backup or migration, run the full account export (Admin Center → Account → Tools → Reports → Export) and choose JSON for the most faithful copy — just remember it's off by default (the account owner enables it), plan-gated (Suite Growth / Support Professional and up; Team uses the API), and delivered async via an emailed link. For a quick slice of tickets, export a view to CSV; for an existing chart, export from Explore; for scale or automation, the incremental API; and for one person's data, the single-user JSON export. Match the method to the job and you'll get the data you actually need on the first try. For more on how the underlying records are structured, see our Zendesk ticketing system explained guide.

Export paths and limits verified against Zendesk's official documentation, June 2026. Zendesk updates its product and plan packaging periodically — confirm labels and entitlements in your own account before relying on them.