Systems and records
How long does Zendesk keep closed tickets?
By SourceX Editorial · Updated
Short answer
Zendesk keeps closed tickets in an active account until someone deletes them. Tickets are archived 120 days after closing, which removes them from views but not from search or the API, and nothing is purged on a schedule unless an admin created a deletion schedule. Check Admin Center for schedules before any cleanup or migration.
Key takeaways
- Zendesk does not delete closed tickets on its own while the account is active, unless an admin has set up a deletion schedule.
- Zendesk archives tickets 120 days after they close; archived tickets leave views but stay searchable and reachable through the API.
- Tickets deleted by a deletion schedule cannot be restored, and schedules keep running until someone changes them.
- Deleted tickets sit in a recoverable state for a limited time before Zendesk removes them permanently.
- Check Admin Center for deletion schedules before any cleanup, migration or privacy project.
What happens to a Zendesk ticket after it closes?#
A Zendesk ticket follows a predictable lifecycle after it closes: it stays closed and visible for a period, is then archived automatically, and remains in the account until an admin or a deletion schedule removes it. Closed tickets cannot be reopened; a customer reply creates a new follow-up ticket instead.
Because follow-ups create new tickets, one customer problem can span several ticket IDs. Keep the follow-up references when exporting, or the history of that problem fragments into unrelated records.
| Stage | What happens | Still exportable? |
|---|---|---|
| Solved | An agent marks the ticket solved; a requester reply reopens it | Yes |
| Closed | The ticket locks and can no longer be edited or reopened | Yes |
| Archived | 120 days after closing (sooner for very high-volume accounts), the ticket leaves views and stops firing rules but stays in search | Yes, through search, user profiles and the API |
| Deleted | An agent, admin or schedule deletes it and it moves to the deleted tickets view | Limited details only, unless restored |
| Permanently deleted | The ticket is removed and cannot be restored | No |
| Account cancelled | Sign-in ends; under Zendesk's Service Data Deletion Policy, permanent deletion of the account's data starts 90 days after cancellation and cannot be reversed | Only before the account closes |
Does Zendesk delete old tickets automatically?#
Zendesk does not delete old closed tickets automatically by default; automatic deletion happens only when an admin has created a ticket deletion schedule. Deletion schedules delete archived tickets after a set period, keep running against every ticket that matches their criteria, and the tickets they delete cannot be restored. Which schedules you can run depends on your plan; running several requires the Advanced Data Privacy and Protection add-on.
Other automatic removals are narrower. Suspended tickets, the messages filtered out before they became tickets, are cleared automatically after a short period. Some apps and integrations can delete or redact tickets on their own rules, and privacy tooling can remove a person's data on request. Check each one before assuming the history is intact.
- Admin Center deletion schedules: whether any are active, their conditions and when they last ran
- Triggers, automations and apps that delete, redact or close tickets in bulk
- Privacy request handling, including how end-user deletion affects that person's tickets
- Attachment and content redaction settings
- Agent roles that allow ticket deletion, and who holds them
- Sandbox or test accounts that could be confused with production
What archiving changes for exports and reporting#
Archiving changes where a ticket shows up, not whether it exists. Zendesk archives tickets 120 days after they close, or sooner on accounts with extremely high volume; archived tickets no longer appear in views or fire rules, but they can still be reached by search, direct link, the requester's profile and API endpoints. Tickets with more than 10,000 events or more than 2MB of associated records are not auto-archived. A process built on views will miss archived tickets, so confirm which API endpoints you use return them before planning a full export.
Archived tickets also cannot be updated, so tagging old tickets for a project has to happen before archiving or not at all. Reporting can treat archived tickets differently from active ones, so test a report that spans the full date range before using it to support a retention decision.
What a complete ticket export should capture#
A complete Zendesk export captures each ticket's full conversation and its change history, not only the fields shown in a view. Ticket audits record every update, including status changes, reassignments, priority changes and the trigger or agent that made them, so they show how a ticket moved from first report to resolution.
Zendesk's account export tools are not on by default: the account owner asks Zendesk Customer Support to enable them, giving the Support subdomain. They run from Admin Center under Account, Tools, Reports; Zendesk recommends JSON for accounts with more than 200,000 tickets, AI agent tickets cannot be exported, and Team plans lack these tools but can export through the REST API. Export users, organizations, groups and custom field definitions as well, because ticket rows refer to them by ID.
| What to pull | Why it matters |
|---|---|
| Public replies and internal notes | The thread holds the diagnosis, workaround and fix |
| Ticket audits | Show status, assignee and priority changes over time |
| Follow-up references | Join a customer problem that spans several tickets |
| Side conversations and linked Jira issues | Capture handoffs to other teams and engineering |
| Satisfaction ratings and comments | Record how the customer judged the outcome |
| Custom field and form definitions | Explain what each field value meant at the time |
Common ways teams lose old tickets#
Teams lose old Zendesk tickets mostly through deliberate actions taken for another reason. Each cause below is reasonable on its own; the loss happens when no one checks first whether the history was still needed.
| Cause | What happens | Prevention |
|---|---|---|
| Deletion schedule set for storage or privacy | Older tickets are removed on every run | Export first and document the retention decision |
| Bulk cleanup of spam or test tickets | Filters catch real tickets along with junk | Review a sample before any bulk deletion |
| Help desk migration | Only recent tickets move to the new tool | Archive the full history before cutover |
| Account cancellation | Data is removed after the account closes | Finish exports before the cancellation date |
| Privacy and erasure requests | A person's tickets or details are deleted or redacted | Keep a log of requests and what was removed |
| Role sprawl | Many agents hold delete permission | Limit deletion rights to a few admins |
Illustrative: an IT lead checks retention before a migration#
Illustrative: a fictional HR software company has used Zendesk Suite for years, with a long tail of closed tickets linked to Jira bugs through an integration. Its COO plans a move to another help desk and asks the IT lead to confirm that nothing old has already been lost.
In Admin Center, the IT lead finds a deletion schedule a former admin created to remove closed tickets past a certain age. The schedule is paused with the COO's written approval, and the remaining history is pulled through the incremental export API with comments, internal notes, attachments, tags, custom fields and follow-up references.
Only recent tickets move to the new help desk. The full archive goes to company-controlled storage under a retention schedule, and a deletion rule is rebuilt later on purpose, after counsel signs off on how long ticket history should be kept.
How SourceX approaches old support tickets#
SourceX approaches an old Zendesk archive as a support history first and a dataset second. Under the SourceX Enterprise Data Value Framework, tickets that carry the full thread, internal notes and a resolution, and that link to engineering issues, are the strongest material.
The first conversation covers years of tickets, channels, languages and links to other systems, without any ticket text changing hands. A package that proceeds moves through the SourceX five-step transaction: customer names, contact details and account identifiers are removed in Preparation, and the company signs off on each release in Approval before Delivery.
Frequently asked questions
Can a permanently deleted Zendesk ticket be recovered?
Generally no. Once a ticket leaves the deleted tickets view, the deletion is treated as final, and support is unlikely to restore it. Your own exports and backups are the only dependable copy, which is why exporting before any deletion schedule or cleanup matters.
Do archived tickets count toward storage limits?
They may. Zendesk plans include data and file storage allowances, and archived tickets and their attachments are still stored. Check your plan's current limits in your account and in Zendesk's documentation before deciding that deletion is needed to stay within them.
Should we turn on a deletion schedule?
It depends on your retention policy. Privacy laws that may apply and customer contracts can favor deleting personal data you no longer need, while product, warranty and dispute needs favor keeping history. Decide the retention period in writing with counsel, then export before the schedule takes effect.
Are Zendesk tickets kept forever if nothing is configured?
While the account is active and no deletion schedule or manual deletion applies, closed tickets generally remain. That is not a promise of permanence: plan changes, cancellation, privacy requests and admin actions can all remove them. Keep your own archive rather than relying on the account.
Can old Zendesk tickets be licensed for AI?
They may be, after a rights review of customer contracts, privacy notices and help desk terms. Preparation removes customer names, emails, phone numbers and account details. The ticket text, internal notes and resolutions are what carry value, so exports should keep the full thread.
Sources
- Zendesk automatically archives tickets 120 days after they reach Closed status, or sooner for accounts with extremely high ticket volume. Archived tickets can still be found by search, direct link, user profile and API endpoints, but they do not appear in views or fire rules. Source
- Zendesk admins can create ticket deletion schedules that delete archived tickets after a set period. Deleted tickets cannot be restored, and the schedules keep deleting any tickets that match their criteria. Source
- Zendesk's account data export tools (tickets, users and organizations as JSON, CSV or XML) are not available on Team plans, but customers on every Zendesk plan, including Team, can export data through the Zendesk REST API. Source
- Zendesk says that once an account is cancelled you can no longer sign in and the account data is deleted under the Service Data Deletion Policy. A customer who cancels mid-cycle keeps using the account until the billing cycle ends. Source
- Under Zendesk's Service Data Deletion Policy, an automated process that permanently deletes the account's Service Data starts 90 days after the account is canceled or terminated, and once it starts it cannot be reversed. Source
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.