Help Desk Software Migration Data 2026: Switching Costs, Timelines, and Hidden Fees by Vendor
Planning examples for Zendesk, Freshdesk, Help Scout, Intercom, Zoho Desk and Gorgias: vendor pricing snapshots, migration tasks, retraining assumptions and cutover costs to estimate for your own team.
Is it right for you?
Your checks are saved on this device only — they reset if you clear browser data or switch devices.
Why this page exists
This page puts vendor pricing snapshots beside migration tasks and illustrative budgeting assumptions. The example timelines and throughput reductions are not a dataset of measured customer migrations; estimate and validate them for the actual records, workflows and team.
The pricing table retains the vendor-plan snapshot discussed below. Migration and retraining durations are illustrative planning scenarios, not verified patterns across real customer accounts. Recheck current vendor pricing and migration support, run a test import, and replace the assumptions with the results of your own pilot before approving a budget.
Master comparison: pricing, trial length, and migration support by vendor
| Vendor | Entry price | Mid-tier price | Pricing model | Free trial | Migration support | Illustrative timeline to validate |
|---|---|---|---|---|---|---|
| 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 | $29/seat/mo (Essential) | $85/seat/mo (Advanced); 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 planning example |
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 republished flat per-seat pricing after a period of quote-only sales: Essential is $29/seat/month, Advanced $85, and Expert $132, plus $0.99 per Fin AI resolution on top, so a fixed Intercom monthly price is knowable again as of this check. 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
Include agent retraining and the cost of running both subscriptions in the migration budget, alongside record export and import. Estimate those costs for the actual team and cutover plan.
The first is agent retraining. As an illustration, assume ten agents cost $5,000 each per month, a four-week retraining period approximated as one month, and a 20% throughput reduction. The estimated lost-output value is 10 × $5,000 × 20% = $10,000, not a vendor charge or measured cash loss. At $500 in monthly savings, that illustrative amount alone takes 20 months to offset. Substitute actual labor costs, pilot throughput and retraining duration; no universal 20-30% dip or $3,000-8,000 loss is established here.
The second is parallel-run overlap, running both systems side by side before full cutover. For planning, compare a one- to two-week overlap scenario with a two- to four-week scenario for more complex routing; these are assumptions to validate, not observed completion times for the listed vendors. 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. Define the criteria for ending the parallel period and assign someone to approve the cutover, so overlap does not continue without a decision. 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, not 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 does it actually cost to move off your current help desk?
Build the budget from record transfer, configuration, training time and duplicate subscription charges. The numerical scenario above uses a 50,000-dollar monthly team cost and assumes output falls by one fifth for a month, yielding a modeled 10,000-dollar output loss. This is a hypothetical case rather than an account-level dataset; use your pilot and payroll figures instead.
How long does help desk data migration actually take?
Ask for a schedule based on ticket volume, attached files, field mappings and rule complexity. Treat each duration in the comparison as an estimate to test. Complete a trial transfer, reconcile the results and confirm the cutover requirements before setting a deadline.
Will my existing workflow rules carry over to a new help desk on their own?
No vendor covered here handles that step automatically. Tickets and contacts move through native importers or CSV/API exports reasonably well. Trigger logic, SLA policies, and any macro referencing variable data all 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 switching cost within a reasonable payback window, and only if you've run into an actual limitation (reporting depth, routing complexity, a pricing tier you have outgrown), not just 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.