Help desk migration: how to switch platforms without losing customer history

Most help desk migration guides assume you have an IT team and a project manager clearing six months for the switch. If you run support at a mid-sized ecommerce brand, you probably don't. Your agents can't stop answering customers for a week, and your ecommerce platform, whether that's Shopify, BigCommerce, or Salesforce Commerce Cloud, has to keep talking to whatever tool you pick. Peak season also gets a vote on when you're allowed to switch.

This guide walks through a help desk migration for that situation, from timing the switch around your sales calendar to the day you cut over and the month after.

What a help desk migration involves

A help desk migration is the move from one customer service platform to another. The data transfer gets most of the attention, but it's often the smaller part of the work. You're also moving workflows like routing rules, tags, macros, SLAs, and automations, and reconnecting integrations such as your commerce platform, returns tool, subscription app, and phone system. Your knowledge base or help center content has to come along too, and the people who've built habits around the old tool need time to build new ones.

When to schedule your migration

Changing support tools in the middle of peak is risky, so many retail and ecommerce teams avoid it between early November and the end of the holiday returns window in January. That leaves late winter through early fall as the practical window.

Work backward from your go-live date. A mid-sized team typically needs a few weeks for setup and integrations, a test import, a week or two of training, and a buffer before any promotion or product launch. Check your current contract's end date at the same time, because you'll want the old system available in read-only mode for a few weeks after go-live. If you're reading this in the fall, plan for a cutover after holiday returns settle down, and use the next few months to evaluate vendors and clean up your data. Our guide to preparing for CX software renewals can help you line the decision up with your contract dates.

Decide what history you need to keep

It's tempting to move everything. Before you do, ask what your team will use.

Your agents need enough history to recognize a returning customer and understand recent issues: past conversations, the channel they came in on, and the customer's contact details. They rarely need attachments from four years ago or the internal tags from a routing setup you're replacing. Your finance or legal team may have their own retention rules, so check those before you decide.

Most platforms can't import everything your old tool stored, so ask each vendor for specifics. Gladly imports historical conversations from platforms including Zendesk, Kustomer, Gorgias, and Freshdesk, with the import scoped alongside its implementation team, and groups them on each customer's timeline by email address. Those imports are text only, so images, recordings, and attachments don't come across, and imported history isn't included in reporting. Limits like these are common, which is why many teams keep a full export of the old system in storage for audits and year-over-year reporting.

If you're moving from a ticket-based tool to one organized around the customer, a customer's 30 separate tickets become one timeline, which makes duplicate records and missing email addresses show up fast. We cover the difference in ticket-based vs. customer-based CX platforms.

How to migrate your help desk, step by step

1. Audit what you have

Export a list of everything configured in your current help desk, from channels and phone numbers to routing rules, macros, automations, integrations, and user accounts. You'll find things nobody remembers building. Mark each one keep, rebuild, or retire.

2. Clean up your data before you move it

Apply the history scope you set above, then merge duplicate customer records, fix obviously broken email addresses, archive spam and test conversations, and deactivate accounts for agents who've left. Data problems are much cheaper to fix in the old system than after they've been imported into the new one.

3. Rebuild your workflows and knowledge base

Copying every rule one for one usually carries over the problems you're trying to leave. Start from the customer's reasons for contacting you, like order status, returns, sizing, damaged items, and subscription changes, and decide how each one should be handled in the new platform, including which ones AI should resolve and which should go to a person.

Give your knowledge base the same treatment. Moving the articles is the easy part. Rewriting the outdated ones and deciding which articles your AI should draw answers from takes longer, so start it early.

4. Connect your commerce stack

Agents who have to switch tabs to find an order slow down on every conversation. Connect your commerce platform first, then your returns, subscription, and shipping tools, and test that agents can see and act on orders without leaving the new platform.

5. Run a test import

Import a sample of historical data and have a few agents look up real customers to check that names, emails, and conversation history landed where you expected. Fix field mapping now, while it's still a small batch.

6. Train your team on real scenarios

Train on your top 10 contact reasons, using real past conversations, and have agents handle them end to end in the new tool. Pick one or two agents to act as go-to experts during the first few weeks.

7. Cut over and run a delta import

Phone numbers are the piece most likely to slip. If you're porting numbers to a new provider, start that process weeks before go-live, because carriers can take a while to move them.

On cutover day, pick a quiet day of the week, point your email forwarding, chat widget, phone numbers, and social accounts at the new platform, and keep the old system in read-only mode. If anything customers see is changing, like a support email address, a chat widget, or a phone menu, tell them before it changes. Then run a delta import to bring over anything that came in between your main import and go-live. Gladly's implementation team recommends importing history about two weeks before launch and running the delta import a couple of days after.

8. Watch the first 30 days closely

Track first response time, handle time, backlog, and CSAT daily for the first month, and compare them with the same period in the old system. Handle time often rises for a few weeks while agents learn the tool, so hold a quick weekly review to fix routing and workflow gaps as they show up.

Help desk migration checklist

• Go-live date set outside your peak season and major promotions

• Old contract end date checked, with time for read-only access after go-live

• Full export of the old system saved for reporting and audits

• History scope decided (what moves, what stays archived)

• Duplicate customers merged and bad email addresses fixed

• Configuration audit done, with each item marked keep, rebuild, or retire

• Workflows rebuilt around contact reasons

• Knowledge base articles reviewed and rewritten where needed

• Commerce platform, returns, and subscription integrations tested

• Test import checked by agents

• Agents trained on top contact reasons

• Phone number porting started weeks ahead

• Customers told about any changes they'll see

• Channels redirected and old system set to read-only

• Delta import completed after go-live

• Daily metrics review scheduled for the first 30 days

Common help desk migration mistakes

Migrating during or right before peak is the most expensive one. Even a smooth migration costs your team some speed for a few weeks, and November is the worst time to pay that cost.

Teams also go wrong treating the switch as an IT project. The people who know how your support should work are your CX leads and senior agents, so put them in charge of workflow decisions and bring in technical help for integrations and data.

Moving everything because you can slows setup down and clutters the new tool with old tags, dead macros, and years of attachments nobody opens.

And it's easy to forget the customer-facing pieces. Contact forms, help center links, auto-replies, and chat widgets on your site all need to point to the new platform, so walk through your website as a customer before go-live.

One more decision is worth making before you pick a tool: whether to keep organizing support around tickets at all.

Moving from tickets to a customer timeline

A lot of teams use a migration to change how support is organized, moving from ticket queues to one timeline per customer where every channel lands in the same conversation. Agents see the whole history when a repeat customer writes in, and the AI works from that same history.

That's how Gladly is built. Deckers moved its brands off a ticket-based system to Gladly and improved service levels by 40% within a month. Bryan Riter, Deckers' Director of Customer Care, said Gladly "took most of the implementation burden off our team by being extremely well planned and efficient."

KÜHL made the same move, and as of late 2025 its AI was resolving 79% of email conversations. Their old setup had been shaping how agents treated customers.

If you're comparing platforms alongside the migration, our roundups of Help Scout alternatives and Freshdesk alternatives are a good place to start. For the bigger picture, read about the disadvantages of ticket-based CX software.