Zendesk before you cancel: preserving ticket history and attachments

What does a standard Zendesk export include, and what does it miss?#

A standard Zendesk account export covers tickets, users and organizations in JSON, CSV or XML, which is the core of a help desk archive but not all of it. Several things a wind-down team assumes are inside the export often need their own step.

Two gaps matter most. Attachments such as screenshots, invoices and log files may appear only as references back to the account rather than as files you hold, and side conversations with vendors or engineers can sit outside the ticket thread. Tickets handled by an AI agent cannot be exported at all, according to Zendesk's export documentation.

When does Zendesk delete your data after you cancel?#

Zendesk deletes account data on a fixed path after cancellation, and the timeline is shorter than most wind-down plans assume. Zendesk asks for notice of intent to cancel at least 30 days before the subscription term ends; for self-service customers, canceling in Admin Center counts as that notice.

A customer who cancels mid-cycle keeps using the account until the billing cycle ends. After that, nobody can sign in, and under Zendesk's Service Data Deletion Policy an automated process begins permanently deleting service data 90 days after cancellation or termination. Once that process starts, it cannot be reversed.

The practical rule: treat the last day of the billing cycle as the real deadline, not the deletion date. Once sign-in ends, there is no admin left to rerun a failed export, recover a missing attachment or explain a custom field.

How to turn on and run the full Zendesk export#

The full Zendesk export is not on by default: the account owner has to contact Zendesk Customer Support, giving the Support subdomain, to enable it. If the person who held the owner role has already left, fix that first, because the request has to come from the owner.

Plan level decides the route. Zendesk's account export tools are not available on Team plans, but customers on every plan, including Team, can export through the Zendesk REST API. For accounts with more than 200,000 tickets, Zendesk recommends the JSON format.

• 1Confirm who holds the account owner role and that the person can still sign in.
• 2Ask Zendesk Customer Support to enable exports for your subdomain.
• 3Check Admin Center for ticket deletion schedules and pause any that would remove archived tickets.
• 4Run the JSON export from Admin Center under Account, Tools, Reports; exports do not run in sandbox instances.
• 5Download the zip as soon as the email arrives; Zendesk keeps the link valid for at least three days, not indefinitely.
• 6Store two copies in company-controlled storage with restricted access.

Archived tickets and deletion schedules need a separate check#

Archived tickets are the part of a Zendesk history most often misjudged during a shutdown. Zendesk archives tickets 120 days after they reach Closed status, and archived tickets drop out of views even though search, direct links, user profiles and the API still reach them.

A team that checks its export against views will undercount what the account holds and may chase a gap that does not exist. Compare against search or API counts instead.

Deletion schedules are the opposite risk. Admins can create schedules that delete archived tickets after a set period, those deletions cannot be undone, and the schedules keep running. An old retention rule set years ago can quietly remove the early history a wind-down team is trying to keep, so review every schedule before the first export.

Collecting attachments and side conversations#

Attachments and side conversations are the Zendesk records most likely to be lost, because a quick export check rarely opens them. Both carry context: the photo of a damaged part, the crash log, the side thread where a support lead asked engineering for a fix.

For attachments, open a sample of exported tickets and look at how each file is represented. If the export gives a link rather than the file, run a download job that saves each attachment in a folder named by ticket ID and comment ID. Links pointing back into the account stop helping once the account is deleted.

For side conversations, compare a handful of escalated tickets in the agent workspace with the same tickets in the export. If side threads are absent, pull them through the API and store them beside their parent tickets. Run the same comparison for satisfaction ratings with comments and any linked engineering issues.

How to verify the archive before you give notice#

Verifying a Zendesk archive means proving it matches the live account on counts, content and files before anyone cancels. Do it while agents who know the account can still answer questions.

Illustrative: a scheduling software company closes its help desk#

Illustrative: a fictional company selling scheduling software to field service businesses is winding down. Its Zendesk account holds many years of tickets, a large share with screenshots and log files, plus side conversations where agents escalated bugs to engineers.

The operations lead asks the account owner, still employed through the final month, to have exports enabled, then pauses a deletion schedule an earlier admin had set for archived tickets. The first JSON export looks complete, but a sample check shows attachments only as links and side conversations missing from escalated tickets.

The team runs two API jobs, one for attachment files and one for side conversations, stores both by ticket ID and writes up the verification. Only then does it give cancellation notice. The archive is complete before the billing cycle ends, and the company can decide later whether to retain, delete or license it.

What the archive is for, and how SourceX approaches it#

A verified Zendesk archive is a business record first: it supports warranty claims, customer disputes and tax questions after operations stop. Zendesk's Data Processing Agreement states that Zendesk claims no ownership interest in the service data it processes, so the archive is generally the company's to manage under its own contracts and notices.

Support histories that link escalations, fixes and outcomes are also the kind of operational record some AI developers license. SourceX starts with a metadata-only fit check, so no tickets leave the company during assessment. If a package proceeds, the SourceX five-step transaction runs Supply, Rights, Preparation, Approval and Delivery, with personal and confidential details removed in Preparation and the company approving each step. Records are licensed, not sold outright, and a SourceX Evidence Packet documents provenance, licensing rights, permitted use, the privacy record and release authorization.