Export guide · Checked against Zendesk documentation 2026-11-17
How to export all your tickets and data from Zendesk
Zendesk admins export tickets, users and organizations from Admin Center under Account > Tools > Reports, after the account owner asks Zendesk Customer Support to turn exports on. JSON exports include ticket comments, CSV exports cover ticket fields only, and XML is for accounts under 200,000 tickets. Admins on any plan can use the incremental export API.
Who can export from Zendesk
At the time of checking, Zendesk's built-in export tools are available on Suite Growth, Professional, Enterprise and Enterprise Plus, and on Support Professional and Enterprise. Zendesk says they are not available on Team plans, but customers on all plans can use the REST API.
Exports are off by default. The account owner has to contact Zendesk Customer Support, include the Zendesk Support subdomain and ask for data exports to be enabled. Once that is done, admins can export account data. Zendesk also lets you restrict which admins can export, or deactivate exports altogether.
The incremental export API endpoints for tickets, ticket events, users and organizations are listed as allowed for admins only.
How to export, step by step
Route 1 of 4
JSON export in Admin Center
Admins on eligible plans, after exports are enabled
- 01Confirm with Zendesk Customer Support that data exports are enabled for the account.
- 02In Admin Center, click Account in the sidebar, then select Tools > Reports.
- 03Click the Export tab if it is not already open.
- 04Under the JSON export, select a date range.
- 05Select tickets, users or organizations.
- 06Click Export.
- 07Open the email from Zendesk when the export is ready and download the zip file from the link.
Zendesk recommends the JSON export for accounts with more than 200,000 tickets. Accounts with more than one million tickets are downloaded in 31-day increments. If an export errors, adjust the date range and try again.
Route 2 of 4
CSV export of ticket fields
Admins on eligible plans, after exports are enabled
- 01In Admin Center, go to Account > Tools > Reports and open the Export tab.
- 02Under the CSV export, select a date range.
- 03Click Export.
- 04Download the zip file from the link Zendesk emails you.
Dates in the CSV are converted to the account's default time zone at the time of export.
Route 3 of 4
XML export
Admins on accounts with 200,000 tickets or fewer
- 01In Admin Center, go to Account > Tools > Reports and open the Export tab.
- 02Click request file next to the full XML export or the user XML export.
- 03Download the file from the link in the email Zendesk sends.
You cannot set a date range or pick a data type for XML. If the email does not arrive, click latest beside the export type on the Reports page to download the most recent file.
Route 4 of 4
Incremental export API
Admins, on any plan
- 01Call GET /api/v2/incremental/tickets/cursor with a start_time for the first request.
- 02Request the next page with the cursor returned in after_cursor until end_of_stream is true.
- 03Call GET /api/v2/incremental/ticket_events with include=comment_events to get the full comment objects for each ticket.
- 04Call GET /api/v2/incremental/users/cursor and GET /api/v2/incremental/organizations for people and organizations.
- 05Store the last cursor or end_time and use it to start the next run, so each run only returns what changed.
Without include=comment_events, a ticket event only tells you that a comment is present and whether it is public. It does not carry the comment text.
What comes out
Every UI export arrives as a zip file by email link. The JSON export is newline-delimited JSON, with one ticket, user or organization object per line, not a single JSON array. Files are named export_YYYY_MM_DD_uniqueID_X, and Zendesk says the trailing number does not indicate the order of the data, which is not guaranteed inside files either.
The CSV export is one row per ticket with fields such as ID, requester details, submitter, assignee, group, subject, tags, status, priority, channel, ticket type, timestamps, organization, satisfaction score, and reply, resolution and wait times in minutes. The full XML export bundles account settings, groups, organizations, tickets with comments, and users.
The API returns JSON pages of up to 1,000 items. Ticket events are a stream of changes, where each event contains the fields that were updated in that change, so a ticket's history is rebuilt by joining events on the ticket ID.
| In the export | What it contains |
|---|---|
| Tickets JSON (NDJSON) | One ticket object per line, including its comments unless the ticket is larger than 1 MB. |
| Users JSON (NDJSON) | One user object per line. |
| Organizations JSON (NDJSON) | One organization per line, including deleted organizations, which carry a deleted_at value. |
| Oversized tickets JSON | A separate file in the zip listing tickets over 1 MB whose comments were omitted, with an error message. |
| Tickets CSV | Ticket fields and metrics only. No comments, descriptions, deleted tickets, multi-line text, multi-select or custom date fields. |
| Full XML export | Account settings, groups, organizations, tickets with comments, and users including end users, agents and admins. |
| User XML export | Groups, organizations and users with tags, without custom user or organization fields. |
Before you rely on it
Limits and gotchas.
- The download link in the email is valid for at least three days, and processing can take from a few minutes to a day or more.
- XML exports have a maximum file size of 500 MB, roughly 200,000 tickets, and are not available for accounts with more than 200,000 tickets.
- The full XML export does not include custom ticket fields, metric sets or comment metadata.
- JSON and CSV date ranges use a system-generated timestamp that usually matches the most recent update, not the creation date, and items with a timestamp within 6 minutes of the request are excluded.
- CSV and JSON exports are not available in sandbox instances, and AI agent tickets cannot be exported with these tools.
- The incremental export endpoints allow up to 10 requests per minute and do not return data for the most recent minute.
- Secondary email addresses are not in the CSV. Zendesk points to the List Users API with include=identities for those.
Handle with care
Personal data inside a Zendesk export.
- Requester, submitter and assignee names and details on every ticket
- End user, agent and admin records in the users export
- Ticket subjects and comment text written by customers and agents
- Organization names tied to the people who raised tickets
- Tags and satisfaction scores linked to an identifiable requester
- Anything customers typed into a ticket, such as phone numbers, addresses or order details
An export is a copy outside the access controls of Zendesk. Store it encrypted, limit who can open it and delete working copies when you are done. The personal data scrubber removes common identifiers in your browser before a file is shared.
What the export can be worth
Outrich Data is a direct buyer of de-identified company data for AI training, from companies with 50 or more employees. We never connect to your Zendesk account: your team runs the export above and removes what is out of scope. Not every export qualifies, and a rights review comes before any offer.
Questions
Exporting from Zendesk: common questions.
Why can't I see the export option in Zendesk?
Does the Zendesk CSV export include ticket comments?
How do I export more than 200,000 Zendesk tickets?
How long is a Zendesk export link valid?
Sources
Steps were checked against Zendesk documentation on 2026-11-17. Vendors change menus, plans and limits, so confirm against the linked pages. Zendesk is a trademark of its owner. Outrich Data is not affiliated with Zendesk.
Find out if your data qualifies.
Eleven questions, about five minutes, no call required. You get an answer on screen and a written follow-up.