Software companies
Migrating helpdesks: what to do with tickets you will not migrate
By SourceX Editorial · Updated
Short answer
Tickets you will not migrate should be exported in full and archived in company storage before the old helpdesk subscription ends, keyed by the original ticket ID with comments, internal notes and attachments intact. Archiving is the default. Deletion follows your retention policy, and licensing is a later option for archived history after a rights review.
Key takeaways
- Export everything you are not migrating before the old plan is downgraded or cancelled, because API access often goes with it.
- Keep the original ticket ID as the key that ties comments, attachments and linked engineering issues together.
- Archive first and decide later: deletion and licensing are both easier from a complete, documented archive.
- Resolved tickets with internal notes and linked Jira issues carry the most value if licensing is ever considered.
Which tickets get left behind in a helpdesk migration?#
The tickets left behind in a helpdesk migration are usually closed history older than a cutoff date, plus anything the new system cannot map cleanly. Teams set a cutoff because migration services often price by record volume and because agents rarely open old tickets in daily work.
Less obvious items get dropped too: internal notes, side conversations, satisfaction ratings, field change history, merged duplicates, macro usage, and tickets from deleted users or organizations. Agents may never miss them, but each can matter later for reporting, a customer dispute or a licensing review.
Set the cutoff by how tickets are used, not by age alone. Tickets tied to open disputes, warranty claims, active enterprise accounts or unresolved bugs often deserve migration even when they are old, while high-volume password resets can stay behind even when recent.
Migrate, archive, keep read-only or license: how to decide#
The decision for each group of tickets comes down to who still needs them and in what form. Agents need open and recent tickets inside the new tool; finance, legal and leadership need older history to be retrievable; nobody needs a second helpdesk subscription that runs indefinitely.
Licensing is not an alternative to archiving. It is an option you keep open by archiving well, and it is assessed only after rights and privacy have been reviewed.
| Option | Best for | What you keep | Main risk |
|---|---|---|---|
| Migrate to the new helpdesk | Open tickets and recent history agents use | Working records in the daily tool | Cost and mapping errors on custom fields |
| Archive to company storage | Closed history outside the cutoff | A complete export under your control | An archive nobody can search or explain |
| Keep the old helpdesk read-only | A short overlap during cutover | Native search for a while | A subscription that never gets cancelled |
| Delete under retention policy | Spam, test tickets, data past its retention date | A deletion record | Deleting history later needed for a dispute |
| Assess for licensing | Archived history with resolutions and linked issues | Ownership; the records are licensed, not sold | Proceeding without a rights review or de-identification |
- 01Your work records
- 02Personal details removed
- 03You approve the release
- 04Licensed to AI developers
How to build a ticket archive that stays useful#
A useful ticket archive is a complete structured export that someone outside the support team can understand years later. Export through the helpdesk API rather than a reporting tool, because report exports usually flatten conversations and drop internal notes.
Store the archive in company-controlled storage with restricted access, a checksum for each file and a retention label. Record who holds the admin account for the old helpdesk until cancellation, so nobody loses access in the middle of the export.
- Tickets with every public reply and internal note, in order, with author and timestamp.
- Ticket fields, custom fields, tags, priority, status history and satisfaction ratings.
- Organization and user records, so tickets can be grouped by account.
- Attachments saved as files and mapped to ticket and comment IDs in a manifest.
- Links to engineering issues, such as Jira keys stored by an integration field.
- A schema note explaining field names, status values and the export date.
What to check before the old subscription ends#
The old subscription's end date sets the real deadline, not the go-live date of the new helpdesk. Many vendors restrict API access on lower plans, limit how far back exports reach, or delete account data after cancellation, so check your plan and the vendor's documentation before you downgrade.
Zendesk shows how plan details shape the plan. Its account data exports are not turned on by default, so the account owner has to ask Zendesk Customer Support to enable them, and those export tools are not available on Team plans, although the REST API works on every plan. Zendesk recommends JSON for accounts with more than 200,000 tickets, and AI agent tickets cannot be exported. Closed tickets are archived automatically 120 days after closing; they drop out of views but remain reachable through search and the API. If an admin has set a ticket deletion schedule, it keeps deleting matching archived tickets and they cannot be restored, so pause it before the export.
Confirm four things in writing: the date access ends, whether a downgrade removes API access, how long the vendor keeps data after cancellation, and how deletion is confirmed. Run a full test export early, because accounts with many attachments take longer than expected and API rate limits slow everything down.
Check integrations as well. If the old helpdesk pushed links into Jira or your CRM, those links will break, so archive the mapping between ticket IDs and issue keys to keep the connection.
Can unmigrated tickets be licensed?#
Unmigrated tickets can sometimes be licensed, because resolved support conversations are a record type AI developers use to train and evaluate support agents. Whether yours qualify depends on your customer agreements, your privacy notices and how much personal data the tickets contain.
What makes archived tickets valuable is the same thing that makes them hard to migrate: full threads, internal notes explaining decisions, resolutions and links to bugs. The SourceX Enterprise Data Value Framework counts human-generated signal, domain expertise, data cleanliness and rights as value drivers, while preparation cost and privacy burden reduce net value.
Some tickets should stay out of any package whatever the contracts say: threads containing payment card details, health information volunteered by end users, security vulnerability reports, legal threats and tickets from customers whose agreements prohibit reuse. Tag them in the archive while the export is fresh, because finding them later is slower.
| Archive feature | Why it matters if licensing is considered |
|---|---|
| Full threads with internal notes | Shows how agents reasoned, not just the final reply |
| Resolution codes and satisfaction ratings | Gives each conversation an outcome |
| Linked Jira issues | Connects a customer problem to the fix that solved it |
| Consistent tags and fields | Lowers preparation cost |
| Customer names, emails and account details | Raises privacy burden; removed or de-identified before any release |
Illustrative: retiring a legacy helpdesk at a freight software company#
Illustrative: a fictional freight brokerage software company moves from a legacy helpdesk to a new support platform. The head of support migrates open tickets and recent history and leaves several years of closed tickets behind.
Before the downgrade, the COO has IT export the older tickets through the API with internal notes, attachments and the Jira link field, and stores them in company storage with a schema note. A few shipper accounts have contracts restricting reuse of their data, so their tickets are tagged in the archive.
Months later, leadership reviews the archive for licensing. The tagged accounts are excluded, customer details are removed in preparation, and resolved threads linked to engineering fixes become the proposed package.
How SourceX reviews an archived helpdesk#
SourceX reviews an archived helpdesk starting from metadata: the helpdesk name, the years covered, broad ticket volumes, whether internal notes and engineering links exist, and any known contract restrictions; no tickets or files change hands at that stage.
If the archive moves forward, it goes through the SourceX five-step transaction of Supply, Rights, Preparation, Approval and Delivery. The archive stays in your storage until delivery is approved, and the SourceX Evidence Packet's privacy record lists what was removed from the tickets and why.
Frequently asked questions
Is it cheaper to keep the old helpdesk on a small plan?
Sometimes, for a short overlap, but rarely as a long-term archive. Lower plans may remove API access or limit exports, and the subscription tends to outlive the people who know why it exists. A structured export in company storage is usually easier to govern and to explain later.
Do we need customer consent to keep archived tickets?
Keeping tickets as business records is usually governed by your retention policy, privacy notice and customer agreements rather than fresh consent. Licensing them is a different use and needs its own review. The laws that may apply differ by customer location, so confirm both questions with counsel.
Should internal notes go into the archive?
Yes. Internal notes record why agents escalated, credited an account or declined a request, and they are often the first thing lost in a migration. They can also contain candid comments, so restrict access to the archive and review notes before any external use.
What file format should a ticket archive use?
JSON preserves nested conversations and fields best, with attachments stored as files and mapped by ID in a manifest. Add a CSV index of tickets for quick browsing. Avoid PDF-only exports, which are readable but hard to search, de-identify or reuse.
Who should own the archive after the migration?
Give it a named owner outside the support tool, often IT or operations, with legal setting retention and the head of support approving access requests. Without an owner, archives get duplicated, forgotten or deleted in the next storage cleanup.
Sources
- Zendesk data exports must be enabled by contacting Customer Support; account export tools are not available on Team plans but the REST API is available on every plan; JSON is recommended above 200,000 tickets and AI agent tickets cannot be exported. Source
- Zendesk archives tickets 120 days after they are closed; archived tickets are reachable by search and API but do not appear in views. Source
- Zendesk ticket deletion schedules delete archived tickets after a set period, keep deleting matching tickets, and deleted tickets cannot be restored. Source
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.