← Back to Blog
You Think Thursday Is the Deadline? Zendesk Actually Has Three
·6 min read
Everyone's focused on June 12. That's when Zendesk's forced AI agent migration goes live and the new outcome-based pricing kicks in.
But June 12 is just the first deadline. There are two more — and most Zendesk customers don't know about them yet.
The full Zendesk migration timeline runs through December 2026. Six more months of forced changes, feature shutoffs, and configuration disruptions. Here's the complete picture.
Deadline #1: June 12, 2026 — Forced Migration Begins
What happens:
- Migration to the new AI agents experience completes for all accounts
- The Essential/Copilot distinction is permanently removed
- All customers moved to the unified Forethought-powered AI platform
- New AI agent reporting changes go live (already rolling out since May 18)
- Outcome-based pricing activates: Zendesk begins charging per automated resolution, at a rate it does not publish
What you lose:
- Access to the old Essential AI tier and its pricing
- Existing AI agent configurations may need updating or rebuilding
- Familiar reporting dashboards replaced with new metrics
Impact level: High. This is the day billing changes and AI configurations potentially break. Teams that haven't prepared will feel it immediately.
Deadline #2: August 31, 2026 — Development Stops
What happens:
- Zendesk stops all development on legacy AI agents (Essential tier)
- Bot builder development halts — no new features, no improvements
- Old functionality enters maintenance-only mode (and even that's limited to critical bug fixes only)
- New Zendesk features and integrations will only work with the new AI stack
What you lose:
- Any hope of legacy AI improvements or fixes for known issues
- Compatibility with new Zendesk features — the old system becomes increasingly isolated
- Bug fixes beyond critical security patches
Impact level: Medium-high. If you're still running legacy AI after August 31, you're on an abandoned platform. Zendesk's own documentation recommends completing migration by this date "to avoid disruptions." When a vendor tells you to hurry, the system you're on is about to degrade.
Deadline #3: December 10, 2026 — Full Shutdown
What happens:
- Legacy AI agents (Essential) are completely turned off
- Bot builder is shut down entirely — no access, no functionality
- All customers must be on the new AI stack or lose AI capabilities entirely
- No rollback option — the legacy system is gone permanently
What you lose:
- Everything built on the old system. Every bot, every flow, every configuration that wasn't migrated stops working.
- If you haven't migrated by December 10, your AI-powered support goes dark overnight
Impact level: Critical. This is the hard wall. There is no extension, no grandfather clause, no "one more month." December 10 is the end.
The Six-Month Timeline at a Glance
| Date | What Happens | What You Lose |
|---|---|---|
| June 12 | Forced migration begins, new pricing activates | Old pricing, old AI configs |
| August 31 | Legacy AI development stops entirely | Bug fixes, new features, compatibility |
| December 10 | Legacy AI and bot builder shut off | Everything not migrated — permanently |
Why Zendesk Is Boiling the Frog
These three deadlines aren't random — they're a deliberate graduated migration strategy. Each deadline is designed to move customers further along the migration path while making it progressively harder to leave:
June: Change the pricing
Get customers onto the new billing model. Once you're paying per-resolution, you're invested in the new system — you want to optimize it, not abandon it.
August: Remove the safety net
Stop maintaining the old system. Now the legacy option isn't just old — it's degrading. Bugs accumulate, compatibility breaks, and the new system looks increasingly like the only viable path.
December: Close the door
Shut off legacy entirely. By this point, most customers have migrated (either willingly or grudgingly), and the holdouts face a binary choice: migrate to the new pricing or lose AI entirely.
It's textbook gradual forced migration. Each step feels manageable in isolation. But the cumulative effect is six months of disruption — configuration changes, pricing surprises, deprecation warnings, and finally a hard shutdown — all while your team is supposed to be running support operations.
The Real Cost of Six Months of Uncertainty
The financial impact of the new pricing is well documented — a 10-agent team faces $13,800/year in seats plus an unpublished AI charge on the full AI stack. But the operational cost of six months of forced migration is harder to quantify:
- Testing time: Each deadline requires testing AI configurations, flows, and automations against the new system. That's engineering and admin time diverted from actual support.
- Training time: New AI agent framework means new interfaces, new configuration patterns, new reporting dashboards. Your team learns the system three times as features migrate.
- Customer impact: Every configuration change risks degrading the customer experience. AI responses may change quality, routing may shift, response times may fluctuate during transitions.
- Planning paralysis: How do you plan your support operations for H2 2026 when the platform underneath keeps changing? Roadmaps become guesswork.
The Alternative: Zero Deadlines, Zero Surprises
DeskLeap doesn't have migration deadlines because there's nothing to migrate from. The AI is built into the platform — it's not a bolt-on that gets replaced every year.
- Free for every agent — the AI Agent is a $29/month add-on, priced per AI Agent. No per-resolution fees. No mandatory add-ons. No pricing restructures.
- AI included on all paid plans — auto-resolution, intelligent routing, suggested replies. No tiers, no gating.
- Updates ship without breaking your setup — platform improvements are backward-compatible. No forced migrations, no configuration rebuilds, no shutdown deadlines.
- Free plan to test first — sign up without a credit card or sales demo, import your knowledge base, see how the AI handles your tickets.
Your Complete Research Library
If you're evaluating whether to stay on Zendesk or switch, we've published comprehensive coverage throughout May and June 2026:
- Zendesk vs DeskLeap 2026: Full Comparison
- Zendesk Relate 2026 Recap: Every Announcement
- Zendesk's Pricing Is Impossible to Predict
- What Zendesk Users Are Actually Saying
- 4 Forced Migrations: Your Escape Plan
- 3 Business Days Left: D-3 Countdown
- Best Zendesk Alternatives 2026
- Fin for Zendesk vs Switching to DeskLeap
The Decision Point
Thursday starts a six-month countdown. If the new pricing works for your budget and your team has the bandwidth for six months of migration management — stay and adapt.
If the math doesn't work, or the operational disruption is too much, or you'd rather spend the next six months helping customers instead of managing platform migrations — the window to switch cleanly is closing.