Systems and records
What happens to your Zendesk data when you cancel?
By SourceX Editorial · Updated
Short answer
When you cancel Zendesk, access ends with the subscription and the account's data is later deleted under Zendesk's terms, with no realistic way back after that. The safe rule: export tickets, comments, internal notes, attachments and help center content before the renewal date, and ask Zendesk in writing for the post-termination window that applies to your account.
Key takeaways
- Export before the renewal date; access after cancellation is not something to plan around.
- Downgrading, cancelling and letting payment lapse lead to different losses, so choose the path on purpose.
- A ticket export without internal notes, side conversations and the attachment files themselves is not a complete archive.
- Ask Zendesk in writing for the access end date, any retrieval window and the deletion date.
- Name one owner for the archive so it outlives the company's own wind-down.
What happens to Zendesk data when you cancel#
Zendesk data stays tied to the subscription: when the subscription ends, agents and admins lose access, and the account's data is later deleted under Zendesk's terms and policies. Once deletion happens, there is no practical way to bring tickets back.
The gap between cancellation and deletion is the part owners ask about most, and it is the part you should not guess. Get the dates for your account from Zendesk in writing. Plan as if access ends on the renewal date, and treat any later window as a safety margin rather than working time.
Downgrade, cancel or let it lapse: three different outcomes#
Downgrading, cancelling and letting payment lapse lead to different outcomes, so a wind-down officer should choose one deliberately. A downgrade keeps the account alive but can remove features, and data stored by those features may become hidden or unusable.
The worst path is the accidental one. A card that expires during a wind-down can trigger suspension while the team is still exporting, and the person who could fix it may already have left.
| Path | What usually happens | Main risk | Use it when |
|---|---|---|---|
| Downgrade to a smaller plan | Account stays open with fewer features and agent seats | Side conversations, custom objects, advanced reporting or some channels may stop working | You need a lower-cost period to finish exports and nothing you need depends on removed features |
| Cancel at renewal | Full access until the end of the term, then access ends | Exports not finished by the end date are at risk | Exports are complete and verified |
| Payment lapses | Account may be suspended, then closed under Zendesk's process | Loss of access with no warning to the team doing exports | Never, if the records matter |
| Request account deletion | Data is removed under Zendesk's deletion process | Irreversible | Only after the archive is approved |
What a complete Zendesk export includes#
A complete Zendesk export includes every ticket with its full conversation, the files attached to it, and the configuration that explains how tickets were routed and answered. Built-in exports cover part of this; the rest needs API pulls or separate downloads, so map each component to a method before starting.
| Component | What to capture | Export note |
|---|---|---|
| Tickets and fields | All tickets, statuses, custom fields, tags, dates and assignees | Built-in export options vary by plan, and some must be enabled before use |
| Public comments and internal notes | Full comment history in order, with authors and timestamps | Check that internal notes are included, not only public replies |
| Attachments | The files themselves, mapped to ticket and comment IDs | Export files often reference attachments by link, and links stop working after closure |
| Side conversations | Threads with vendors, partners or other teams | Often missed by ticket exports |
| Users and organizations | Customer and agent records, with the IDs used in tickets | Needed to read authors and requesters later |
| Help center | Articles, translations, sections and their attachments | Separate from ticket exports |
| Macros, triggers, automations and views | Rules and canned replies | Explains how tickets were handled |
| Satisfaction ratings, calls and chats | Ratings with comments, call recordings and chat transcripts | Each channel may need its own export |
The export-before-renewal rule, step by step#
The export-before-renewal rule means nothing is cancelled, downgraded or allowed to lapse until a full export has been produced, checked and stored outside Zendesk. Working back from the renewal date gives the team a real deadline instead of a vague intention.
- Step 1: confirm the renewal date and the cancellation notice terms in your order form.
- Step 2: confirm an admin login that stays active through the end date, and an account owner with authority to ask Zendesk for help.
- Step 3: turn on or request the full export options your plan supports.
- Step 4: run ticket, user and organization exports, then pull comments, internal notes and side conversations through the API where needed.
- Step 5: download attachments and help center content separately.
- Step 6: check ticket counts by year and by status against what Zendesk shows.
- Step 7: store the archive in company-controlled storage with access controls, and record who holds it.
What to ask Zendesk in writing#
The questions to ask Zendesk in writing are the ones that set dates and options after the end of the term. A short email to your account representative or support, sent by the account owner, creates a record the wind-down file can rely on.
Keep the reply with the export index. If the company later faces a dispute, a regulator's question or a buyer's diligence request, the file shows what was kept, what was deleted and when.
- On what date will agent and admin access end?
- Is there any period after termination when data can still be retrieved, and how is it requested?
- Will the account be readable in any form after the end date?
- When will data be deleted, including backups, and can deletion be confirmed in writing?
- Can Zendesk help with a full export, and at what cost?
Illustrative: closing a support desk during a wind-down#
Illustrative: a fictional workforce scheduling software company has sold its customer contracts to a competitor and is now closing down. The wind-down officer finds that the Zendesk subscription renews in a few months and that the only admin who knows the setup is leaving soon.
The officer downgrades nothing and lets nothing lapse. The departing admin runs full ticket and user exports, pulls side conversations and internal notes through the API, downloads attachments and help center articles, and writes a short guide to the custom fields. The officer emails Zendesk for the access end date and deletion timing, files the reply, and gives notice of cancellation only after the archive passes a count check.
Months later, the buyer of the customer contracts asks how a recurring integration bug was handled for a shared client. The answer is in the archived internal notes.
Why a closed company's ticket archive still matters#
A closed company's ticket archive matters for disputes, warranty questions and any obligations transferred to a buyer. Support tickets linked to engineering fixes and outcomes can also be licensable operational records, if rights and privacy allow.
Keep the archive's structure intact for either purpose. Ticket IDs, comment order, timestamps and links between tickets and engineering issues are what make the history usable, whether the task is answering a dispute or a later licensing review.
That second question comes after preservation, never before. SourceX starts with a metadata-only fit check, then works through rights and privacy preparation, so customer names, emails and other personal details are removed before anything is shared, and the company approves every step.
Frequently asked questions
Can a cancelled Zendesk account be reactivated?
Sometimes, if the account has not yet been deleted and Zendesk agrees, but it is not a plan to rely on. Reactivation may require a new subscription and may not restore every feature or setting. Ask Zendesk directly before the end date if you think you might need it.
Who should hold the Zendesk archive after the company closes?
Someone with continuing authority: the wind-down officer, a successor entity, a buyer that took on customer obligations, or counsel holding records for the estate. Store the archive in company-controlled storage with access controls and a written note of what it contains and who may open it.
Do we need customer consent to keep support tickets?
Keeping tickets as business records is usually a matter of your retention schedule and privacy obligations. Using them for something new, such as licensing, raises separate consent and contract questions that are assessed with counsel. Treat retention and reuse as two decisions.
What if nobody has an admin login anymore?
Contact Zendesk support on the company's behalf, provide documents showing your authority, for example a board resolution or the paper appointing you to run the wind-down, and ask for account ownership to be transferred. Start early, because verification takes time and the renewal date does not move.
Should we delete personal data inside Zendesk before closing the account?
Deletion choices follow your retention schedule and privacy obligations, which counsel should confirm. Many companies export first, keep the archive under access controls for the periods their obligations require, and then let the vendor's deletion run. Deleting inside Zendesk before exporting removes your own copy as well, so the order of steps matters.
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.