Zendesk's 6 Migration Deadlines Through 2028: A Survival Calendar

If you administer a Zendesk account, you are currently living inside six separate forced migrations. They run from the summer of 2026 through the summer of 2028, they touch three unrelated parts of the product, and they are announced across a handful of different help-centre articles that do not link to each other.

This is the whole calendar in one place. Every date and every quotation below comes from Zendesk's own support documentation — sources are listed at the end. Nothing here is our characterisation of their roadmap; it is their roadmap.

One of these deadlines has already passed.

The full calendar: eight dates, six migrations

Migration 1: legacy AI agents (31 August and 10 December 2026)

If you built anything with the bot builder, or you use autoreplies with articles, you are on what Zendesk now calls "AI agents – Essential and legacy functionality." Two dates apply.

On 31 August 2026, technical development stops — Zendesk continues critical bug fixes and support for breaking changes, and nothing else. On 10 December 2026, the products shut off entirely. You must migrate to the upgraded AI agent experience before that second date.

Zendesk's own guidance is to be finished by the earlier one. In their words, they recommend customers "plan to complete their migration by August 31, so you may avoid any potential disruptions to your support."

That is a meaningful gap between the deadline that exists on paper and the deadline the vendor actually recommends. If you are budgeting time, budget to August, not December.

What to check this week

• Open Admin Center and list every bot built in the legacy bot builder.
• Note which of your help-centre articles are wired into autoreplies.
• Rebuild each flow in the new AI agent experience — conversation flows do not carry across automatically.
• Re-test the handoff from bot to human. This is the step teams most often discover is broken after the cutover, because it is the one nobody thinks to test.

Migration 2: API tokens become OAuth (three phases to 30 April 2027)

This is the one to worry about, and it is the one getting the least attention — because it is not a pricing change a finance team can absorb. It is engineering work on every custom integration you own, with a hard cutoff and no opt-out.

Zendesk is removing API tokens as an authentication method entirely. Every integration must move to OAuth. The rollout has three phases:

• Phase 1 — 28 July 2026 (already in effect). A one-time cleanup deactivated any token unused for 30 days or more, and that deactivation is now continuous: tokens sitting idle for 30 days get deactivated, and tokens left deactivated for 60 days are permanently deleted. Critically, accounts created on or after this date "cannot create or use API tokens" at all.
• Phase 2 — 27 October 2026. No account can create a new API token, through the UI or the API. Tokens that already exist keep working.
• Phase 3 — 30 April 2027. Every remaining token is deactivated permanently, and admins cannot reactivate them.

Two things about Phase 1 deserve emphasis, because they change what you should do today rather than next year.

The first is that idle tokens are being deactivated now, on a rolling basis. A token that runs a quarterly export, or a disaster-recovery script, or a seasonal integration, can be deactivated for inactivity and then deleted 60 days later — before you ever reach for it. The failure mode is not a warning at renewal time; it is a script that worked in March failing silently in July.

The second is that Zendesk accounts created on or after 28 July 2026 have no API-token path whatsoever. If you spin up a sandbox or a second brand today and follow an integration runbook written last year, the first step no longer exists.

What to check this week

• In Admin Center, review the API token list and the new "Deactivates on" column and usage reports Zendesk shipped alongside Phase 1.
• Inventory anything that authenticates to Zendesk: middleware, internal scripts, data warehouse syncs, billing reconciliation jobs, that one Zapier connection nobody owns.
• Check webhooks specifically. Using an API token in a webhook that calls back into your own Zendesk instance is no longer supported and stops working as part of this deprecation.
• For each integration, confirm the vendor has an OAuth path. Not every one does — this is the item most likely to become someone else's roadmap dependency, so find out early.

Migration 3: Zendesk Chat retires (31 January 2028)

On 4 August 2026, Zendesk announced that Zendesk Chat will be removed. Chat retires on 31 January 2028, and full access to the Chat dashboard ends on 28 July 2028. Customers migrate to Zendesk messaging, with an 18-month window and self-serve migration tooling.

The reason given is worth quoting exactly as written, because a paraphrase would sound like an attack and the original is simply a statement of fact from the vendor:

"Chat is a legacy product that hasn't received feature enhancements since 2020 and does not support modern AI features."

Read that as an administrator rather than as a competitor. If you have been running Zendesk Chat since 2021, you have been running software that received no feature work for the entire time you were paying for it — and you are now told so in the same notice that gives you a date to leave by. The lesson is not that Zendesk behaved unusually. It is that "included in your plan" and "actively developed" are separate questions, and most buyers only ever ask the first one.

What to check this week

• Nothing urgent — this is the one deadline with genuine room. Do not let it pull attention from the API work, which has a 2027 cutoff and far more engineering in it.
• Do note the trigger and shortcut logic you have accumulated in Chat, since that is what has to be rebuilt in messaging.
• If your chat widget is embedded through custom code on a marketing site, find out now who owns that code. It is usually not the support team.

How to read six deadlines in twenty-four months

Any mature platform deprecates things, and every vendor on the market — us included — will eventually ask customers to move off something. The number of deadlines is not, by itself, an indictment.

What is worth noticing is where the cost lands. A price increase is absorbed by a budget. A forced migration is absorbed by people: the admin who rebuilds the bot flows, the developer who rewrites the auth layer on four integrations, the support lead who re-tests every handoff afterwards. That cost does not appear on any invoice, which is exactly why it tends to be underestimated when it is planned and painfully visible when it arrives.

So the practical question for the next eighteen months is not "what does this cost." It is "who is doing this work, and what are they not doing instead."

Where DeskLeap fits

We build a helpdesk with ticketing, live chat and a knowledge base, so we are not a neutral party here and you should read this section accordingly.

The relevant difference is structural rather than clever. Our live chat is not a separate legacy product bolted onto the ticketing system through an acquisition — it is part of the same platform, which is the reason it does not have its own retirement date. The platform itself is free, with human agents included at no cost; the only paid component is the AI Agent add-on at $29 per month per agent, which you can add or remove at any time.

What we will not tell you is that migrating is free of effort. Moving helpdesks is real work, and anyone who says otherwise is selling. If your Zendesk setup is working and your integrations are already on OAuth, the honest advice is to do the migrations above and stay put.

The case for looking elsewhere is narrower and more specific: if you are about to spend a quarter of engineering time rewriting integrations against a platform whose live chat is already scheduled for retirement, that is a reasonable moment to ask whether you want to be on that platform for the deprecation after this one.

Sources

Every date and quotation above comes from Zendesk's own documentation, verified on 12 August 2026:

• Announcing the removal of AI agents – Essential and legacy functionality: Important dates and migration guidance
• Announcing the removal of API tokens as an authentication method for API requests
• Announcing the removal of Zendesk Chat for messaging-eligible customers
• About the removal of Zendesk Chat and migration to messaging
• Migrating from API tokens to OAuth access tokens (Zendesk Developer Docs)

Dates change. Before you plan a quarter around any of them, check the source articles — and if you spot a change we have missed, tell us and we will correct this page.