Help Desk Vendor Lock-In 2026: How to Minimize It (with the Help Desk Playbook)

SaaS vendor lock-in is a reality for every modern company. Any software contract creates some degree of dependency — and that's perfectly normal.

The real question isn’t how to avoid SaaS vendor lock-in. It’s how much of an exit tax you'd be slapped with if you decided to leave. In sticky categories like help desks, ITSM, and CRM, the cost routinely reaches up to 150–200% of annual contract value.

The good news is that the contractual, technical, and operational practices can help reduce help desk vendor lock-in. With 50,000+ migrations across 90+ platforms completed since 2016, we created this guide for CFOs, CIOs, CTOs, Heads of Procurement, and operational leaders across CX, IT, Sales, Marketing, and Finance who rely on these systems every day. It maps how lock-in develops across the SaaS stack, using help desk and ITSM platforms as the working example.

The 2026 SaaS Lock-In Tax in Seven Numbers (with Help Desk Specifics)

If you have time only for one section, let it be this one. These seven numbers capture the current state of SaaS vendor lock-in — from rising SaaS inflation and expanding software portfolios to the realities of help desk migration cost.

• SaaS inflation reached 11.4% year-over-year through January 2025, with the average SaaS price increase outpacing consumer inflation by around 322% (Vertice)
• Average SaaS spend per employee increased from $6,900 in 2023 to $9,200 in 2026, bringing the annual SaaS total cost for a 500-person company to roughly $4.5M, much of it concentrated in hard-to-replace systems (including help desks and ITSM platforms) (Vertice)
• 300+ applications is the average SaaS portfolio size of a mid-market company, with dependency created mostly by the SaaS sprawl concentrated in 10-15 strategic systems (Productiv)
• 1.5-2× annual contract value is a typical help desk switching cost for a mid-market support platform once expenses beyond the direct help desk migration cost are factored in (benchmarks from 2,000+ projects completed by Help Desk Migration)
• Hellman & Friedman and Permira took Zendesk private in a $10.2B deal in November 2022; the acquisition of Zendesk resulted in hardened list prices, stronger pressure toward suite-based packaging, and per-resolution pricing for AI agents (Zendesk)
• Intercom’s Fin AI pricing starts at $0.99 per resolved conversation on top of standard seat licenses, with the agent deeply tied to the provider’s data model — a canonical example of AI vendor lock-in and an approach adopted across major help desk platforms (Fin)
• Help Desk Migration platform supports migrations across 90+ help desk and ITSM solutions, including Zendesk, Freshdesk, Jira Service Management, ServiceNow, Salesforce Service Cloud, Intercom, Help Scout, HubSpot Service Hub, BMC Helix, Ivanti, Cherwell, and newer platforms like Chatwoot, DevRev, Enchant, and Accelo. (Help Desk Migration)

Now, let’s take a step back and start with the definition of vendor lock-in.

What Is SaaS Vendor Lock-In?

SaaS vendor lock-in happens when a company becomes so dependent on a software platform that switching to another solution becomes too difficult, expensive, or risky.

At first, lock-in rarely feels like a problem. A platform fits the budget, integrates well enough, and solves an immediate business need.

At some point, the platform becomes hard to leave — even when pricing changes, product direction shifts, or the tool no longer fits the company’s needs.

So, the earlier you notice SaaS vendor lock-in, the less the effect.

The five areas where every SaaS lock-in shows up

Vendor lock-in rarely stems from a single issue. In most cases, it builds gradually across several layers of the business at the same time.

These are the five areas where SaaS dependency becomes visible:

These same five layers explain why companies experience Salesforce lock-in and Workday lock-in differently. These platforms have different SaaS stickiness.

SaaS stickiness scale: where help desk and ITSM systems rank

Not every software product creates the same level of dependency, or “stickiness.” Some SaaS categories are less “sticky” and can be replaced relatively quickly, while others quickly strike deep roots in your system.

As you can see, help desks and ITSM platforms are the hardest to replace. And for good reason.

Why help desk vendor lock-in is harder than most

Help desk and ITSM platforms rank among the hardest SaaS categories to leave because all five lock-in layers tend to be deeply embedded at the same time.

Take the Zendesk lock-in:

• Contract — AI bundled into pricing plans
• Data — records, tickets, conversations, voice recordings, internal notes, multilingual knowledge bases, Zendesk AI training data, and data fields
• Integrations — deep connections with dozens of business applications through the Zendesk Marketplace
• Code — custom apps, workflows, agent roles, and other platform-specific configurations
• People — over time, teams adapt to Zendesk's interface, processes, and operation style

ITSM platforms take the challenge even further. Beyond ticketing, they serve as a central hub for managing IT operations, assets, and services, creating a dense web of data, automations, and integrations. Jira Service Management lock-in, for instance, is reinforced by deep ties to the broader Atlassian ecosystem, including Jira Software, Confluence, Bitbucket, and Compass. ServiceNow lock-in runs even deeper. Vendor-specific components like scoped applications, custom tables, and Now Assist require manual rebuild after migration.

Let’s explore help desk and ITSM platform dependencies in more detail.

Where Vendor Lock-In Hides (Nine SaaS Dependencies, with Help-Desk Specifics)

Quite a few teams underestimate the cost of switching platforms as they focus on data export. In reality, though, vendor lock-in extends far beyond data and is spread across nine dependency layers that vary in complexity and migration effort. The breakdown below doubles as a checklist for your help desk migration.

Records, transactions, and history (data)

Every SaaS platform accumulates business information over time: customer records, opportunities, invoices, audit logs, and time-series data. As datasets grow, SaaS data migration becomes increasingly complex.

In help desk and ITSM platforms, this dependency takes the form of ticket history, conversation threads, attachments, and other support records collected over years of customer interactions. A five-year-old support environment with 50 agents can easily contain more than 100 GB of data.

Moving that information is not always easy. Help desk API limits slow down ticket export, and data integrity issues add another layer of risk.

Fields and metadata (data)

Every SaaS platform has its own data structure. Field names, types, and underlying identifiers are often platform-specific. This is especially true for drop-downs, lookups, multi-selects, and formulas. Add custom fields created around your organization's unique processes, and SaaS schema migration becomes even more complex.

Ticket forms and contact custom fields are the number one cause of migration overruns in help desk projects. Even when the data itself can be transferred, differences in field structures and supported field types often create challenges during custom field migration.

Knowledge base and content (data)

Knowledge base content is a major source of help desk and ITSM platforms lock-in. And knowledge base migration gets overlooked the most during platform moves.

Zendesk, Freshdesk, and Fin all use different category structures and translation models. This makes knowledge base migration much more complex than a simple content export. A 500-article knowledge base available in four languages effectively becomes 2,000 articles, which must all be transferred and revalidated.

Custom automations (code)

Many SaaS platforms allow you to automate certain processes through custom code or no-code workflow builders. Over time, these automations become deeply embedded in daily operations, making SaaS workflow migration a major challenge when switching platforms.

Automated workflows are part of help desk platforms, but each approaches them differently. Salesforce uses Salesforce Apex and Flows. Workday relies on Studio and business processes. Zendesk uses triggers and macros. There is no clean cross-platform export for these workflows. Even when similar functionality exists, such automations usually need to be recreated in the destination system.

Integrations

Over time, organizations build SaaS integrations with CRMs, identity providers, communication tools, and other business systems, creating additional migration dependencies.

Help desk and ITSM platforms are no exception. Depending on your platform, you can extend its functionality through solutions at Zendesk Marketplace, Freshworks Marketplace, Salesforce AppExchange, and similar ecosystems. These integrations often have platform-specific settings and workflows that do not transfer automatically during migration.

SLA rules and other operational policies (layer: code)

Many SaaS platforms allow organizations to set service levels, business hours, escalations, and other operational policies. Over time, these rules become tightly connected to the way teams work, making SLA policy migration more complex than it first appears.

Help desk and ITSM platforms often approach policy management differently. Even when two systems support similar functionality, the underlying configuration rarely transfers directly between platforms.

CMDB, assets, and CI relationships (data)

This dependency is specific to ITSM platforms. CMDBs within ITSM tools maintain not just configuration items (CIs) but also the relationships between them. This makes CMDB migration much more demanding than moving incidents or users alone.

This single dependency is one of the main reasons enterprise ITSM migrations can take 4–9 months.

AI training data and model state (data)

This is the newest lock-in layer. Unlike records, workflows, or integrations, it barely existed as a migration concern in 2020. Today, however, AI training data ownership is becoming an important factor in long-term platform decisions.

Wherever vendor-native AI is in use, the model learns from your support interactions and knowledge base content within the vendor's environment. Switching providers often means starting the AI brain over. For example, a Fin AI data export may retrieve underlying support data, but not the learned behavior, configuration, or model state built over time.

Reports, dashboards, and KPI definitions (data)

While the underlying data can usually be migrated, reports, dashboards, and KPI calculations are typically rebuilt later rather than transferred during a SaaS reporting migration.

Help desk reporting migration is no exception since platforms calculate CSAT, First Contact Resolution (FCR), Mean Time to Resolution (MTTR), and other metrics differently. KPI definitions, too, may vary depending on the vendor.

User UI training and operational muscle memory (people)

Over time, teams develop habits around a platform's interface. Switching the software means changing those habits as well.

Support agents, managers, and administrators rely on familiar screens, reports, and workflows to do their jobs efficiently. This makes help desk training just as essential as the technical migration itself.

And the challenge is only growing. It's not just that organizations accumulate more data, workflows, and integrations as years pass. Market forces are reinforcing lock-in too — from AI features tied to proprietary data models to pricing strategies that make switching increasingly expensive. The next section looks at the trends driving this shift.

Why SaaS Lock-in Is Worse in 2026 vs. 2020

Vendor lock-in is not a new problem. What has changed is the number of factors making it worse.

The five structural shifts hit the help desk and ITSM users especially hard. CFOs and CIOs should keep them in mind when adopting a new platform or going into another renewal cycle.

SaaS private-equity acquisitions have raised renewal pricing power

Hellman & Friedman and Permira's take-private of Zendesk is just one example of a broader trend. In recent years, major vendors across multiple categories have been acquired, including Anaplan ($10.4 billion, Thoma Bravo, 2022), Coupa ($8 billion, Thoma Bravo, 2023), Avalara ($8.4 billion, Vista, 2022), and Citrix ($16.5 billion, Vista and Elliott, 2022).

Such rollups usually translate into suite-first pricing models, reduced flexibility in plan selection, and double-digit renewal increases.

Point pricing is giving way to SaaS suite-bundling

Software vendors are increasingly moving away from standalone products and toward bundled platforms.

Salesforce, for example, now offers its service platforms along with its sales and marketing products, starting from the lowest pricing tier. HubSpot Service Hub has long been sold together with other products by the same provider, while Microsoft continues to bundle Copilot into its Microsoft 365 ecosystem.

The impact goes beyond pricing. Bundles increase ACV while locking multiple surfaces in.

AI is being priced and packaged as deep-lock-in by design

Today, many vendors position AI as an add-on layered directly on top of their platform. Examples include Zendesk Advanced AI, ServiceNow Now Assist, Freshworks Freddy AI, Fin's AI, Salesforce Agentforce, and Microsoft Copilot.

The challenge is not just the additional spend typically stemming from AI’s usage-based pricing. These systems learn from your tickets, conversations, knowledge base content, and workflows inside the vendor's environment. Switching platforms means rebuilding AI workflows, retraining assistants, and recreating the context accumulated over years of use.

As a result, AI lock-in is one of the strongest across SaaS.

Ecosystem stacks create integration dependencies

SaaS ecosystem lock-in is the plague of the modern software market, focused on stacks rather than standalone products. While these integrations create real value, they also increase switching costs, as replacing one application can affect workflows, reporting, automations, and data flows across several others.

SaaS renewal cycles are getting longer while buyer leverage shrinks

The average SaaS contract length for customer service and IT management software has reached 35 months, as vendors continue to push longer commitments.

Meanwhile, opt-out windows are becoming narrower and easier to miss. Combined with SaaS inflation, these longer commitments can significantly reduce customers’ negotiating leverage.

The flexibility that many buyers associated with SaaS a decade ago is becoming harder to hold onto. By 2026, the ability to "leave anytime" is often less about the contract per se and more about whether an organization negotiated that option in advance.

But longer contracts are only part of the story, as many of the biggest switching barriers are written directly into the agreement.

The Seven SaaS Contract Clauses That Create Lock-In (and How to Negotiate Them)

Vendor lock-in starts long before you begin using the software. It starts with the contract itself.

The seven clauses below appear across customer service, ITSM, CRM, and other enterprise software agreements. Knowing what they mean — and negotiating them upfront — can significantly cut down future switching costs.

Auto-renewal with shrinking opt-out windows

Most SaaS MSAs include a SaaS auto-renewal clause that automatically extends the contract unless the customer provides notice within a specified period. Zendesk and Freshdesk MSAs commonly require 60 days' notice, while ServiceNow contracts can require up to 90 days.

Negotiate the notice period down to 30 days in writing and set calendar reminders at least 120 days before renewal. Where possible, push for month-to-month renewals after the first contract year.

Annual price uplift caps

Following Vertice's reported 11.4% year-over-year SaaS inflation, annual SaaS price uplift clauses of 7–10% are now becoming the norm. For example, Zendesk Suite pricing increased by approximately 10–12% across the 2024–2026 period.

So, many businesses find themselves locked into a platform that grows more expensive year after year, while the cost of switching continues to rise.

AI usage-pricing bundling

AI help desk pricing is routinely layered on top of subscription plans. For example, Fin AI cost starts at $0.99 per resolution; Zendesk Advanced AI costs $50/agent/month plus per-resolution AI agents; ServiceNow Now Assist adds roughly 50–60% on top of fulfiller licenses; Freshworks Freddy AI Copilot costs $29/agent/month, and Agentforce pricing starts at $2 per conversation. This can strain your IT budget if you grow dependent on AI features.

To save on AI spend and make it more predictable, negotiate a monthly cap, request transparency into unit economics (e.g., cost per resolution), secure usage-data export rights, and avoid clauses that allow vendors to change AI pricing during the contract term.

API rate limits and data export fees

API throttling is a common form of soft lock-in across help desk platforms. SaaS data export at the scale of 100K–1M tickets is subject to API rate limits with virtually all major vendors. In addition, some providers charge data egress fees when exporting large volumes of information.

Negotiate an explicit data ownership clause, the right to perform free machine-readable exports at any time, inclusion of attachments in exported data, and retention of API access for at least 60 days after contract termination. Where possible, negotiate temporary increases to API export limits for migration projects.

Right-to-audit, SLA penalties, and security

Push for automatic SaaS SLA credits instead of manual credit claims. Also negotiate a SaaS audit clause and commitments around security questionnaires and certifications, including SOC 2 Type II, ISO 27001, HIPAA, or FedRAMP, where relevant. Request a 72-hour breach notification window and a Data Processing Addendum compliant with Article 28 of GDPR and the new EU AI Act provisions.

Mandatory professional services and 'success' attach

Some vendors will not sell higher-tier plans without additional SaaS professional services engagements. For example, ServiceNow implementation projects for ITSM Pro and Enterprise routinely require partner-led services totaling 1–2x the first-year license cost.

Negotiate a cap on professional services hours, the right to work with third-party implementation partners (such as Help Migration Desk, ScreenSteps, Premier Zendesk Partners, Atlassian Solution Partners, or Salesforce SI partners), and the removal of mandatory professional services packages at renewal.

Termination assistance and transition rights

The period immediately after contract termination is often when organizations most need access to their data. Without clear transition rights, migration can stall entirely.

Negotiate a SaaS termination clause that includes transition rights such as read-only access for 60–90 days after termination, free data export, no data deletion before written confirmation, the right to engage a third-party migration partner without breaching the DPA, and unrestricted use of API tokens during the transition period. Few clauses matter more at exit.

How to Prevent SaaS Lock-In Before You Sign (with Help-Desk Specifics)

Vendor lock-in isn't determined solely by the contract. Here are a few additional steps you can take to maintain flexibility over time.

Run a 30-day data portability test

Before signing, request a sandbox environment for a 30-day SaaS POC with your own data (1,000 tickets and related data, for example). Run a full export early in the evaluation and, on day 28, perform a re-import.

A help desk POC will show how easy it is to move your data in practice.

If the vendor cannot or will not support the process, that may be the lock-in you're signing up for.

Insist on machine-readable SaaS data export rights in the MSA

Make sure the agreement explicitly grants you the right to export your data at any time in industry-standard formats (JSON, CSV, ZIP for attachments). The clause should apply to all data — including AI logs and audit trails — and belong in the MSA itself, not just in a pricing addendum.

Prioritize help desk API integration over proprietary scripting

Salesforce Apex, ServiceNow scoped applications, Workday Studio, Zendesk Triggers, and Jira ScriptRunner are powerful tools, but they can increase vendor lock-in.

Pick AI as a layer

Vendor-native AI solutions such as Einstein AI, Now Assist, Zendesk AI, Freddy AI, Fin, and Agentforce compound in value the longer they are used — but they deepen AI vendor lock-in just as steadily.

Where AI is core to your operations, consider a model-agnostic AI approach: custom RAG implementation, third-party assistant, or OpenAI/Anthropic API connected to vendor-neutral data sources if possible.

Plan the exit on day one: write the 'switching runbook'

Before going live, document where each data type lives, which integrations are business-critical, who owns the export process, and what the 30-, 60-, and 90-day SaaS exit plan looks like.

For a help desk exit plan, also document macro and trigger naming conventions, the source of truth for knowledge base content, and any AI training data pipelines.

Review and update the switching runbook annually.

How to Walk Back Existing Lock-In

Even on a SaaS platform you’re already committed to, vendor lock-in can be partially unwound.

The six moves below can help cut future switching costs by 30–50% over the next 12 months and make your next migration a decision, not a crisis.

Standardize naming conventions across automations and workflows

Start with the highest-volume objects and expand the standard from there.

Move integrations behind your own iPaaS layer (Workato, Tray.io, Make, Zapier)

A direct connection between SaaS applications increases vendor lock-in. Routing those connections through an integration platform such as Workato, Tray.io, Make, or Zapier creates a lightweight abstraction layer that can survive future platform changes.

For help desk iPaaS strategies, the four integrations that benefit most from this layer are Salesforce, Slack, Jira, and telephony platforms such as Aircall, Talkdesk, and Five9.

Mirror knowledge in a vendor-neutral source of truth

To improve knowledge base portability, keep canonical content in Notion, Guru, or Confluence, then publish it to vendor-specific surfaces such as Zendesk Guide.

Export operational data to a help desk data warehouse monthly

Regularly export operational data to a SaaS data warehouse such as Snowflake, BigQuery, Redshift, or Databricks. Consider exporting ticket history, conversation logs, AI resolution data, and CMDB snapshots. Use integration tools like Fivetran and Hightouch or vendor APIs.

Even if you never migrate, you'll maintain years of historical data independent of vendor uptime, acquisitions, or pricing changes.

Treat AI training data as a portable asset

Wherever vendor AI is in use, store question-to-resolution pairs, prompts, and responses in a separate, neutral repository.

This strengthens AI training data ownership and improves AI portability over time.

Run a quarterly 'lock-in audit'

Conduct a vendor lock-in audit every quarter for your 10 most strategic applications. Score each dependency layer on a scale of 1–5 and create remediation actions for anything rated 4 or 5.

As part of a broader SaaS audit process, this helps identify growing dependencies before they become costly problems. Most teams can reduce their overall lock-in score by around 30% within 12 months. On help desk platforms specifically, reassess scores before renewal, while you still have negotiating leverage.

Vendor-by-Vendor Lock-In: How the Major Help Desk and ITSM Platforms Compare

As a help desk migration provider, we've seen vendor lock-in play out across thousands of projects. The seven platforms below account for roughly 80% of Help Desk Migration's work. Each has its own lock-in mechanisms, as well as a set of viable exit paths when the time comes to move on.

Zendesk

• Parent company / market position: Owned by Hellman & Friedman and Permira since 2022. One of the largest customer support platforms.
• Zendesk pricing in 2026: $19–$115 per agent/month, plus $50/agent/month for Copilot and per-resolution charges for AI Agents.
• Lock-in: Zendesk AI and automations, macros, Marketplace apps, Sunshine Conversations custom objects, and Explore reports.
• Switching to a Zendesk alternative: Migration Wizard for customer, agent, ticket, and other help desk data migration from Zendesk. Manual rebuilding of AI, automations, and dashboards.

Freshdesk

• Parent company / market position: Owned by Freshworks Inc. A leading help desk platform for SMB and mid-market teams.
• Freshworks pricing in 2026: $19–$89 per agent/month, plus Freddy AI Copilot at $29/agent/month and Freddy AI Agent usage fees.
• Lock-in: Freshworks Marketplace apps, Freddy AI training data, automations, custom objects, and reporting.
• Switching to a Freshdesk alternative: Freshdesk migration with Migration Wizard covers tickets, contacts, companies, and knowledge base content. AI, automations, and reports typically require rebuilding.

Jira Service Management

• Parent company / market position: Atlassian (NASDAQ: TEAM), a publicly traded software company and a leading ITSM platform.
• Jira Service Management pricing in 2026: From Free (up to 3 agents) to Premium at $51.42 per agent/month and beyond.
• Lock-in: ScriptRunner code, automation rules, Assets data, Marketplace apps, and the Atlassian ecosystem.
• Switching to Jira Service Management alternatives: Migration Wizard for Jira Service Management migrations to Zendesk, Freshdesk, and ServiceNow. Manual rebuilding of ScriptRunner code and Assets data.

ServiceNow

• Parent company / market position: ServiceNow (NYSE: NOW), one of the leading enterprise ITSM platforms.
• ServiceNow pricing in 2026: Public pricing is not available. Industry benchmarks place ITSM licenses at roughly $70–200+ per fulfiller/month, with Now Assist adding another 50–60%. ServiceNow TCO often reaches 3–5x license costs.
• Lock-in: Scoped applications, CMDB and CI relationships, Flow Designer, Now Assist skills, and IntegrationHub spokes.
• Switching to ServiceNow alternatives: The most complex among the major platforms. Migration Wizard for ticket-side data migration from ServiceNow. Manual rebuild for CMDB configurations and automations.

Intercom

• Parent company / market position: A prominent customer messaging and AI-powered support platform owned by Fin (formerly Intercom, Inc.)
• Intercom pricing in 2026: From $29 to $132/seat/month, plus the Fin AI cost ($0.99 per resolved conversation).
• Lock-in: the Fin AI training data, Inbox automations, and integrations with Salesforce, HubSpot, and Slack create deep dependencies over time.
• Switching to an Intercom alternative: Migration Wizard from Intercom migration to platforms such as Zendesk, Freshdesk, and Help Scout. Fin AI can be used outside the Intercom platform.

Salesforce Service Cloud

• Parent company / market position: Salesforce (NYSE: CRM), one of the largest CRM and customer service platforms.
• Salesforce Service Cloud pricing in 2026: Starter Suite $25, Pro Suite $100, Enterprise $175, Unlimited $350, and Agentforce 1 Service $550 per user/month. Agentforce Service Agent is priced separately at $2 per conversation plus platform fees.
• Lock-in: Apex code, Lightning components, deep CRM integration, and Einstein/Agentforce models trained on your organization's data.
• Switching to a Salesforce alternative: Salesforce Service Cloud migration benefits from mature export tools such as Data Loader and Bulk API. Customizations require rebuilding in the destination platform.

HubSpot Service Hub

• Parent company / market position: HubSpot (NYSE: HUBS), a leading CRM, marketing, sales, and customer service platform for growing businesses.
• HubSpot Service Hub pricing in 2026: From 0 to ≈$175/seat/month, plus the required paid onboarding service for Professional and Enterprise plans, plus $0.50 per conversation resolved by Breeze AI.
• Lock-in: Deep ties to HubSpot CRM, Marketing Hub, and Content Hub, HubSpot Marketplace, workflows, Breeze AI, Snippets, and knowledge base content.
• Switching to a HubSpot alternative: API-friendly export capabilities. Help Desk Migration supports HubSpot Service Hub migration to and from all major help desk and ITSM platforms, though workflows and platform-specific configurations require rebuilding.

Vendor lock-in depth varies by help desk platform. What doesn’t vary: at least part of the data can be migrated automatically with Help Desk Migration. Here’s how the typical migration project unfolds in this case.

How a Help Desk Migration Runs End-to-End (the Help Desk Migration Playbook)

No two migrations are identical, but the underlying process follows the same sequence. Below is the Help Desk Migration approach, which can serve as a reference point for any well-structured migration project.

1. Discovery and feasibility (free)

The process starts with a help desk migration assessment. The team reviews source and target platforms, estimates data volume, inventories integrations, and flags potential risks. Help Desk Migration also offers a free target platform feasibility assessment.

2. Demo migration (free)

Before committing to a full migration, run a help desk demo migration and transfer 20 sample records. You can do this through the Migration Wizard or with assistance from Help Desk Migration engineers.

3. Full migration

Once the setup is validated, the full migration can start. You can run it yourself through the Help Desk Migration Wizard or work with HDM engineers.

The platform migrates tickets, attachments, knowledge base articles, contacts, organizations, custom fields, and other records while handling data API throttling across 90+ help desk and ITSM platforms.

4. Delta migration

A delta migration of help desk data captures records created or updated after the full migration starts and syncs them to the destination platform.

5. Rebuild and validate

Some elements cannot be migrated automatically. These include automations, triggers, SLAs, dashboards, and other platform-specific configurations.

Help Desk Migration provides a validation framework, while the customer's administrators or implementation partner perform the post-help desk migration rebuilding and testing.

6. Cutover and parallel-run

As part of a help desk cutover plan, both systems typically run in parallel for 30–90 days. The old platform remains available for historical reference, while new tickets are handled in the new system.

Understanding the process is one thing. Understanding the true SaaS migration cost is another. Here's a worked example based on a typical Help Desk Migration project.

Worked example: 75-agent CX team migrating from Zendesk to Freshdesk

A real-world Zendesk to Freshdesk migration scenario based on a typical Help Desk Migration customer profile:

• 75 agents
• 370,000 tickets
• 5 years of history
• 12 integrations

Starting state and assumptions

License costs: $148.5K/year for Zendesk Suite Professional ($115/agent/month, annual billing) plus Advanced AI ($50/agent/month) for 75 agents.

Data volume:

• 370,000 historical tickets
• 11,000 macros and triggers
• Knowledge base in four languages
• 12 integrations (Salesforce, Slack, Jira, Aircall, Stripe, and others)

Zendesk renewal cost: Renewal due in 90 days with a 12% price increase.

Direct migration costs with the Help Desk Migration tool

• Data migrated: Users, tickets, attachments, knowledge base articles, internal notes, custom fields, and tags
• Customizations requested and additional options used: Agent matching, data filtering
• Features used: Delta migration

Estimated total cost: ~$5,000.

Indirect (internal) costs

This is where most CFOs’ estimates fall short.

• 60-day parallel run on Zendesk and Freshdesk: +$25K.
• Trigger / automation rebuild (75 hours dev): $15-25K.
• Agent training and dip in productivity: ~5-40K.

Total estimated internal cost of help desk migration: $80-120K.

12-month TCO comparison

Stay on Zendesk

• Current cost: $148.5K/year
• After 12% uplift: ~$166K/year

Switch to Freshdesk

• Freshdesk help desk TCO: ~$107K/year (75 × $55 × 12 months + Freddy AI Copilot at $29 × 75 × 12 months)
• Help Desk Migration: $5K
• Rebuild, training, and parallel-run costs: $80K–120K

Total year-one cost: $192K–232K.

Help desk migration ROI: The Freshdesk path becomes up to $20K–45K less in year two, with break-even reached around month 14.

Frequently Asked Questions (FAQ)

Written by

Taras Velychko

Product Manager, Help Desk Migration

Taras is leading product strategy at Help Desk Migration, specializing in UX/UI, business intelligence, and vendor partnerships. His data-driven approach has improved conversion rates by 50% while keeping the product simple and customer-focused.