How to switch help desk software without losing tickets

You already know your current help desk is wrong for you. What keeps you on it is the few thousand old tickets sitting inside it, plus a quiet fear that the day you switch help desk software, a customer email will land nowhere and nobody will notice for a week. Here is the short version. The technical part of a switch takes about an afternoon. The two weeks around it are all decisions, and the biggest decision is what you are going to leave behind.

Nearly every migration guide on the first page of Google is written for a support department. It assumes a project manager, a staging environment, a data owner and a vendor onboarding call. If your whole support team is you and one other person, that reads like somebody else's job.

We build support software for small teams, and we watch people move over from a shared Gmail, from Zendesk, from Freshdesk, from a mail rule somebody set up in 2019. The same handful of things go wrong every time, and they are almost never the things the enterprise checklists warn you about.

Signs it is actually time to move

Switching help desk software costs you a week of attention, so it should fix something real. These are the four reasons we hear that hold up:

• The bill grew faster than the team. A per-agent price that jumped, an add-on you now need, or a renewal quote with a number on it you did not expect.
• You use about six percent of it. Big platforms are built for departments. If half your admin screens are for roles you do not have, you are paying to look at them.
• Things fall through. Two people answering the same email, or nobody answering it, because the tool never made ownership obvious.
• You cannot get an answer out of it after hours. No help articles, no bot, no self-service, so every question waits for a human.

A reason that does not hold up on its own: you are bored of the interface. Retraining yourself costs more than a slightly ugly screen.

What it means to switch help desk software

Four things move when you switch help desk software, and only one of them is technical.

• Where customer email lands. A forwarding rule or an alias change. Ten minutes of work.
• Your saved replies and help articles. Copy and paste, or an import if the new tool offers one.
• Your old ticket history. The part everyone worries about most. Usually the part you should skip.
• Your own habits. New words for old things. What you called a ticket might now be a conversation, and what you called pending might now be closed.

Three of those four are decisions rather than engineering. That is why a job that sounds like a fortnight turns out to be an afternoon of clicking and a week of getting used to it.

The one question that decides your whole migration

Do you carry your ticket history over to the new help desk, or do you leave it where it is?

Every ranking guide assumes you carry it. Paid migration services exist to carry it and they charge by the record. Before you spend that money, answer one honest question: when did you last open a support ticket older than three months?

For most small businesses the answer is "I can't remember." Support history is like an old bank statement. You want to know it exists somewhere. You almost never read it.

Leave it behind when

• You mostly answer one-off questions from people who buy once or twice a year.
• Your old tool will let you keep a read-only or downgraded account, or hand you an export file.
• The data is messy. Half-used tags, three spellings of the same category, tickets closed by somebody who left in 2023. Importing that makes your new reporting useless on day one.
• You have more than a few thousand tickets and a migration quote to match.

Carry it over when

• You sell to named accounts and you genuinely reread old threads before replying.
• A warranty, contract or compliance reason means the correspondence has to stay searchable.
• Your ticket history is the only place your product bug reports live.

If you land somewhere in the middle, the compromise that works is to bring contacts plus the last twelve months of tickets and export everything older to a file in cloud storage. You keep the threads you might reread, without paying to carry six years of "has this shipped yet."

A two week plan for switching help desk software

Week one: run both at the same time

Nothing here touches your live support. You are building the new setup next to the old one.

• Start a trial and add everyone who answers customers, not only yourself.
• Forward a copy of incoming mail so the new tool starts filling up while the old one keeps working normally.
• Rebuild your ten most-used saved replies. Ten covers most of a normal week. Do not try to port a hundred.
• Answer a few real questions in the new tool alongside the old one, so the awkwardness happens while there is a safety net.

Then write the audit list, which is the step people skip and regret. Put down every single place a customer can reach you:

• The support address printed on your website
• Old aliases that still forward, like info@, hello@, or the founder's personal address
• Your website contact form
• The chat widget
• The address in invoices and email signatures
• App store or marketplace listings
• Social messages and reviews you reply to

You will find one you had forgotten. Everyone does. Finding it in week one costs nothing. Finding it in week four costs you a customer who has been waiting nine days for a reply nobody ever saw.

Switch day: move the mail, then test it like a customer

Pick a quiet morning. Your old tool's reporting will show you which day of the week is slowest. Change the forwarding, then run three tests from an outside address rather than your own account:

1. Send a plain email to your support address and check it arrives as a ticket.
2. Submit your own website contact form.
3. Open the chat widget on the live site and ask something.

Now reply to one of those tests and read what the customer receives. Check the from address, check the signature, and check that hitting reply comes back to the right place. A reply that arrives from a no-reply address is the single most common thing to get wrong on day one.

Week two: leave the old system switched on

Do not cancel anything yet. Conversations that started before switch day keep landing in the old help desk for a week or two, because customers reply to the last message in their inbox. Open it once a day, finish what is in there, and close the account only after a full day passes with nothing new. One extra month on the old plan is cheap insurance.

Move your help articles before you move your tickets

Old tickets just sit there. Help articles do work. If you have written anything up, that is the first thing to bring across and the last thing to rush.

The reason is what a modern help desk does with articles. In SupportifyGPT, rules search the articles your business has published, then a model writes a plain reply using what it found. It answers out of your own words or it says it does not know, so it cannot invent a refund policy you never wrote down. An empty knowledge base makes that bot useless. A decent one makes it the thing that answers questions at eleven on a Sunday night.

Bring across whatever you have and tidy it as you go. If you are starting from nothing, read your last fifty replies and write up the five questions you clearly answer over and over. Our guide to writing a knowledge base article covers the format. The same articles can also be published as a public help center on your own domain, so one piece of writing serves your customers and your bot at once.

What to tell your customers

Usually nothing. If your support address stays the same, the switch is invisible from outside. That is the goal.

Say something only if a customer will see a difference:

• The address they write to has changed
• They had a login to a customer portal
• Old help links are going to break

If any of those apply, one short email a week beforehand is plenty. Nobody wants an announcement about your internal tooling.

The costs nobody puts in the plan

Three real costs show up in a switch, and only one of them appears on a pricing page.

• Overlap. You pay for both tools for a month. On SupportifyGPT that overlap is $15 on the Starter plan, which is less than most people spend on coffee in a week.
• Migration services. If you are using a paid record-by-record importer, get the quote before you decide to move history. It often comes to more than a year of the new tool.
• Your own hours. Rebuilding replies and testing takes a day of real attention. Book it rather than squeezing it between tickets.

Watch for the charges that appear after you sign, too. Per-resolution fees on bot answers, a price jump the moment you add a third person, a setup charge for onboarding. Our post on the hidden costs of help desk software lists the ones that catch people out. SupportifyGPT is $15, $39 or $79 a month, the plans differ only in how many seats you get, and every feature is on every plan, including the bot, the live chat widget and the help center. No per-answer fees, no setup charge.

Five things that go wrong

1. A forgotten forwarding address. The audit list fixes this and nothing else will.
2. Nobody tests the outgoing reply. Send one to yourself before you go live and read it as a customer would.
3. The old account gets cancelled too early. Give it a month past switch day.
4. Dirty data goes in. Six years of inconsistent tags will poison your new reports before you have a single week of clean ones.
5. The date is wrong. Switching the week before a sale, a launch or a holiday turns a small problem into a bad one.

If you are still choosing rather than moving, start with how to choose help desk software, and for an outside view there is a general overview written for small business owners. When you are ready to try the move, start a 14 day trial and run it beside whatever you have now for a week. Running both is what makes the switch boring, and boring is what you want.