Should you migrate closed tickets to a new help desk?

What is the short answer on closed tickets?

Usually only some of them. Migrate open tickets and the recent closed ones that agents will actually search, and keep the rest in an export. Dropping the full archive silently is the mistake, because years of resolved tickets are the record of how problems were solved, and that record can have value beyond the help desk.

A good default is a three-bucket split: load, archive, assess. Load what agents need day to day, archive what only compliance or finance might ask for, and have the owner decide whether the full archive deserves a licensing assessment before the old platform's subscription ends.

What does migrating closed tickets cost?

The cost is rarely the file transfer. It is the mapping and cleanup around it.

Specific per-record prices vary by vendor and change often, so get a current quote rather than relying on a rule of thumb.

How do you decide what to load?

Use a short decision rule with four tests.

1. Is it open or waiting? Load it.
2. Was it touched in the last 12 to 24 months? Load it if agents look up repeat issues. Pick the window with the support lead, not the consultant.
3. Is it tied to a contract, dispute or compliance obligation? Archive it with an index, and check retention rules with the company's counsel.
4. Is it older and resolved? Archive it in an export that keeps ticket, comments, tags, resolution and requester references together.

Then add a fifth step before you delete anything: ask the owner who has decision rights on the full archive.

Why might the old tickets be worth more than the help desk thinks?

A resolved ticket is a worked example: a question, an investigation, steps taken, an outcome and often a customer reaction. AI developers building service agents need that kind of record, and it barely exists on the public web. A multi-year archive with consistent tags and resolution codes is more useful than one that is thin or inconsistent. Whether any given archive has licensing value depends on content, rights and customer data, which the company reviews with SourceX. Customer personal information, client-owned content and sensitive material are redacted or excluded under terms agreed before any work.

What does this mean for a CX or management consultant?

You are already scoping the migration, so you are the person who sees the deletion date. Raise one question with the support director or COO: "Before we drop the history, would you like a non-binding look at whether it has licensing value?"

For the sister problem with audio, see what to do with call recordings in a contact center migration. The AI roadmap for mid-market companies puts the licensing option next to build and buy.

How do rewards work?

Partners earn 25% of the eligible platform fees SourceX actually collects from the referred company's licensing deals, capped at $100,000 per referred company. The reward is paid only after the buyer pays and SourceX receives its fee; an introduction, meeting or signed agreement alone does not trigger payment, and no reward is guaranteed.

Check your own engagement terms before you accept referral compensation, and read the program terms. The referral opportunities for management consultants page covers the role in more detail.

When should you skip it?

• The tickets mainly contain end-client data from a support outsourcing arrangement.
• The archive is already deleted.
• The company is under 50 full-time employees at peak (contractors excluded), or has only a short ticket history.
• Tickets are mostly consumer personal data with no basis for use.

Next step

Add an "archive owner decision" line to your migration plan. If a company fits who qualifies, register as a partner and introduce it, or have the company apply at sourcex.si/apply. Also see winding down a company without losing its records if the client is closing a business.