Zendesk's Legacy AI Shutdown: Why August Matters More Than December

These aren't just cosmetic changes. The underlying way AI agents are configured and managed has evolved, so existing workflows should be reviewed rather than copied across unchanged.

For the full list of affected features, see Zendesk's official guidance and the detailed migration overview published by Help Desk Migration:

→ Zendesk Help
→ Help Desk Migration | Zendesk Legacy AI Shutdown

Why August is the deadline that really matters

Although removal doesn't happen until December, 31 August 2026 is when Zendesk stops active development of the legacy platform.

From that point onwards, the old functionality enters maintenance mode.

That generally means:

• Critical issues may still be addressed.
• No meaningful feature development should be expected.
• Any migration work becomes increasingly time-sensitive.

Waiting until the final few weeks before December leaves little room for testing, refinement or unexpected complications.

For organisations with complex customer journeys, multiple brands or heavily customised automation, that's a significant risk.

Migration isn't simply a lift-and-shift

One of the biggest misconceptions is that upgrading means exporting one bot and importing it somewhere else.

In practice, the new AI experience introduces several behavioural differences that are worth understanding before starting a migration.

For example, AI agents are now designed to operate on a single channel. If your support operation uses both messaging and email, you'll need separate AI agents for each channel.

This presents a good opportunity to step back and ask broader questions such as:

• Which automations are genuinely delivering value?
• Are there outdated conversations that can be retired?
• Could customer journeys be simplified rather than recreated?

Many organisations discover years of accumulated logic, exceptions and duplicate workflows during this process. Cleaning these up before rebuilding often leads to a simpler, easier-to-maintain support experience.

Start with an audit

Before migrating anything, it's worth understanding exactly what your current environment contains.

A simple audit might include:

• Legacy bots currently in production
• Answers and knowledge-driven responses
• Intents and routing logic
• Default messaging responses
• Channel-specific workflows
• Dependencies on integrations or APIs

Having a clear inventory makes it much easier to decide what should be migrated, redesigned or retired altogether.

Migration is also an opportunity

Platform changes are rarely welcome when they're unexpected.

However, they do provide a natural opportunity to improve customer support rather than simply preserve the status quo.

Many organisations find this is a good time to:

• Remove outdated or duplicate automation
• Improve self-service journeys
• Simplify escalation paths
• Review reporting and AI performance
• Align support experiences across channels

Rather than viewing this purely as a technical migration, it's worth treating it as a chance to modernise your customer service workflows.

Final thoughts

December 2026 is the date the old AI experience disappears - but for most organisations, the real planning deadline is much earlier.

Starting before the end of August gives teams time to understand their current setup, redesign customer journeys where necessary, and complete testing without unnecessary pressure.

If you'd like a detailed breakdown of everything that's changing, the migration considerations, and a feature-by-feature comparison, the article from Help Desk Migration is well worth reading.

→ Help Desk Migration | Zendesk Legacy AI Shutdown

If you're reviewing your Zendesk environment and would like an independent assessment of your existing workflows or help planning a migration, feel free to get in touch. We're always happy to discuss options and share practical advice based on your specific environment.