How to Export Tickets from Zendesk (2026 Guide)
Zendesk export tickets guide: CSV, XML, JSON and API methods, what each misses, the API token to OAuth change and what to delete first. Read the guide.
Published Updated 11 min read

On this page
- New in 2026: Zendesk is retiring API tokens
- Which Zendesk export option should you use?
- Method 1: export a view to CSV
- Method 2: account CSV export
- Method 3: XML export
- Method 4: JSON export
- Method 5: incremental export API (all tickets, any plan)
- Pre-export checklist
- What happens to archived tickets after 120 days?
- Delete, keep or leave behind
- How does Zendesk deletion actually work?
- Zendesk API rate limits that set your timeline
- Next steps by destination
- How MigrateX does this
- Zendesk ticket export FAQ
- Changelog
To export tickets from Zendesk, you have five routes: a view exported to CSV, the account-level CSV, XML or JSON export in Admin Center, or the incremental export API. Only the JSON export and the API carry ticket comments, and only the API works on every plan. If you are exporting to migrate, the API is the route that gets everything: comments, archived tickets, attachments and custom fields.
Below: each method and its gaps, the move from API tokens to OAuth, what to delete first, and the rate-limit math. For teams leaving Zendesk and MSPs scoping an exit.
New in 2026: Zendesk is retiring API tokens
Any API-based export now needs OAuth. Zendesk is phasing out API tokens in three steps (Zendesk OAuth migration guide, as of 4 Nov 2026):
| Date | What happens |
|---|---|
| 28 Jul 2026 | Tokens unused for 30 days are deactivated, then deleted after 60 more days unused. New accounts created from this date can't create or use API tokens. |
| 27 Oct 2026 | Existing accounts can no longer create new API tokens. Active tokens keep working. |
| 30 Apr 2027 | All remaining API tokens are permanently deactivated. Requests using them fail. |
Zendesk recommends the authorization code flow, with client credentials only when browser approval isn't possible. Third-party apps "must not use a customer's API credentials, including API tokens", and apps that don't move to OAuth stop working.
Which Zendesk export option should you use?
Five methods, five different gaps.
| Method | Plans | Comments? | Custom ticket fields? | Main limits |
|---|---|---|---|---|
| View export to CSV | All plans, Team included | No | Only the view's columns | No archived tickets; filtered views can't export; large views may fail |
| Account CSV export | Suite Growth+, Support Professional+; off by default | No | Partly: multi-line, multi-select and date fields excluded | No comments, descriptions or deleted tickets |
| XML export | Same as CSV | Yes (full XML) | No | 500 MB, about 200,000 tickets; unavailable above that |
| JSON export | Same as CSV | Yes, unless a ticket is over 1 MB | Yes | 31-day chunks above 1 million tickets |
| Incremental export API | All plans | Via ticket events or the comments endpoint | Yes | 10 requests/min, up to 1,000 tickets per page |
Sources: Zendesk data export article, view export article and incremental exports docs, as of 4 Nov 2026. On Team, the API is the only full export. AI agent tickets can't be exported by any Admin Center method.
Method 1: export a view to CSV
Fast for a spreadsheet list; not a migration export.
Steps. In Support, click Views, open the view, then Export CSV or Actions > Export as CSV. Zendesk emails a download link.
What it contains. Zendesk says it "exports only the ticket details displayed within the view itself", not comments (Zendesk help, as of 4 Nov 2026).
Limits. Views don't list archived tickets, so most tickets closed more than 120 days ago are missing. Only non-filtered views can be exported (Zendesk help, as of 4 Nov 2026).
Troubleshooting. No Export button means your role lacks export permission. If the email never arrives, Zendesk says larger views "might fail to export"; narrow the view or use the Views API.
Method 2: account CSV export
Every ticket's fields in one file, no conversation.
Steps. The account owner asks Zendesk Customer Support to turn exports on (they are off by default). Then go to Admin Center > Account > Tools > Reports, choose CSV and wait for the email.
What it contains. 40 columns, including ID, requester, assignee, group, subject, tags, status, priority, channel (Via), created, updated and solved dates, reply and resolution times, and satisfaction score.
Limits. No deleted tickets, comments or descriptions. "Multi-line text and multi-select fields, as well as custom date fields, are excluded from CSV reports." Dates use the account time zone, so they won't match the UTC dates in a JSON export.
Troubleshooting. The link lasts at least three days; "latest" re-downloads the last report, which may be stale.
Method 3: XML export
Full XML (same path as CSV) bundles settings, groups, organizations, users and tickets with comments. It caps at 500 MB, about 200,000 tickets; above that you see "Full XML export is no longer supported." It "doesn't include custom ticket fields, metric sets, or comment metadata", nor custom user or organization fields. For a migration, that loses too much.
Method 4: JSON export
Zendesk recommends JSON above 200,000 tickets; it is the best Admin Center option for a migration.
Steps. Same path; choose JSON. Accounts with more than one million tickets download in 31-day increments. Not available in sandboxes.
What it contains. Tickets with comments, as newline-delimited JSON, including the field types CSV drops.
Limits. If a ticket holds more than 1 MB of data, "the comments are not included in the JSON file"; those tickets are listed in a separate error file in the zip. The article doesn't say whether attachments or archived tickets are included, so check both against your own count.
Method 5: incremental export API (all tickets, any plan)
The incremental export API exports all tickets with comments on any plan, returning tickets changed since a start time, page by page.
# First request: start from a Unix timestamp (0 = the beginning)
curl "https://{subdomain}.zendesk.com/api/v2/incremental/tickets/cursor?start_time=0&exclude_deleted=true" \
-H "Authorization: Bearer {access_token}"
# Next requests: pass after_cursor from the previous page
curl "https://{subdomain}.zendesk.com/api/v2/incremental/tickets/cursor?cursor={after_cursor}" \
-H "Authorization: Bearer {access_token}"
Zendesk "highly encourages" the cursor-based version. Each page returns up to 1,000 tickets plus after_cursor and end_of_stream, which is true once you have everything to date. start_time must be more than a minute in the past, and the latest minute is never returned (incremental exports docs, as of 4 Nov 2026).
Zendesk export tickets with comments
The ticket stream doesn't carry the conversation. Two ways to get it:
- Ticket events export (
/api/v2/incremental/ticket_events) withinclude=comment_events. Without that sideload, comments show only as true/false flags. - List Comments (
GET /api/v2/tickets/{ticket_id}/comments), up to 100 per page. Inline images only appear as attachments withinclude_inline_images=true; the default is false (ticket comments docs, as of 4 Nov 2026).
Attachments
Zendesk has no bulk attachment download. For private attachments, content_url "is often a pre-signed, temporary URL" that returns 403 Forbidden once it expires, and it needs Basic Auth or an OAuth bearer token (Zendesk help, as of 4 Nov 2026). Download each file when you read its comment.
Troubleshooting. Deleted tickets appear in the stream unless you set exclude_deleted=true. Time-based exports can exceed 1,000 items per page when items share a timestamp; cursor pagination avoids that.
Pre-export checklist
- Plan tier. Team means API only. Growth or Professional and up can use Admin Center exports once enabled.
- Exports enabled? Ask the account owner to request it now.
- Ticket count band. Under 200,000: any format. Over 200,000: no XML. Over 1 million: JSON in 31-day chunks, or the API.
- True count. The Count Tickets endpoint skips archived tickets, so it under-counts.
- Brands, forms and fields. List every brand, form and custom field, flagging multi-line, multi-select and date fields (the ones CSV drops).
- Authentication. An OAuth client, not an API token.
- Other API users. Integrations running during the export share the account rate limit.
Config cleanup
Configuration gets rebuilt, so record only what is live: custom fields and their forms, active triggers and automations, macros still in use, groups (mapped to new queues) and SLA targets per priority. Running SLA timers don't move.
What happens to archived tickets after 120 days?
Zendesk archives most tickets 120 days after they close; very high-volume accounts may archive sooner (Zendesk archiving article, as of 4 Nov 2026).
Archived tickets drop out of views, and triggers and automations can't run on them; search and Explore still find them. Every ticket API endpoint returns them except Bookmarks, Count Tickets, Count Ticket Comments, Listing Tickets, Listing Ticket Metrics, Ticket Skips and Listing Ticket Audits. Incremental export is named as returning them.
So inventory with the incremental export, never a view, and fetch metrics and audits per ticket.
Delete, keep or leave behind
Delete what has no legal or support value; keep what customers or auditors may ask about. Our ticket history guide covers how much history to bring.
| Record type | Typical decision | Why |
|---|---|---|
| Spam, suspended and test tickets | Delete | Pollutes reporting in the new system |
| Closed tickets past your retention policy | Delete with a deletion schedule | Schedules only touch archived tickets |
| Attachments past retention | Delete with an attachment schedule, keep the ticket | Cuts transfer volume, keeps the record |
| Closed tickets inside retention | Keep and migrate | Customer history and audit trail |
| Open, pending and on-hold tickets | Keep, migrate last at cutover | Still being worked |
| Departed agents | Keep as users | Comment authorship |
| End users with erasure requests | Delete ("forget") before export | Don't copy data you were asked to remove |
How does Zendesk deletion actually work?
Agree what goes before the final export; some deletion can't be undone.
- Delete a ticket. It sits in the Deleted tickets view for 30 days, where you can restore or permanently delete it, then is deleted automatically (Zendesk help, as of 4 Nov 2026).
- Archived tickets skip that view. They can't be restored in the agent interface, only through the API with their IDs.
- Permanent deletion. Zendesk scrubs the ticket and keeps a minimal record such as the ID for 90 days; after that it no longer appears in API results or exports (Zendesk help, as of 4 Nov 2026).
- Deletion schedules. Conditions must include "Created at" or "Last updated". Eligible archived tickets go within 72 hours, up to 200,000 per account per day, and can't be restored. Up to 10 schedules, but only one active without the Advanced Data Privacy and Protection add-on (deletion schedules article, as of 4 Nov 2026).
- Attachments only. Redaction and attachment deletion schedules remove files and keep the ticket (Zendesk help, as of 4 Nov 2026).
- Users (Zendesk GDPR delete). Forgetting a user is a soft delete, then a permanent one; soft-deleted users are removed automatically after 30 days. You can't delete a requester on an unclosed ticket (Zendesk help, as of 4 Nov 2026).
Zendesk API rate limits that set your timeline
Two limits set an API export's length: the incremental export limit and the account limit.
| Limit | Requests per minute |
|---|---|
| Incremental exports | 10 (30 with High Volume add-on) |
| Suite Team | 200 |
| Suite Growth and Professional | 400 |
| Suite Enterprise | 700 |
| Enterprise Plus or High Volume add-on | 2,500 |
Source: Zendesk rate limits docs, as of 4 Nov 2026. High Volume is sold on Suite Growth or Support Professional and above, with at least 10 agent seats.
Read the headers on every response:
HTTP/1.1 200 OK
x-rate-limit: 700
ratelimit-limit: 700
x-rate-limit-remaining: 699
ratelimit-remaining: 699
ratelimit-reset: 41
zendesk-ratelimit-tickets-index: total=100; remaining=99; resets=41
Over the limit, Zendesk returns 429 Too Many Requests with a Retry-After header giving the seconds to wait.
Worked throughput math
Example: 250,000 tickets on Suite Growth (400 requests/min), comments fetched per ticket, up to 100 comments each. These are arithmetic, not measured export times.
Ticket pages: 250,000 / 1,000 per page = 250 requests
250 / 10 per minute = 25 minutes
Comments: 250,000 tickets x 1 request = 250,000 requests
250,000 / 400 per minute = 625 min, about 10.4 hours
At 2,500 per minute (High Volume):
250,000 / 2,500 per minute = 100 minutes
Attachment downloads come on top.
Next steps by destination
- Freshdesk: Zendesk to Freshdesk migration covers field mapping and import limits.
- Salesforce Service Cloud: the Zendesk to Salesforce migration guide maps tickets to Cases.
- Freshservice: the Zendesk to Freshservice migration guide covers ITIL record types. Still deciding? Compare Zendesk vs Freshservice first.
- Jira Service Management: start with Zendesk vs Jira. The Zendesk to Jira Service Management route covers the move itself.
- HubSpot, Intercom or Gorgias: the Zendesk to HubSpot, Zendesk to Intercom and Zendesk to Gorgias route pages list what moves and what is rebuilt.
Before switching Zendesk off, check the result against it; our data migration validation guide shows how.
How MigrateX does this
MigrateX reads Zendesk through the API, including archived tickets, comments, inline images and attachments, and keeps authors and original dates. You start with a free 100-record sample to check against the source, then get a fixed quote within 24 hours. MigrateX is SOC 2 Type II, GDPR compliant and HIPAA compliant, with a DPA and BAA available. See the Zendesk platform page or send us your ticket count.
Facts checked November 4, 2026 from Zendesk data export article, Zendesk incremental exports API, Zendesk rate limits, Zendesk OAuth migration guide, Zendesk ticket archiving and Zendesk ticket deletion schedules. No vendor paid for this article. How we research
Zendesk ticket export FAQ
How long does Zendesk keep tickets?
Zendesk documents no time limit on live tickets. Closed tickets archive after about 120 days but stay searchable and exportable through the API. Deleted tickets stay 30 days in the Deleted tickets view, then are permanently deleted. Deletion schedules, if set, remove archived tickets automatically.
Can I export Zendesk tickets with comments to CSV?
No. Both the view CSV and the account CSV exclude comments. Use the JSON export or the API, and fetch comments through the API for any ticket over 1 MB.
Why are old tickets missing from my export?
They are probably archived. Views, List Tickets and Count Tickets don't return archived tickets. The incremental export API does.
Do I still need an API token to export from Zendesk?
No. Existing accounts can't create new tokens since 27 Oct 2026, and all remaining tokens stop working on 30 Apr 2027. Use an OAuth bearer token.
How long does a full Zendesk API export take?
The ticket list is quick; the comments pass takes longest. Example: 250,000 per-ticket comment requests at 400 a minute is about 10.4 hours (arithmetic), before attachments.
Changelog
- 24 Mar 2026: First published as "How to Audit Legacy Help Desk Data Before a Professional Migration".
- 4 Nov 2026: Rewritten and moved from /blog/audit-legacy-help-desk-data-before-migration. Now a Zendesk export guide: every export method and its gaps, the API token to OAuth change, archived tickets, deletion timeline and rate-limit math, checked against Zendesk docs.
Written by
Ayush BothraFounding Member, MigrateX
Ayush writes about ITSM platforms, pricing and what it takes to move a service desk to a new platform without losing its history.


