Helpdesk Migration Checklist: Keep Support Running
Back to all insights
Customer Support

Helpdesk Migration Checklist: Keep Support Running

Changing helpdesk software should not leave a customer wondering why their reply disappeared. The difficult part is preserving the conversation and the team’s next action while new messages continue arriving. A clean import count can hide broken threading, exposed internal notes, or tickets assigned to former employees.

Quick answer: Inventory every incoming channel, map ticket states and owners, pilot difficult conversations, rebuild routing and replies, then switch traffic through a documented cutover. Verify a real customer reply end to end before retiring the old inbox.

1. Map every route into the support queue

List support addresses, contact forms, chat widgets, social channels, ecommerce integrations, and any automated system that opens tickets. Record who controls each route and whether it forwards mail, calls an integration, or writes directly to the helpdesk. An address printed on old invoices still matters even if it rarely receives messages.

Separate historical records from live traffic. You may be able to archive old closed tickets while moving every unresolved case. Define how an agent will find an archived answer without switching between unrestricted accounts. For wider data preparation, use the CRM migration checklist; the support-specific work here is channel continuity and conversation handling.

2. Translate support behavior, not just field names

Create a map for status, priority, queue, assignee, customer identity, tags, attachments, and internal notes. “Pending” may mean waiting for a customer in one tool and waiting for an agent in another. Write the operational meaning beside each source value before deciding the destination.

Example support migration acceptance map
Record or ruleDestination decisionPass condition
Open refund caseRefund queue and active ownerAppears in the correct working queue
Internal notePrivate conversation noteNot visible in a customer reply
Customer attachmentSupported ticket attachmentAgent can open the original file
Automatic acknowledgementOne active ruleCustomer receives one acknowledgement

3. Pilot conversations with awkward histories

Include a long thread, a reopened case, two customers with similar names, a forwarded email, an attachment, and a ticket with private notes. Ask an agent to find the issue, explain its current state, and draft the next reply. A demonstration using newly created tickets cannot prove that imported history is usable.

As one vendor-specific example, Help Scout’s import guide recommends a sample migration and preparation of users and inboxes. Its options depend on the source system. Request a written list of what your chosen importer preserves, transforms, or omits.

4. Rebuild the pieces an import may not move

Saved replies, assignment rules, service targets, business hours, and knowledge-base links need their own checklist. Review the most-used replies for obsolete URLs or promises. Test automation in a controlled queue so an imported batch does not generate customer notifications or apply the wrong priority.

Have one person own the final version of each rule. Running equivalent workflows in both systems can create duplicate acknowledgements or competing assignments. Compare the capabilities you need with the Help Scout review or Gorgias review, then verify current plan entitlements with the provider.

5. Switch live traffic with a clear handover

Choose a quieter period and publish a short runbook: when agents stop editing the source, who changes each route, where new enquiries should arrive, and what happens to replies to old threads. Follow the importer’s prescribed sequence because incremental imports and final copies do not behave identically.

Send a controlled enquiry through every channel and reply from an external test account. Confirm threading, sender identity, attachments, and visibility in the destination. Keep an incident owner available. If a route fails, pause that route and use the agreed fallback rather than letting agents improvise across two active queues.

6. Sign off on outstanding work and operating costs

Reconcile unresolved tickets by queue and age, not just total historical records. Review unassigned items, reopened cases, and messages received during the switch. Give the team a short guide explaining how to search old history and escalate a missing conversation.

Include overlap subscriptions, migration assistance, training, and rebuilt integrations in the budget. Keep an appropriately restricted source archive until acceptance checks pass. The first week’s success measure is whether every customer needing a reply still has an accountable owner, not whether the old subscription was cancelled quickly.

Helpdesk Migration Checklist FAQs

Can you migrate only open support tickets?

Often this is a reasonable scope, but confirm the importer supports it and that agents can still consult relevant closed history. Document where the archive lives.

Will old customer replies reach the new helpdesk?

That depends on email routing and how the systems handle existing threads. Test a reply to an old conversation rather than assuming new-ticket tests cover it.

When is a helpdesk migration complete?

When live channels, unresolved queues, access controls, and representative conversation histories pass the agreed checks, and the team knows how to handle exceptions.

Next step: Start with a channel map and one difficult ticket sample. Then compare customer service software offers against the support workflow you need to preserve.