Systems and records
Should you migrate old support tickets or archive them?
By SourceX Editorial · Updated
Short answer
Migrate the support tickets agents need in daily work, usually open tickets and recent history for active customers, and archive the full ticket history as a complete export outside the new helpdesk. Index both by the original ticket ID so any old ticket can be found from the new system, which makes migrating everything unnecessary.
Key takeaways
- Migration effort grows with ticket volume, attachments and field mapping, while each older year matters less to agents.
- Base the cutoff on how often agents actually open old tickets, not on a round number.
- A complete archive keeps internal notes, attachments and links to bugs that imported tickets often lose.
- Store the old ticket ID on every migrated ticket and key the archive by the same ID.
- Export metrics history separately so service level and satisfaction trends survive the switch.
The decision rule for old tickets#
The decision rule for old support tickets is to migrate what agents need daily and archive everything, with the original ticket ID linking the two. Migration serves the people working in the new helpdesk; the archive serves everyone with a question about the past.
Migrating everything looks safer but rarely is. Imported tickets can lose fidelity: authors map to a generic user, timestamps take the import date, internal notes merge with public replies or large attachments fail. Search in the new tool fills with closed issues from customers who left long ago, and the project timeline stretches with every extra year carried across.
What drives the cost of a ticket migration?#
Ticket migration cost is driven by volume and by everything each ticket carries: attachments, notes, custom fields and the links to users and organizations that must be mapped. Migration services and in-house scripts slow down on the same things, so a smaller scope reduces effort at every stage.
| Cost driver | Why it adds effort | How to reduce it |
|---|---|---|
| Ticket and message volume | Every record is read, transformed, written and checked | Migrate a defined slice; archive the rest |
| Attachments | Large files transfer slowly and fail more often | Move attachments only for migrated tickets |
| Custom fields and forms | Each field needs a mapping and a test | Retire fields nobody reports on |
| Users and organizations | Authors must match accounts in the new tool | Map active agents; label departed ones as legacy |
| API rate limits on both sides | Pulls and writes are throttled | Start early and run by period |
| Validation | Someone must confirm the result | Fewer migrated records means faster sign-off |
Which tickets to migrate and which to archive#
Which tickets to migrate depends on whether an agent will act on them, or look them up while serving a current customer. Everything else goes to the archive, which holds the full history either way.
| Ticket segment | Migrate | Archive | Reason |
|---|---|---|---|
| Open, pending and on-hold | Yes | Yes | Work in progress must continue |
| Recent closed tickets, active customers | Yes | Yes | Agents check recent history before replying |
| Linked to open bugs or feature requests | Yes | Yes | Engineering links must stay live |
| Older closed tickets, active customers | Rarely | Yes | Looked up occasionally; the archive covers it |
| Closed tickets, former customers | No | Yes | Needed for disputes and analysis, not daily work |
| Spam, auto-replies and test tickets | No | Optional | No operational value |
| Under legal hold | No | Preserved as required | Hold rules take priority over the plan |
How to set the cutoff from your own data#
The cutoff should come from your own helpdesk data: how often agents open closed tickets, and how old those tickets are. Many helpdesks can report reopen events or ticket views; if yours cannot, sample recent replies and note how far back agents looked before answering.
Interview senior agents too. They know which customers have long, complicated histories and which ticket types, such as installations or contract renewals, tend to be looked up later. Those cases can be migrated by segment instead of pushing the date back for everyone.
Write the rule down with its reasoning, for example full history for enterprise accounts plus recent history for everyone else, so the next helpdesk switch starts from a documented decision rather than a debate.
Read-only old helpdesk, full export or both?#
Archived tickets can be held in three ways: the old helpdesk kept read-only, a full export to company storage, or both during a transition. The right choice depends on the old vendor's terms, the cost of keeping seats and how much your team relies on the old tool's search.
Even when the old helpdesk stays read-only, take the full export at the start. Vendor plans change, finance closes accounts that look unused and retention settings can delete what everyone assumed was kept.
Check the old vendor's documented behavior before you choose. Zendesk, for example, archives tickets 120 days after they close; archived tickets stay reachable by search, link and API but drop out of views. Admins can also set deletion schedules that permanently delete archived tickets. Freshworks partner support says Freshdesk deletes an account and its data 14 days after the subscription ends and that an export can take up to 10 business days, so a read-only period may not exist at all.
| Option | Pros | Cons | Fits when |
|---|---|---|---|
| Old helpdesk read-only | Familiar search and views | Ongoing fees; the vendor controls access and retention | A transition with frequent lookups |
| Full export to company storage | Owned, durable, independent of the vendor | Needs a viewer or search tool and an owner | The long-term default |
| Both, then export only | Agents keep familiar search during transition | Two things to manage for a while | Large teams with heavy lookup needs |
Indexing both by ticket ID#
Indexing by ticket ID makes the archive usable from inside the new helpdesk instead of leaving it as a separate island. The link takes only a few fields, and they must be set up before the migration runs.
Test the link on a sample before cutover: pick old tickets at random, find each one from the new helpdesk through the customer record, and confirm the archive returns the full thread with notes and attachments.
- Add a custom field for the legacy ticket ID on every migrated ticket.
- Add a legacy customer or organization ID field on customer records.
- Key the archive by legacy ticket ID, with attachments in matching folders.
- Give agents a simple archive search by legacy ticket ID, customer ID and email domain.
- Record how old tags, groups and custom fields map to new ones.
Illustrative: a property management software company changes helpdesk#
Illustrative: a fictional property management software company is moving from its long-time helpdesk to a platform that bundles chat and phone support. The first migration quote covers every ticket, and the timeline puts cutover after the old contract's renewal date.
The COO and IT lead pull view data from the old helpdesk and find that agents rarely open tickets beyond recent history, except for a group of large portfolio customers. They migrate open tickets, recent history and full history for those accounts, and archive everything else as a complete export with notes, attachments and links to engineering issues, keyed by ticket ID.
Cutover lands before renewal. The archive later settles a billing dispute and gives the product team a long view of recurring issues, without the new helpdesk carrying years of closed tickets.
What the full archive is worth later#
A full ticket archive keeps value the migrated slice cannot: long-run trends in issue types, the path from a ticket to a bug fix and a release, and how answers changed as the product changed. Product, engineering and finance all draw on it, and so do buyers in a sale of the company.
Linked support history is also a record type AI developers study when building support and agent tools. SourceX reviews such an archive first from a description alone, without files. A package that goes further moves through the SourceX five-step transaction of Supply, Rights, Preparation, Approval and Delivery, where personal details are removed and the company approves every release.
Frequently asked questions
Will customers notice if old tickets are not migrated?
They might, if your help center shows customers their past requests. Decide whether customers need to see older requests and, if so, include them in the migration for those accounts. Either way, give agents a quick way to retrieve an archived ticket when a customer asks.
How do we keep service level and satisfaction trends?
Export metrics history separately: response and resolution times, satisfaction results and volumes by period and channel. Imported tickets rarely recreate original timings, so the old helpdesk's reports, saved as data, become the record of past performance.
What about attachments and inline images?
Archive them all, keyed by ticket ID, and download them while you still have access, since attachment links can stop working after an account closes. Migrate attachments only for tickets you migrate, and check the new helpdesk's file limits first.
Who decides the cutoff?
The head of support proposes it from the data, IT confirms what the migration can carry, and legal or compliance confirms holds and retention needs. The COO signs off, because the decision trades cost and timing against agent convenience.
Should the archive be deleted eventually?
Set a retention rule with counsel. Privacy laws and customer contracts may require deleting personal information once it is no longer needed, while legal holds and tax or contract obligations may require keeping some records. Removing personal details can sometimes let you keep the rest.
Sources
- Zendesk automatically archives tickets 120 days after they reach Closed status; archived tickets can still be found by search, direct link, user profile and API but do not appear in views. Source
- Zendesk admins can create ticket deletion schedules that delete archived tickets after a set period, and deleted tickets cannot be restored. Source
- Freshworks partner support says Freshdesk permanently deletes the account and its data 14 days after the subscription end date, and the export can take up to 10 business days. Source
Related resources
- IndustryBPO & contact centers data
- IndustryIT managed services data
- QuestionDo AI labs buy video of people working?
- InsightCan property management companies sell their data to AI companies?
- InsightCan e-commerce brands sell their data to AI companies?
- InsightCan call centers and BPOs sell their data to AI companies?
See if your company qualifies
A short company assessment. No data uploads are needed.