Skip to content

Helpdesk migration

Adrià Castany 2 min

What is a helpdesk migration?

A helpdesk migration is the move from the tool a company uses to serve its customers to a different one, taking along what is needed to keep working. That covers conversation history, customers, the knowledge base, saved replies, rules and integrations.

Also called

help desk migration, ticket migration, switching support tools

Topic
Support concepts
On this page
  1. Why it matters
  2. What gets migrated and what does not
  3. The phases of a migration
  4. Switch-over day
  5. What tends to go wrong
  6. How Intake handles it
  7. Frequently asked questions

Why it matters

The risk in a migration lies in what the customer notices.

An open conversation that gets lost, an email that stops arriving or an agent who cannot see the history turn into a bad experience just as the team is learning the new tool. That is why the plan is built around switch-over day.

What gets migrated and what does not

Not everything is worth the trip, and deciding beforehand shortens the migration.

WhatUsually migratedWorth reviewing first
Customers and companiesYes, in fullDuplicates and unused fields
Open conversationsYes, or closed in the old toolWho owns them
Closed historyThe period people look upWhat law or contract says to keep
Knowledge baseYesOut-of-date articles
Saved replies and rulesRebuiltWhich are still in use

The phases of a migration

A migration runs in six phases, and the third is the one most often skipped.

  • Inventory. What is in the current tool and what is used.
  • Set-up. Channels, teams, hours and permissions in the new one.
  • Trial. A test import and a small group working in it.
  • Training. The team practises on cases before the switch.
  • Switch-over. Channels are redirected on a low-volume day.
  • Overlap. The old tool stays available to look things up for a while.

Switch-over day

On switch-over day email, chat and the other channels are redirected, and each is checked with a test message.

It is worth having written down how to roll back and who decides.

What tends to go wrong

Three failures keep recurring in migrations.

  • Rules and automatic replies left active in both tools.
  • Integrations nobody remembered that stop receiving data.
  • Reports that cannot be compared because metrics are calculated differently.

How Intake handles it

Frequently asked questions

How long does a helpdesk migration take?

It depends on data volume, the number of channels and the integrations. What stretches the timeline most is deciding what to migrate and rebuilding rules, more than moving the data.

Does all the history need to be migrated?

Not always. Migrate what the team looks up to serve customers and what has to be kept by law or contract. The rest can be exported and archived outside the tool.

Do customers notice the change of tool?

They should not. Email addresses and channels stay the same, and what changes is where the team works. If something does change for customers, such as how the chat looks, tell them beforehand.

When is a good time to migrate?

In the quietest season and away from a launch or a year-end close. The team needs a few weeks to work fluently in the new tool.

Glossary

Keep reading

Glossary

Related terms

See the full glossary

Add it without dropping what you use

15 minutes, no commitment