Merging helpdesk instances after an acquisition: keep ticket history

How do you keep ticket history when helpdesks are consolidated?

Treat ticket threads and their resolutions as the asset to protect: migrate with full conversation history, status, tags and resolution fields mapped one to one, and keep a read-only archive of the old instance until the new one is verified. A migration that moves only open tickets or flattens threads destroys the most useful part.

Support records are among the most structured business records a company produces. Each ticket has a request, a sequence of replies, an owner, a category and an outcome. For an MSP or CX consultant running a consolidation, how you map those fields decides whether the history survives. This is general information; confirm what your tools support in each vendor's current documentation.

What a support instance holds

• Tickets with the customer's request, agent replies, internal notes and the final resolution.
• Fields and tags that classify the issue, product, priority and root cause.
• Timestamps that show first response, escalations and time to resolve.
• Satisfaction ratings and survey comments.
• Macros, canned replies and knowledge-base articles that show how agents answer.
• Links to CRM accounts, engineering issues and chat threads.
• Customer, organization and agent records.

Older instances may also include a prior vendor's archive from an earlier migration, which extends the history further back.

Why resolution history is high-value

Training and evaluating agents that handle support work needs real examples of a problem, the steps taken and the outcome. A ticket with a clear resolution, an escalation path and a category tag is labeled work. A flattened export with no status or resolution field is much less useful.

Customer data is also at stake. Tickets contain personal data and customer confidences, so rights and de-identification are agreed with the company before any work. Whether specific records can be licensed is decided in qualification, contracts and counsel review, not by the partner.

Where consolidations lose value

A consolidation sequence

1. Freeze deletion on both instances, following the retention guidance for acquired companies.
2. Record the inventory: instance owner, oldest ticket, ticket count by year, active versus archived, custom fields, connected tools and retention settings. No ticket content.
3. Check the entity that owns each instance and its customer contracts, using the entity map.
4. Map the schema: statuses, priorities, fields, tags and groups from the old tool to the new one, in a written table.
5. Run a sample migration and compare counts, threads and resolutions by hand.
6. Cut over and keep the old instance read-only for an agreed period.
7. Sign off: the support lead confirms resolution history is intact, and the decision is logged.

The same discipline applies to chat in Slack workspace merges and to engineering history in GitHub organization migrations.

Moving between vendors

Moving from one helpdesk to another, including from Freshdesk to Zendesk, is a field-mapping exercise. Check each vendor's current documentation and your migration tool for what it carries across, since limits on attachments, custom fields and history vary and change. Avoid assuming any tool preserves everything.

How a CX or MSP partner spots a company worth a conversation

• Several years of tickets, with closed tickets retained.
• Resolutions, categories or root-cause fields are used consistently.
• Tickets link to CRM accounts and engineering issues.
• More than one support system has been used, so archives exist.
• The company has 50+ full-time employees at peak (contractors excluded).
• An administrator can run exports, and an authorized sponsor exists.

Companies that fail on consumer-only data, client-owned data held for outsourced clients or deleted archives should be parked.

What to say to the client's support lead

Keep the request about process and counts. It also gives the support lead a reason to confirm that exports are possible and who runs them.

How the introduction and reward work

You can introduce a client through the managed service provider page, or by referral link so the company applies itself. SourceX handles qualification, inventory, pricing, buyer review, contracting and delivery, while you never handle ticket content.

Partners earn 25% of the eligible platform fees SourceX actually collects from the referred company's licensing deals, capped at $100,000 cumulative per referred company. The reward is payable only after the buyer pays and SourceX receives its fee, and no reward is guaranteed. Check your client agreements for conflicts first, and read the program terms.

Next step

Build the inventory for one client's support instance, then check fit with the company fit checker and the who qualifies page. If it fits, register as a partner. Investors can place this in context through value creation in longer holds.