Zendesk legacy AI agents removal: rebuild by February 2027, and the migration tool skips legacy bots

The Zendesk legacy AI agents removal has no single shutdown date. If your answers were built in bot builder, Zendesk starts migrating your agents for you at the beginning of February 2027, and removes the features from the product no later than June 2027. Development already stopped on August 31, 2026.

What follows is the four dates Zendesk publishes, how to check in Admin Center which kind of agent you actually have, and why a legacy agent is a rebuild rather than a migration: the auto-migration tool Zendesk rolled out in October 2026 covers AI agents - Essential only.

The zendesk legacy ai agents removal covers three features and exempts one group

Zendesk's announcement applies to customers using AI agents - Essential or legacy AI agent functionality, which it defines as bot builder, answers and intents, plus the separate autoreplies with articles feature. The announcement states that it does not apply to customers who previously purchased the AI agents - Advanced add-on. If you bought Advanced, nothing here is your problem.

The reason for the removal is packaging, not cost cutting. Zendesk rolled out new AI agent packaging between May 11 and June 12, 2026 that removes the Essential and Advanced distinction, so the agentic features once sold as Advanced now sit on all Suite and Support plans.

When does Zendesk remove legacy AI agents: four dates, not one

Zendesk's recommended date was to migrate before August 31, 2026, which has passed. The date that now binds you is February 2027, because after that Zendesk makes the decision instead of you. Zendesk writes "with some exceptions" for both forced migrations and does not say what those exceptions are, so do not plan around being one of them.

Autoreplies with articles has its own consequence. Zendesk says that if you do not migrate, from January 2027 the autoreply is still sent but no longer includes the article recommendations, which is a quiet degradation rather than an outage.

How do I know if my Zendesk bot is legacy? Look for the Answers tab

Both kinds of agent sit under the same heading in Admin Center, which is why teams misjudge which deadline applies to them.

1. In Admin Center, click AI in the sidebar, then select AI agents > AI agents.
2. Under Essential (legacy), click an AI agent to open its settings.
3. Review the tabs. An Essential agent has no Intents or Answers tab.
4. A legacy agent has an Answers tab, and may also have an Intents tab.

That tab is the whole distinction, and it decides whether you get a tool or a rebuild.

Zendesk's auto-migration tool only covers Essential agents

The tool rolled out between September 30 and October 6, 2026. For an Essential agent it creates a new agent and carries over the settings and instructions, messaging and email behavior including greetings and escalation flows, connected knowledge sources, brand settings, and the default language and translation configuration.

What it does not carry over is worth planning for: Zendesk states that historical conversation logs, analytics and insights are not migrated, and conversation memory does not persist, so in-progress messaging conversations are interrupted when you activate. Migration cannot be undone, and editing the original Essential agent afterwards leaves the two permanently out of sync.

For legacy agents the picture is less settled. Zendesk's migration guide says you can migrate manually now or use a migration tool that will become available later in 2026, but the only tool Zendesk has announced is the Essential one, and as of October 31, 2026 we found no Zendesk article describing a legacy equivalent or giving it a date. Treat a legacy rebuild as manual until Zendesk says otherwise.

What the rebuild involves: bot builder becomes Dialogue builder

The concepts rename, and the renaming is not cosmetic. Zendesk's own mapping table is the best scoping document you have.

The procedure Zendesk gives is to generate a list of your current answers and intents, then follow its getting-started guidance, paying particular attention to step 4.1 on creating use cases and step 4.2 on creating generative procedures or dialogues. There is no import step in that sequence.

Zendesk does not publish how long any of this takes, and we are not going to invent an hours figure. The honest unit of scope is the answer flow: count your answers, then count the branching steps and API calls inside each one. Zendesk's own signal on effort is indirect but clear, because it strongly recommends its AI Expert offering for agents with many answer flows or flows with many branching steps or integrations. AI Expert is a recurring service subscription and Zendesk's guide points you to its sales team rather than to a price.

One structural change catches multi-channel setups. Essential agents were omnichannel, but each agent in the new experience handles one channel type only, so an agent that ran on messaging and email becomes two agents that you configure and maintain separately. Custom translations also get heavier, because the new experience needs a language-specific version of each system reply, which is why Zendesk recommends automatic translation instead.

Your automated resolution bill can move even if the agent behaves the same

Zendesk warns that the number of automated resolutions may change as you start using the upgraded capabilities, and because pricing is tied to outcomes that can change what you pay. Your existing overage configuration is respected, which limits the surprise but does not remove it.

The allowances are small enough to matter. Zendesk's pricing page lists Suite Team at US$55 per agent per month billed annually with 5 automated resolutions per agent per month, and Suite Professional at US$115 with 10, with resolutions beyond the allowance billed on top. Check the AR line on your invoice for the month after you activate, not just the agent's deflection rate. We covered the wider trap in what counts as the billable unit in AI customer support pricing.

Skip the vendor hunt unless you were only deflecting articles

Migrating inside Zendesk is the right default for most teams here. Your knowledge sources, channels, ticket history and routing already live there, and rebuilding dialogues is less work than reproducing a help desk somewhere else. If your legacy answers make API calls into your own systems, stay: that integration work does not transfer to another vendor either.

The case for looking is narrow. If you ran an Essential agent purely to suggest help center articles and the rest of your Zendesk footprint is light, a cheaper chat-plus-bot tool can cover it. Prices we checked on each vendor's own pricing page on October 31, 2026:

None of these is a help desk replacement at that price, and swapping vendors in the same quarter as a forced migration doubles your risk. As of October 2026 Upfynd lists 243 products in Customer Support and 370 in AI Agents if you do want to compare the field properly.

The useful thing to do this week is the count, not the decision: open Admin Center, check whether each agent has an Answers tab, and for the ones that do, write down how many answers they hold and how many branching steps and API calls sit inside each. That number is your February 2027 scope, and it is the only input that makes the build-or-buy argument concrete.