Help Desk Software Migration Data 2026: Switching Costs, Timelines, and Hidden Fees by Vendor
Real switching-cost data for Zendesk, Freshdesk, Help Scout, Intercom, Zoho Desk, and Gorgias: entry and mid-tier pricing, migration timelines, retraining dip, and what actually transfers when you switch.
Is it right for you?
- Export tickets, contacts, and knowledge base articles from the source platform before you start configuring the new one, most vendors let you do this without opening a support ticket
- Screenshot or export every trigger, automation, SLA policy, and macro from the old system; none of the vendors below migrate these automatically
- Set a specific cutover date and a low-volume window (Tuesday mornings are typically the lowest-volume period for B2B support teams) rather than letting parallel running drag on indefinitely
- Budget 20-30% reduced agent throughput for the first 2-4 weeks after cutover and communicate that internally so it is not mistaken for a failed migration
- Keep the old platform live and paid (read-only if possible) for 30 days after cutover as a fallback for anything missed in the export
Quick verdict
Data migration is rarely the real cost of switching help desks. It takes a few hours to a few days for most vendors. The money and time actually go into three places: rebuilding automations and SLA rules that never transfer cleanly, the 20-30% productivity dip while agents relearn muscle memory, and however long you choose to run both systems in parallel. Budget one to two weeks end to end for a small team under 10 agents, three to six weeks for a 20-50 agent team with real automation depth, and treat any vendor quote that only mentions "data import" as incomplete. If your only reason to switch is a mild UI preference, the retraining cost alone will usually outweigh the gain; if you have hit a concrete wall (reporting, routing, or a pricing tier that no longer makes sense), the numbers below should tell you what to budget for the move itself.
Why this page exists
I pulled this together after writing individual migration sections across a dozen help desk comparison guides on this site and noticing the same numbers kept resurfacing in different combinations: a 1-5 day data export, a 2-4 week retraining window, a 20-30% productivity dip. Nobody had put those pieces next to actual vendor pricing in one table. That is what this page does.
The pricing below reflects each vendor's published plans as of mid-July 2026, checked directly against the live pricing pages. The migration and retraining figures come from patterns documented across real customer accounts and support-team workflows referenced throughout this site's vendor-specific guides, not vendor marketing claims. Where a vendor's own numbers changed since we last checked, I have flagged it below the table rather than quietly overwriting the old figure.
Master comparison: pricing, trial length, and migration support by vendor
| Vendor | Entry price | Mid-tier price | Pricing model | Free trial | Migration support | Typical migration timeline |
|---|---|---|---|---|---|---|
| Zendesk | $55/agent/mo (Suite Team) | $115/agent/mo (Suite Professional) | Per agent | 14 days | Built-in importers; paid professional services for SLA/custom-field mapping | 2-4 weeks (small team); 3-6 weeks with rule rebuild at 20-50 agents |
| Freshdesk | $19/agent/mo (Growth) | $55/agent/mo (Pro) | Per agent | 14 days (Enterprise trial), or a 6-month 1-2 agent freemium | Dedicated Zendesk import tool; free migration assistance on lower tiers | 1-3 days for data; 1-2 weeks parallel for a small team |
| Help Scout | $25/user/mo (Standard) | $45/user/mo (Plus) | Per user | 15 days | Free import tool plus documentation; API export for third-party movers | 1-3 days for data; 1-2 weeks parallel |
| Intercom | ~$39/seat/mo historically published; current site shows custom quotes only | ~$85-99/seat/mo historically; plus $0.99 per Fin AI resolution | Per seat + usage-based AI resolutions | 14 days | Self-serve JSON export; paid onboarding for complex routing | 1-3 days for data; 2-4 weeks parallel, longer with complex routing |
| Zoho Desk | $14/agent/mo (Standard) | $23/agent/mo (Professional) | Per agent | 15 days | Free Zwitch tool, pulls directly from Help Scout, Zendesk, and Freshdesk | 1-2 days for export; 1-2 weeks parallel, up to a month for complex 50-agent accounts |
| Gorgias | $10/mo (50 tickets, unlimited agents) | $360/mo (2,000 tickets) | Ticket volume, not per agent | 7 days | Shopify-native order sync; CSV export plus third-party movers for non-Shopify data | Export is near-instant; 2-4 hours to audit macros; 2-week parallel typical |
A few notes on where the live pricing pages disagreed with what had previously been documented on this site, worth flagging because it means some of our other vendor-specific pages need a refresh too. Zendesk's Suite Team plan is $55/agent/month, not the $25 figure that appeared in one of our Freshdesk-alternatives comparisons; $25 looks like a stale carryover from an older promotional rate. Freshdesk has quietly raised prices across the board since we last checked: Growth moved from $15 to $19/agent/month and Pro moved from $49 to $55, both about a 13-27% increase depending on tier. Help Scout's Plus tier is now $45/user/month; earlier drafts on this site had that figure anywhere between $44 and $65, so $45 is the number to trust going forward. Intercom is the biggest change: the live pricing page no longer publishes flat per-seat numbers at all. Pricing is now built around Fin AI resolution volume plus a custom seat quote, which means anyone quoting a fixed Intercom monthly price today is working from an old plan structure. Zoho Desk's pricing page auto-redirected to Indian rupee pricing during this check and did not expose a USD toggle in the fetched content, so the $14/$23 figures here are carried over from previously verified data rather than freshly confirmed; treat those two numbers as the least certain in the table. Gorgias's pricing page is now fully JavaScript-rendered with no plan numbers in the static page, so the $10/$360 figures are likewise carried over rather than freshly verified, and they conflict with an older figure elsewhere on this site that listed a $250/month tier for 2,000 tickets. Until we can confirm Gorgias and Zoho Desk pricing through a rendered page or a signup flow, treat those two rows as directionally correct but not gospel.
The two costs everyone forgets: retraining and parallel overlap
Every migration plan I have seen budgets for the data move and skips the two costs that actually determine whether the switch feels smooth or chaotic.
The first is agent retraining. Getting a team back to its previous productivity level after a platform switch typically takes 2-4 weeks, and during that window throughput usually drops by 20-30%. For a 10-agent team at an average fully-loaded agent cost, that dip works out to roughly $3,000-8,000 in reduced output, money that never shows up on a vendor invoice but is real all the same. Weigh that number against whatever the new platform is supposed to save you monthly, not against the sticker price difference alone. A team saving $500/month by switching but eating an $8,000 retraining hit needs 16 months just to break even.
The second is parallel-run overlap, running both systems side by side before full cutover. Most vendors in the table above land in a 1-2 week window for a small team and 2-4 weeks for a team with complex routing or 20+ agents. The purpose is not redundancy for its own sake, it surfaces the things a demo never shows: webhook integrations with Slack or Salesforce that need reconfiguring, email routing that behaves differently under load, agents who rely on keyboard shortcuts the new tool does not have. The mistake I see most often is not skipping the parallel period, it is letting it drag on past the planned window. An open-ended overlap creates confusion about which system is authoritative for a given ticket, and it tends to extend far longer than intended once nobody owns the decision to cut over. Pick a date, put it on the calendar, and treat the parallel window as a fixed test period rather than a safety blanket.
What transfers cleanly and what you have to rebuild by hand
Across every vendor in this comparison, the pattern is consistent enough to state as a rule. Tickets, contacts, and knowledge base articles move reasonably well, whether through a native importer, a CSV export, or a third-party service like Help Desk Migration. Those are the parts vendors advertise, and they are genuinely the easy part.
Automations, triggers, and SLA policies almost never transfer. Every platform structures its rules engine differently, so even a like-for-like automation has to be rebuilt in the new tool's syntax rather than imported. The same is true of macros that pull in dynamic data, a Gorgias macro referencing a Shopify liquid variable or a Zendesk trigger tied to a custom field both need to be recreated by hand, not copied over.
Custom fields and ticket forms need manual field mapping, this is usually where a migration timeline slips, because nobody notices the mismatch until a test import comes back with blank or misfiled data.
Analytics and reporting history is the one that catches teams off guard. Response-time metrics, resolution stats, and CSAT survey context typically stay locked in the old platform and do not migrate at all. If you need historical reporting for the record, export whatever CSV reports you rely on before the old subscription lapses, because access usually ends the day billing does.
Integrations and webhooks (Slack, Salesforce, CRM connectors) need to be reconnected and re-authorized on the new platform, they do not carry over automatically even when both old and new tools support the same integration.
One more item worth planning for if support content lives in a public knowledge base: article URLs usually change when you switch platforms, so set up redirects to protect the SEO value of that content and avoid breaking any in-product help links that point to specific articles.
Migration FAQ
What is the real cost of switching help desks, beyond the subscription price? The subscription difference is almost never the deciding number. The real cost is the 20-30% productivity dip during the 2-4 week agent retraining period, which for a 10-agent team typically works out to $3,000-8,000 in reduced throughput, plus however many weeks you run both systems in parallel. Data migration itself is usually the cheapest and fastest part of the whole process.
How long does help desk data migration actually take? For the data itself, tickets, contacts, and knowledge base articles, most vendors complete this in a few hours to a few days depending on volume. The number that stretches the timeline is not the data move, it is rebuilding automations, SLA rules, and custom field mappings, which can add one to four weeks depending on how much configuration the old system had.
Do automations and SLA rules migrate automatically to a new help desk? No, not with any vendor in this comparison. Tickets and contacts move through native importers or CSV/API exports reasonably well. Automations, triggers, SLA policies, and macros with dynamic variables have to be manually recreated in the new platform's own rules engine, because no two vendors structure their automation logic the same way.
Is a cheaper help desk always worth switching to? Only if the price gap is large enough to absorb the migration and retraining cost within a reasonable payback window, and only if you have hit a concrete limitation (reporting depth, routing complexity, a pricing tier you have outgrown) rather than a general sense that something better exists. A team saving a few hundred dollars a month can easily spend more than that in retraining dip alone; run the actual numbers from the table above before committing.