How to Export Tickets from Zendesk: The Complete Step-by-Step Guide (2026)

Why You Need to Export Zendesk Ticket Data

Your Zendesk instance holds more than conversations. It contains structured data on customer issues, agent performance, resolution patterns, and product gaps. At some point, you'll need that data outside of Zendesk — for a QBR your reporting tools can't build natively, a compliance audit requiring timestamped archives, or a migration to another platform.

The process varies significantly depending on how much data you need, what format you need it in, and what you plan to do with it. This guide covers the three primary methods: View Export (CSV), Full Data Export (JSON/CSV/XML), and the Incremental Exports API. We'll document what each method actually returns, where each one breaks, and which Zendesk plans support which features.

Before You Begin: Prerequisites

Before exporting, confirm two things:

• Admin permissions: The Full Data Export and API methods require administrator access. Agents cannot access these features. This is a Zendesk security control, not a bug.
• Feature enablement: Zendesk does not enable the Full Data Export feature by default on all plans. The account owner may need to contact Zendesk Support and request that "data export" be turned on, providing your subdomain (e.g., yourcompany.zendesk.com). This applies primarily to Suite Team and Suite Growth plans — Suite Professional and Enterprise typically have it enabled. Check Admin Center → Account → Tools → Reports → Export to see if the tab is visible before contacting support.

Once you've confirmed admin access and feature availability, you're ready to proceed.

Method 1: View Export (CSV)

This is the fastest way to pull a targeted list of tickets. It exports tickets currently visible in a specific View into a CSV file.

Best for:

• Targeted datasets up to 1,000 tickets.
• Weekly or monthly team reports.
• Filtering by status, group, tag, assignee, or brand.
• Immediate use in Excel or Google Sheets.

Step-by-Step

Step 1: Log in to Zendesk Support. Click the Views icon in the left navigation bar.

Step 2: Select the view containing the tickets you want, or create a new one. For example, to export all solved billing tickets from the past 30 days:

• Status | Is | Solved
• Hours since solved | Less than | 720
• Tags | Contains at least one of the following | billing_issue

Getting the view conditions right before exporting is the most important step.

Step 3: With the view loaded, click the Actions menu (three vertical dots) in the top-right corner.

Step 4: Select Export as CSV.

Step 5: Zendesk processes the export in the background and sends a download link to the email address on your user account. The download link is typically valid for at least three days.

What the CSV Contains

The CSV includes ticket metadata: Ticket ID, Subject, Requester Name & Email, Assignee Name, Status, Priority, Group, Creation Date, Last Updated Date, Tags, and any custom fields visible in the view.

What it does not contain: Ticket comments (public replies), internal notes, descriptions, or attachments. You get the envelope, not the contents.

Hard Limit: 1,000 Tickets

The View Export caps at 1,000 tickets per export. If the view contains 1,001 tickets, the CSV silently truncates at 1,000 — often without warning. There is no pagination or "next page" option.

For anything beyond 1,000 tickets, you need Method 2 or Method 3.

Method 2: Full Data Export (JSON / CSV / XML)

When you need everything — every ticket, user, comment, and organization — the Full Data Export is the native bulk extraction tool.

Best for:

• Complete data backups for compliance (GDPR, CCPA) and archival.
• Datasets exceeding 1,000 tickets.
• Full historical analysis across your entire account.
• Migration preparation (with significant caveats — see below).

Step-by-Step

Step 1: Click the Admin icon (gear symbol) in the bottom-left sidebar to open the Admin Center.

Step 2: Navigate to Account → Tools → Reports.

Step 3: Click the Export tab.

Step 4: Choose your export format:

Format	Date Range Filter	Includes Comments	Includes Attachments	Best Use Case
JSON	Yes (created_at field, ISO 8601 format, UTC)	Yes (in separate file, linked by ticket ID)	URLs only (not binary files)	Large accounts (200K+ tickets), programmatic processing, migration prep
CSV	No	No	No	Metadata-only snapshots — not suitable for backup or migration
XML	No (all-or-nothing)	Yes	URLs only (not binary files)	Legacy integrations requiring XML; avoid for new projects

Step 5: Click Export or Request File and wait. Processing time scales with account size: a few minutes for small accounts, potentially 24+ hours for accounts with hundreds of thousands of tickets.

Step 6: Zendesk sends a download link via email when the file is ready. The download is a ZIP archive.

What the JSON Export Actually Contains

The JSON export produces separate files for different object types. A ticket object in the JSON export typically includes these fields:

• id — Zendesk ticket ID
• subject — Ticket subject line
• description — First comment / original message
• status — open, pending, hold, solved, closed
• priority — low, normal, high, urgent
• requester_id — numeric ID (must be cross-referenced with the users export)
• assignee_id — numeric ID
• group_id — numeric ID
• tags — array of tag strings
• custom_fields — array of field ID / value pairs
• created_at — ISO 8601 timestamp, UTC
• updated_at — ISO 8601 timestamp, UTC

Comments are exported in a separate file and linked to tickets by ticket_id. Each comment includes author_id, body (HTML), public (boolean), and created_at.

Attachments: The export includes attachment URLs within comment objects, but does not include the binary files themselves. Attachment URLs point to Zendesk's CDN and may expire. If you need to preserve attachments, you must download them separately before the URLs expire — either manually or via the Attachments API.

Relational Mapping

The JSON export uses numeric IDs for all relationships. A ticket's requester_id is just a number — you must join it against the users export file to resolve it to a name and email. The same applies to assignee_id, group_id, and organization_id. This relational mapping step is where most DIY export projects hit unexpected complexity.

Limitations

• Rate limit: Zendesk restricts full exports to approximately once every 7 days per account. If your first export has an issue, you may wait a full week before you can try again.
• Processing time: Hours to days for large accounts. There is no progress indicator.
• File size: Large accounts produce multi-gigabyte ZIP files. You cannot open these in Excel — you need a scripting language (Python, Node.js) or a database tool to parse them.
• No incremental option: The full export is a point-in-time snapshot. If tickets are created or updated during or after the export, those changes are not captured.

Troubleshooting

• Export email never arrives: Check your spam/junk folder. Verify the email address on your Zendesk admin profile is correct. If the export is for a very large account, wait at least 48 hours before assuming it failed. You can also check the Export tab — if a download link appears there, the email may have been filtered.
• ZIP file is corrupted or won't extract: Re-download the file. Large ZIPs occasionally fail during download on unstable connections. Use a dedicated archive tool (7-Zip, The Unarchiver) rather than the OS default.
• Missing data in export: Confirm you selected the correct format. CSV exports omit comments and descriptions. JSON exports require you to download the separate comments file.

Method 3: Incremental Exports API

The Zendesk Incremental Exports API is the most powerful and flexible extraction method. It is designed for programmatic, ongoing data extraction and is the foundation most migration tools and data pipelines use.

Best for:

• Exporting more than 1,000 tickets programmatically.
• Building ongoing data sync pipelines.
• Delta exports — pulling only tickets created or updated since your last export.
• Migration tooling that needs to capture changes right up to cutover.

How It Works

The Incremental Exports API returns tickets (or users, or organizations) modified since a specified Unix timestamp. It uses cursor-based pagination, returning up to 1,000 records per page with a cursor to fetch the next page.

Endpoint:

GET /api/v2/incremental/tickets/cursor.json?start_time={unix_timestamp}

Key parameters:

• start_time — Unix timestamp. Returns all tickets with generated_timestamp (an internal Zendesk field reflecting the last database-level modification) at or after this time.
• The response includes after_cursor for pagination and end_of_stream (boolean) to indicate when all records have been returned.

Rate limits: The Incremental Exports API allows approximately 10 requests per minute per account. Each request returns up to 1,000 records. For a 500,000-ticket account, expect the full extraction to take roughly 8–10 hours when accounting for rate limiting and pagination.

What It Returns

Each ticket object returned by the API includes the same fields as the JSON export (id, subject, status, requester_id, custom_fields, etc.) plus sideloaded data if requested. Comments and attachments require separate API calls:

• Comments: GET /api/v2/tickets/{id}/comments.json
• Attachments: Included as URLs within comment objects. Binary files must be downloaded separately.

When to Use the API vs. the Full Data Export

Scenario	Recommended Method
One-time full backup, non-technical team	Full Data Export (JSON)
Ongoing sync or scheduled extraction	Incremental Exports API
Exporting only recent changes (delta)	Incremental Exports API
Account on Suite Team or Growth plan	View Export (CSV) — other methods may not be available
Migration to another platform	Incremental Exports API (for precision and delta capability)
Quick report under 1,000 tickets	View Export (CSV)

Decision Table: Which Export Method Should You Use?

Factor	View Export (CSV)	Full Data Export	Incremental Exports API
Max tickets	1,000	Unlimited	Unlimited
Includes comments	No	JSON & XML only	Separate API call
Includes attachments	No	URLs only	URLs only (separate download)
Date range filter	Via view conditions	JSON only	Yes (start_time parameter)
Rate limit	None documented	~Once per 7 days	~10 requests/min
Output format	CSV	JSON, CSV, XML	JSON
Technical skill required	None	Moderate (parsing, relational mapping)	High (scripting, pagination, error handling)
Plan availability	All plans	Professional+ (may require enablement)	Professional+
Best for	Quick reports	Full backups, compliance	Pipelines, migrations, delta syncs

When Manual Exports Aren't Enough: Migration Considerations

If your goal is migration — moving from Zendesk to another platform — the native export methods have real limitations:

• The Full Data Export is a point-in-time snapshot. Tickets created during or after the export are missed. You'll need a delta process to catch up.
• Relational mapping is manual. Requester IDs, assignee IDs, organization IDs, and group IDs all need to be resolved against separate export files.
• Attachments require separate handling. The export gives you URLs, not files. Those URLs can expire.
• The 7-day rate limit makes iteration slow. If your first export has a mapping issue, you may wait a week to retry.
• No format translation. The raw export doesn't map to your destination platform's schema. That translation layer — field mapping, status mapping, custom field conversion — is entirely on you.

The Incremental Exports API solves some of these problems (delta capability, no 7-day rate limit), but you still need to build the relational mapping, attachment downloading, and destination-side import pipeline yourself.

Conclusion

Knowing how to export tickets from Zendesk comes down to matching your method to your use case:

• View Export (CSV): Fast, simple, limited to 1,000 tickets, no comments or attachments. Use it for targeted reports.
• Full Data Export (JSON/CSV/XML): Complete account extraction, but slow, rate-limited, and requires technical skill to parse. Use it for backups and compliance archives.
• Incremental Exports API: The most powerful option — supports delta exports, cursor-based pagination, and programmatic pipelines. Use it for migrations, ongoing sync, and large-scale extraction. Requires development resources.

Before choosing, verify your Zendesk plan tier supports the method you need. And if you're exporting for a migration, plan for the relational mapping, attachment handling, and delta sync work that the raw export doesn't do for you.

For a deeper look at advanced extraction patterns, see our guide on 3 Advanced Ways to Export Tickets from Zendesk.