← Back to Blog
Zendesk Is Forcing 4 Migrations in 6 Months — Here's Your Escape Plan
·7 min read
Between June and December 2026, Zendesk is forcing four separate migrations on its customer base. Not optional upgrades. Not recommended updates. Mandatory changes to mission-critical support infrastructure, each with a hard deadline and no option to opt out.
For support teams already stretched thin, the prospect of four forced migrations in six months — while simultaneously dealing with unpredictable outcome-based pricing — is pushing many to ask whether staying on Zendesk is worth the disruption.
Here's the full timeline, what each migration means for your team, and a practical plan for switching to something simpler before the deadlines hit.
The Four Forced Migration Deadlines
Migration #1: June 12, 2026 — Relate Changes Begin Rolling Out
The first wave of changes announced at Zendesk Relate 2026 starts rolling out. This includes:
- Forethought AI Agents replacing the existing AI framework
- Outcome-based pricing activation for new AI features
- Admin Copilot, Action Builder, and App Builder deployments
- Knowledge Connectors and voice AI expansion
Impact: Workflows built around the current AI setup may break or behave differently. Teams that relied on the old Essential AI tier pricing now face the optional $50/agent/month Copilot add-on plus per-resolution charges of $1.50 committed or $2.00 pay-as-you-go per automated resolution (zendesk.com/pricing, read 17 Oct 2026).
Migration #2: June 30, 2026 — CCs and Followers Forced Migration
All legacy CC (carbon copy) accounts are auto-migrated to the new CCs and followers experience. This changes how email notifications work on tickets — who gets copied, how followers are managed, and how reply threading behaves.
- All legacy accounts auto-migrated with no opt-out
- Email notification behavior changes for existing tickets
- Workflow automations that depend on CC behavior may need updating
- Custom triggers referencing the old CC model may break
Impact: This sounds minor until you realize how many teams built workflows around CC behavior. Automated ticket routing, escalation rules, and notification chains that depend on CC functionality all need testing and potentially rebuilding.
Migration #3: August 31, 2026 — Legacy AI Development Stops
Zendesk stops all development on legacy AI agents. No new features, no bug fixes, no security patches.
- Legacy AI enters maintenance-only mode (and even that's generous — no bug fixes)
- Any issues discovered after this date won't be fixed
- New Zendesk features will only work with the new AI stack
- Integration compatibility with legacy AI may degrade as other Zendesk components update
Impact: Teams still running legacy AI after August 31 are on borrowed time. The system won't improve, bugs won't be fixed, and the gap between legacy and new capabilities will widen every week.
Migration #4: December 10, 2026 — Legacy AI Shut Off
The final deadline. Legacy AI services are completely turned off. Every Zendesk customer must be on the new Forethought AI stack by this date.
- Legacy AI agents stop working entirely
- All customers forced onto the new pricing model
- No grandfather clause announced
- Teams that haven't migrated will lose AI functionality overnight
Impact: This is the hard wall. If you're currently managing costs by staying on the older, cheaper AI tier, that option disappears on December 10. Migration to the new system — billed at $1.50–$2.00 per automated resolution, with Copilot an optional $50/agent/month add-on billed yearly — is mandatory.
Why Four Migrations in Six Months Is a Problem
Any one of these migrations would be manageable in isolation. But stacking four of them in a six-month window creates compounding disruption:
Each migration requires testing
Every forced change needs to be tested against your existing workflows, automations, triggers, and integrations. Four migrations means four testing cycles — and with the first two hitting in June alone, teams have barely two weeks between them.
Support doesn't pause for migrations
Your customers don't stop needing help because your helpdesk vendor is forcing infrastructure changes. Every hour spent on migration testing and troubleshooting is an hour not spent on actual support.
The pricing impact compounds
Migration #1 introduces outcome-based pricing. Migration #4 forces everyone onto it. Between June and December, teams face both the operational disruption of migrating AND the financial uncertainty of a new pricing model. Budget planning for H2 2026 becomes an exercise in guessing.
No opt-out, no delay
These aren't optional. Zendesk has made each migration mandatory with fixed deadlines. As one customer put it: "You don't force workflow-related changes onto mission-critical software without an option to disable it."
The Cost of Staying
Beyond the migration disruption, the financial picture after all four migrations complete is stark. Based on confirmed pricing from Zendesk Relate 2026:
| Team Size | Zendesk Annual Cost | DeskLeap Annual Cost | Annual Savings |
|---|---|---|---|
| 5 agents | $115/agent/month in seats + $1.50–$2.00 per automated resolution | $0, or $1,740 with the AI Agent on all 5 | Depends on resolution volume |
| 10 agents | $13,800 in seats + $1.50–$2.00 per automated resolution | $0, or $3,480 with the AI Agent on all 10 | Depends on resolution volume |
| 15 agents | $115/agent/month in seats + $1.50–$2.00 per automated resolution | $0, or $5,220 with the AI Agent on all 15 | Depends on resolution volume |
| 25 agents | $115/agent/month in seats + $1.50–$2.00 per automated resolution | $0, or $8,700 with the AI Agent on all 25 | Depends on resolution volume |
Zendesk: Suite Pro ($115/agent) = $13,800/year for 10 agents, plus Copilot at $50/agent if you add it, plus $1.50 committed or $2.00 pay-as-you-go per automated resolution (zendesk.com/pricing, read 17 Oct 2026). DeskLeap: platform free; AI Agent $29/month each.
Teams across the industry are reporting 40–70% cost reductions by switching away from Zendesk. The cost difference alone funds the migration effort many times over.
Your Escape Plan: Switching Before the Deadlines
If you're going to switch, doing it before June 12 means you skip all four migrations entirely. Here's the practical plan:
Week 1: Evaluate
- Sign up for DeskLeap — the platform is free — no sales demo, no credit card
- Build your knowledge base from your website
- Enable AI auto-replies and test against your common ticket types
- Check that your critical workflows are covered: ticket routing, SLA management, CSAT
Week 2: Set Up
- Invite your team — the platform is free; add the AI Agent at $29/month each if you want it
- Install the DeskLeap chat widget on your site (script tag, WordPress plugin, or Shopify app)
- Connect integrations: Slack alerts, Shopify or WordPress, plus webhooks and the REST API as needed
Week 3: Parallel Run
- Run both Zendesk and DeskLeap simultaneously
- Route new tickets to DeskLeap while maintaining Zendesk for historical access
- Monitor response times and CSAT scores
- Train your team on the DeskLeap interface
Week 4: Cut Over
- Move your website chat widget and help center to DeskLeap
- Export any remaining Zendesk data you need for records
- Cancel your Zendesk subscription
- Enjoy predictable billing
What You Get by Switching
- No forced migrations — ever. DeskLeap updates ship automatically and don't break existing workflows. No mandatory deadlines, no auto-migrations, no "opt-in or lose access" ultimatums.
- Predictable pricing. The platform is free; each AI Agent is $29/month. No per-resolution fees, no mandatory add-ons, no outcome-based billing. Your bill is the same every month.
- Free trial without a sales call. Sign up, test everything, decide on your own timeline. No demos required.
- Simpler operations. No intent tags to manage, no Admin Copilot needed to debug your AI. The platform is designed to work without a dedicated admin.
The Timeline Is Working Against You
June 12 is the first deadline. After that, you're managing Zendesk's migration process AND evaluating alternatives simultaneously — the worst of both worlds.
Switching before the deadline means:
- Zero forced migrations to deal with
- Immediate cost savings — the platform is free, and your AI cost is a number you can state in advance
- A fresh start on a platform that won't force you through this again next year
Switching after December 10 means:
- Surviving all four migrations first
- Paying the new outcome-based pricing for at least 6 months
- Migrating while exhausted from half a year of forced changes
The math and the timing both point the same direction: if you're going to leave Zendesk, doing it now saves the most money and the most disruption.