Key takeaways
- Most migrations go wrong on channels, not data. A forwarding rule nobody changed, or a chat widget left on an old page, loses customers quietly for weeks.
- Don't move everything. Move open conversations, customer history you'll actually look up, and help content. Keep the old account read-only for the rest.
- Rebuild automations and saved replies from what you used in the last 90 days instead of copying years of clutter.
- Run both tools in parallel for a week, switch on a quiet weekday morning, and check every channel the same day.
- Tidio is our top pick for stores moving to a simpler setup because its channels, store integration and AI agent can be live within days, without an admin.
Nobody switches help desks for fun. You do it because the old one got too expensive, too complicated or too limited, and the new one promises to fix that. The new tool is rarely the problem. The move is.
The failure is almost never dramatic. Tickets don't vanish in a puff of smoke. Instead, an old contact form keeps sending emails to an inbox nobody watches, a saved reply quotes last year's returns window, and a customer who wrote twice gets two different answers. This guide is about avoiding that, with a four-week plan built for online stores.
Why help desk migrations go wrong
The same mistakes come up in almost every move:
- A forgotten channel. A second email address, a contact form, a Facebook page or an old chat widget still points at the old tool.
- Too much history moved, too little checked. Years of tickets imported, but the new tool shows them without attachments or in the wrong customer record.
- Automations copied blindly. Old rules that nobody understands fire in the new tool, or important ones are missed.
- Bad timing. A switch planned for "after the busy season" slips into the next busy season.
- Contract surprises. The old tool renews for a year because the notice period passed during the migration.
Each one is easy to prevent if you plan for it. Timing matters most: with Black Friday weeks away, autumn is the wrong moment to cut over. Use it to choose the tool and plan the move, then switch in January or February, when volume is low and the next peak is months away.
Step 1: Take inventory before you touch anything
List everything the current help desk does, in four groups. This document becomes your migration checklist.
| Group | What to list | Example |
|---|---|---|
| Channels | Every address, form, widget and social account that creates conversations | support@, returns@, contact form, chat widget, Instagram, WhatsApp |
| Integrations | Every connected tool | Store platform, reviews, returns app, Slack, CRM |
| Automations | Rules, triggers, saved replies, tags | Auto-tag "refund", route VIPs, 40 saved replies |
| Content | Help articles, FAQs, policies | 35 help center articles, returns policy |
Also note your contract's renewal date and notice period. Put the cancellation date in a calendar today.
Step 2: Decide what to move and what to leave
Moving everything feels safe. It usually isn't worth it.
| Data | Move it? | How |
|---|---|---|
| Open and pending conversations | Yes | Finish them in the old tool during parallel running, or import them |
| Customer contacts | Yes | Import, or let the store integration create them |
| Last 6 to 12 months of history | Often | Importer, export and API, or a migration service |
| Older history | Rarely | Keep the old account read-only, or keep an export file |
| Help content | Yes | Copy or import, then review every article |
| Automations and saved replies | Rebuild | Only what was used in the last 90 days |
| Reports | Export | Save key numbers as a baseline for comparison |
If you do import history, test with a small batch first. Check that message threads, attachments and customer matching look right before you import the rest.
Step 3: Rebuild the setup, don't copy it
A migration is the one time you get to clean house.
- Saved replies: export usage data, keep the 20 to 30 that were used, and rewrite them for current policies.
- Automations: recreate only the rules you can explain in one sentence. If nobody knows why a rule exists, leave it out and watch for a week.
- Tags: cut them to a short, agreed list, such as order status, returns, product question, payment, complaint and other.
- Help content: move it to wherever your new AI agent will read it, and update anything out of date. Your AI is only as good as this content.
Step 4: Connect channels and test each one
Set up every channel from your inventory in the new tool, then test it like a customer:
- Email: add forwarding from your support addresses and send a test from a personal account. Check that replies go out from your own address, not the vendor's.
- Chat widget: install it on a staging site or a single page first. Remove the old widget completely when you go live, so two never show at once.
- Social and messaging: reconnect Instagram, Messenger and WhatsApp. For WhatsApp, ask the new provider how your existing number is moved, because it can take extra steps.
- Store integration: open a test order and check that the new tool shows it next to the conversation.
- Forms: update every form that sends email to support, including old landing pages.
Step 5: Run both tools in parallel for a week
For about a week, new conversations arrive in the new tool while the team finishes open ones in the old one. During this week:
- check every channel daily for conversations in the wrong place;
- read AI transcripts if the new tool has an AI agent, and fix content gaps;
- note every place the team gets stuck, and fix it with a saved reply or a short how-to.
Step 6: Cut over on a quiet morning
Pick a Tuesday or Wednesday morning, never a Friday or a sale day. Then work through the list:
- Point the last email forwarding rules at the new tool.
- Remove the old chat widget everywhere.
- Set the old help desk to read-only and turn off its automations and auto-replies.
- Send a test through every channel and confirm it lands in the new inbox.
- Check again at the end of the day, and again a week later.
Step 7: Check the first 30 days
Compare first response time, resolution time and satisfaction with the baseline you exported. A dip in the first week is normal. A dip that lasts a month means something in the setup needs fixing, and the team usually knows what.
The best help desks to move to
These are the tools stores most often move to. We judged them on how quickly a small team can be fully live, how easily channels and store data connect, and how much rebuilding they need.
Tidio is the quickest move for a small or mid-size store. Website chat, email, Instagram, Messenger and WhatsApp connect from one settings area, the store integration brings order data into conversations, and Lyro learns from your help center and Q&A pairs so the AI covers repeat questions from the first day. There are no complex triggers or views to rebuild, just saved replies and a few Flows. Bigger brands can take the Premium plan, where Tidio's services team sets up the AI agent and its knowledge base for you, which removes much of the migration work.
Why we like it
- Channels, store data and AI agent live within days
- Little to rebuild; no admin needed
- Free plan for the parallel-running week
- Combines chat, tickets and social messages in one inbox
Watch out for
- Lyro conversations are billed by volume, so estimate your monthly use
- Teams coming from complex Zendesk setups will simplify some workflows rather than replicate them
Brands moving from a general help desk to one built for Shopify often choose Gorgias for its in-ticket order actions. Expect a proper project to rebuild rules and macros, and price your peak months, because Gorgias bills by ticket volume.
Why we like it
- Deep Shopify order actions in the ticket
- Retail-focused rules and macros
Watch out for
- Ticket-based pricing rises in busy months
- More setup than a chat-first tool
If you are moving because you have outgrown a smaller tool, Zendesk offers the routing, SLAs, multi-brand support and import tooling large teams need. Plan the move as a project with an owner, and budget for per-agent pricing and AI add-ons.
Why we like it
- Handles very large, complex setups
- Wide range of migration partners and APIs
Watch out for
- Long setup and ongoing admin
- Per-agent pricing with AI resolutions and copilot extra
Teams leaving another ticketing system often pick Freshdesk because tickets, SLAs and rules work in a familiar way, so agents need less retraining. It suits email-heavy stores that want to keep a classic help desk.
Why we like it
- Familiar ticketing model, less retraining
- Capable automation rules
Watch out for
- Store integrations come from marketplace apps
- AI copilot is a paid per-agent add-on
A four-week migration plan
| Week | Focus | Done when |
|---|---|---|
| 1 | Inventory, contract dates, decide what to move | The checklist is complete and the cancellation date is in the calendar |
| 2 | Set up the new tool, rebuild saved replies, import content and contacts | A test conversation works end to end |
| 3 | Connect and test every channel, parallel running starts | All channels land in the new inbox |
| 4 | Cut over, read-only old account, review | No conversations in the old tool for three days |
If you are still choosing where to move, read our guides to Zendesk alternatives for e-commerce and Gorgias alternatives for small stores, or start with a free Tidio account for the parallel-running week.
Frequently asked questions
Can I move my ticket history to a new help desk?
Usually yes. Most help desks offer an importer, an export from the old tool, an API, or support from a third-party migration service. Check that the export includes full message threads and attachments, not just ticket fields, and test with a small batch first.
How long does a help desk migration take?
For a small store with a few channels, two to four weeks including a week of parallel running. Larger teams with many automations, integrations and brands should plan for one to three months.
Will customers notice when I switch help desks?
They shouldn't, if you keep the same support email address, move the chat widget cleanly and reconnect social channels on the same day. The risk is in forgotten channels, such as an old contact form or a second email address.
Should I cancel my old help desk straight away?
No. Keep it read-only for one to three months so your team can look up old conversations, and check your contract's renewal date and notice period early, so you don't pay for another year by accident.