---
title: "Zendesk AI Agent Migration Checklist (2027) | BoldDesk"
description: "Legacy bots and autoreplies retire in 2027. Use this Zendesk AI agent migration checklist to audit bots, rebuild flows, and migrate on your terms."
url: "https://www.bolddesk.com/blogs/zendesk-ai-agent-migration-checklist"
last_updated: 2026-11-16
---

-   Blogs [Explore Blogs Blogs](https://www.bolddesk.com/blogs)

# Zendesk AI Agent Migration Checklist: Replace Answer Bot Before 2027

-    [by Cherine Apondi Okumu](https://www.bolddesk.com/author/cherine-apondi-okumu)
-   Updated on: November 12, 2026

![Light blue Zendesk legacy bots checklist graphic showing green checkmarks, an AI Agent card, and a peach 2027 clock.](https://www.bolddesk.com/wp-content/uploads/2026/11/zendesk-ai-agent-migration-checklist-banner-1024x546.webp)

Level Up Your Customer Support with BoldDesk

[![Sign up for BoldDesk](https://www.bolddesk.com/wp-content/uploads/2026/09/80ada21c-bolddesk-blog-ads.svg)](https://app.bolddesk.com/signup?)

[Free Trial](https://app.bolddesk.com/signup?)

[Book Demo](https://www.bolddesk.com/request-demo)

Summarize with:

Share

> **TL;DR:** Zendesk is retiring AI agents - Essential, legacy bot builder, and article autoreplies, requiring a Zendesk AI agent migration. Unmigrated Essential agents are migrated automatically in January 2027 and legacy agents from February 2027, with removal no later than June 2027. Test first, because migration can’t be undone.

If your Zendesk account still runs an Essential AI agent, a bot builder flow, or autoreplies that suggest help center articles, you have a Zendesk AI agent migration to finish. As of November 2026, Zendesk’s January 2027 automatic switch for Essential agents is about seven weeks away, with the holiday period in between.

“Answer Bot” is an older Zendesk name. In Zendesk’s current documentation, it maps to three different setups: Essential AI agents, legacy bot builder agents, and article autoreplies.

Each one follows its own migration path. If your account uses more than one setup, a Zendesk Answer Bot migration requires separate steps for each.

This guide explains what changes, how to tell which setup you have, and what to check before, during, and after the switch. The downloadable version lets you assign owners and record sign-off.

## Zendesk AI agent migration checklist at a glance

-   Inventory every AI agent, bot builder flow, and article autoreply, by brand, channel, and language.
-   Save a performance baseline: volume, automated resolutions, handoffs, and feedback.
-   Map each flow to the new experience and decide whether to replicate or redesign it.
-   Migrate Essential agents with Zendesk’s migration tool and rebuild legacy flows.
-   Test every channel, language, API action, and human handoff.
-   Estimate automated resolution usage and overage costs.
-   Activate in a low-traffic window, starting with the lowest-volume agent.
-   Compare results with your baseline before retiring the old setup.

## What happens to Zendesk legacy AI agents in 2027?

Zendesk is retiring three things: AI agents - Essential, legacy AI agent functionality (bot builder, answers, and intents), and autoreplies with articles. The change applies across Zendesk Suite plans (Team, Growth, Professional, Enterprise, and Enterprise Plus) and Support plans (Team, Professional, and Enterprise).

According to Zendesk’s removal notice, customers who purchased the AI agents - Advanced add-on are not affected. Zendesk’s [removal announcement](https://support.zendesk.com/hc/en-us/articles/10904648529690-Announcing-the-removal-of-AI-agents-Essential-and-legacy-functionality-Important-dates-and-migration-guidance) and [migration guide](https://support.zendesk.com/hc/en-us/articles/10543162665242-Migrating-to-the-new-AI-agents-experience) set out the dates below.

| **Milestone** | **What a support team should know** |
| --- | --- |
| **June 23, 2026** | Zendesk announced the removal. |
| **August 31, 2026** | The affected features entered maintenance mode. Development ended, except for critical bug fixes and support for breaking changes. |
| **January 2027** | Zendesk migrates any remaining Essential AI agents, with some exceptions. Unmigrated Zendesk autoreplies with articles keep sending responses, but without specific article recommendations. |
| **Beginning of February 2027** | Zendesk migrates any remaining legacy AI agents, with some exceptions. |
| **No later than June 2027** | The old functionality is removed from the product. |

Zendesk says exceptions may apply but doesn’t list them publicly. Review the notices in your account, and don’t assume your setup is exempt.

### Why do some pages say December 10, 2026?

Earlier Zendesk documentation gave December 10, 2026, as the date these features would stop being available, and many third-party articles still repeat it.

Zendesk’s current removal notice and migration guide replace it with the January, February, and June 2027 dates above. Because the dates have changed once already, check the removal notice again before you set your internal deadline.

### Bought AI agents - Advanced before March 10, 2026?

You’re outside this retirement, but you have a separate change to plan for. Zendesk is moving these accounts to new infrastructure through the end of 2026.

Integrations that use the Ultimate Public API should already have switched from `*.ultimate.ai` to `<your-subdomain>.zendesk.com/ai-agents/api`; if you haven’t, update now.

The separate AI agents - Advanced login page is also being retired by the end of 2026. See Zendesk’s [workspace migration notice](https://support.zendesk.com/hc/en-us/articles/10887725757210-Announcing-AI-agents-workspace-migration-and-updates-to-knowledge-and-search-rules) for details.

### What happens if you don’t migrate in time?

Zendesk migrates the remaining setups for you, but on its schedule rather than yours.

Remaining Essential agents are migrated in January 2027 and legacy agents from February 2027, and autoreplies keep sending without article recommendations.

Zendesk doesn’t publish how an automatically migrated bot builder flow will be recreated, which accounts fall under the exceptions, or exactly when each account switches.

If you wait, you can’t choose the activation window or test the new agent before customers use it. Migrating yourself gives you both.

## Which Zendesk bot setup do you have?

The Answer Bot name alone won’t tell you which migration path applies.

In Admin Center, go to **AI > AI agents > AI agents** and open each agent listed under **Essential (legacy)**. The tabs show which type it is.

![Zendesk Admin Center showing a legacy AI agent with Insights, Settings, Messaging behavior, Intents, Answers, and Instructions tabs](https://www.bolddesk.com/wp-content/uploads/2026/11/zendesk-legacy-ai-agent-answers-intents-tabs.webp)

A legacy AI agent shows Answers and Intents tabs

| **Existing setup** | **How to identify it** | **Migration path** |
| --- | --- | --- |
| **Essential AI agents** | Listed under Essential (legacy), with no Answers or Intents tab. A **Start migration** banner appears on the AI agents page when you have Essential agents to migrate. | Use Zendesk’s migration tool, then preview and test the new agent before you activate it. |
| **Legacy bot builder, answers, and intents** | Listed under Essential (legacy), with an Answers tab and possibly an Intents tab. | Rebuild manually now: answers become dialogues and intents become use cases. Zendesk says a migration tool for legacy agents is planned for later in 2026; it wasn’t available at the time of writing. |
| **Autoreplies with articles** | Check **Manage autoreplies** (Email and Web form tabs) and each brand’s Web Widget (Classic) settings for the Autoreply with articles option. | Create a new AI agent that gives generative replies from your help center content, and test each entry point. |

## How long does a Zendesk AI agent migration take?

It depends on the setup. Zendesk describes migrating an Essential agent with the tool as quick; most of the effort goes into testing and activation planning.

A legacy bot builder rebuild scales with the number of answers, intents, API calls, branches, and languages you support. Count those for each agent during your inventory to estimate the effort.

If you’re short on time before January 2027, work in this order:

-   Inventory every setup so nothing is migrated without your knowledge.
-   Migrate and test Essential agents first, because their deadline comes first and the tool does most of the work.
-   Replace autoreplies with articles, which lose their article links in January 2027.
-   Rebuild your highest-volume legacy flows, then the rest before February 2027.

## Zendesk AI agent migration checklist: 8 checks

Use these checks to identify what needs to move, what needs rebuilding, and what to test before rollout.

### 1\. Find every bot and autoreply you run

Create an inventory of every AI agent, bot builder flow, article autoreply, and customer entry point in use. Include draft configurations that might be activated later.

For each setup, record the brands, channels, languages, knowledge sources, escalation paths, and the owner responsible for it. For legacy agents, also count answers, intents, and API calls so you can size the rebuild.

Review triggers, automations, views, dashboards, and reports that reference legacy bot outcomes, intents, or tags. These dependencies may need updates after migration.

### 2\. Save your current bot performance baseline

Save a baseline before you change anything. Record conversation volume, automated resolutions, article usage, human handoffs, unresolved requests, and customer feedback by channel.

Historical conversations and analytics don’t move to the new agent, so export what you need now. Keep a small sample of real conversations, including questions the bot answered poorly.

### 3\. Map each flow to the new experience

Walk through your most-used flows. Note where each one asks for details, suggests an article, calls an API, follows a branch, or hands the customer to a person.

Zendesk maps the bot builder to the dialogue builder, answers to dialogues, and intents to use cases. The table shows how each bot builder step becomes a dialogue builder block.

| **Bot builder step** | **Dialogue builder block** | **What to test** |
| --- | --- | --- |
| **Send message** | AI agent message | Wording, formatting, and translations. |
| **Present options** | Customer message | Every option leads to the correct outcome. |
| **Show help center articles** | Generative replies | Answers come from the correct articles and knowledge sources. |
| **Add carousel** | Carousel | Cards and links display correctly in each channel. |
| **Ask for details** | Ask for details | Required fields, validation, and data capture. |
| **Ask if question resolved** | Customer message that asks if the question was resolved | Both paths, resolved and not resolved. |
| **Make API call** | Integration or action flow | Authentication, failed requests, and empty responses. |
| **Transfer to agent** | Escalation | Routing reaches the right team with conversation context. |
| **Branch by condition** | Conditional | Every branch, including fallback paths. |
| **Add business hours condition** | Availability | After-hours behavior and messages. |
| **Link to another answer** | Link to | Customers land in the right dialogue. |
| **Set variable** | Any block with an added action that sets a conversation parameter | Values are set and used later in the flow. |

A Zendesk bot builder migration is a rebuild, not a copy. Use it to decide which flows to replicate and which to redesign.

Keep scripted dialogues where a fixed sequence matters, such as collecting an order number before an API call.

For requests that need judgment across several steps, consider generative procedures, which Zendesk recommends exploring during migration.

For sensitive requests, define when a human agent should review or take over. Our [human-in-the-loop support](https://www.bolddesk.com/blogs/human-in-the-loop-ai-for-customer-service) guide has examples of escalation planning.

For many or complex answer flows, Zendesk recommends its AI Expert offering. Note that AI Expert is a recurring paid subscription.

Zendesk Professional Services can also help; contact your account team for scope and pricing.

### 4\. Check what the migration tool carries over

For Essential agents, the [Zendesk AI agent migration tool](https://support.zendesk.com/hc/en-us/articles/11154156930842-Migrating-essential-AI-agents-to-the-new-unified-AI-agent-experience-using-the-migration-tool) creates a new agent and configures it from the original. It carries over:

-   Agent settings and instructions.
-   Messaging and email behavior, including greetings, escalation flows, feedback collection, and fallback behavior.
-   Connected knowledge sources.
-   Brand settings and visual customization.
-   Default language and translation configuration.
-   Channel connections.

Historical conversations, analytics, insights, and live conversation memory stay with the original agent.

New agents work on one channel type only, so if an Essential agent served both messaging and email, the tool creates two agents. The email agent also covers web form and API channels.

Expect these configuration differences after migration:

| **Standard response (Essential agent)** | **System reply (new experience)** |
| --- | --- |
| Start of the conversation | Welcome reply |
| After the AI agent replies | Collect BSAT reply |
| Escalation | Escalation reply |
| If the AI agent can’t answer the question | Default reply |

-   **New system replies to review:** unsupported language reply, failed escalation reply, and technical error reply. They start with a default configuration.
-   **Custom translations:** each system reply needs its own version per language, which adds maintenance. Zendesk recommends automatic translations instead.
-   **Where you manage agents:** new agents live in the AI agents workspace, not Admin Center.

The migration cannot be undone. Choose a low-traffic period before you start.

For legacy bot builder agents, rebuild flows manually using the mapping in check 3 until Zendesk releases its planned legacy migration tool. For article autoreplies, create a new AI agent to replace them.

### 5\. Test the customer experience end to end

Before testing, review your knowledge base for outdated, duplicate, or incomplete articles. AI agents generate answers from this content, so weak articles lead to wrong answers and unnecessary handoffs.

Use the **Test AI agent** widget with the questions customers ask, not just a few ideal prompts. Check answers against current articles.

Try unclear questions, restricted content, failed API actions, unsupported requests, and changes of topic. Run the tests in every channel and language you support.

If some articles are restricted to signed-in users, test them through your live help center. Zendesk notes that the test widget doesn’t support authentication, so it only sees content available to anonymous visitors.

Then ask to speak to a person. Confirm the request reaches the right team with enough context to continue.

The [AI agent security](https://www.bolddesk.com/blogs/ai-agent-security) guide covers permission and action checks that are easy to miss during testing.

If you use article autoreplies, inspect the reply the customer receives.

From January 2027, unmigrated autoreplies may still send messages without article recommendations. A sent message doesn’t mean self-service still works.

### 6\. Review usage, billing, and costs

Check your account’s automated resolution allowance and overage settings.

Zendesk warns that the upgraded agents may change the number of automated resolutions your account records, and because pricing is tied to outcomes, that can change your costs.

Your existing overage configuration continues to apply. Estimate what a normal month and a busy month could cost after the switch.

Review the bill alongside handoffs, repeat contacts, and customer feedback. For a fuller cost review, see our [Zendesk pricing](https://www.bolddesk.com/blogs/zendesk-pricing) breakdown and [renewal checklist](https://www.bolddesk.com/blogs/zendesk-renewal-checklist).

### 7\. Plan the switch-on

Choose a quiet period and tell your support team who will watch the first conversations. Zendesk’s reporting dashboard can help you find a low-traffic window.

You can migrate an agent without activating it, so the original agent keeps running while you preview and test the new one. If a migration fails, the original agent stays active and you can retry.

Activating a new messaging agent interrupts conversations already in progress. Customers in those conversations are redirected to your default messaging response, and the new agent doesn’t remember what they told the old one.

Email isn’t affected; new emails go to the new agent.

Make final changes in the new agent, not the original. Edits to an Essential agent after migration don’t sync to the new one.

Start with your lowest-traffic agent, review the results, and then move higher-volume agents. If the original agent powered proactive messages, point them to the new agent after activation.

Watch the first live conversations and make sure someone can fix a failed route quickly.

### 8\. Review results before retiring old flows

Compare the first days of results with your baseline. Read a sample of conversations to check answer quality, article use, handoffs, and repeat contacts.

Confirm that every brand and channel reaches the intended new agent.

Update your team’s playbooks and keep historical reports available separately. Keep the old flow until the replacement has proven itself in live conversations.

If the migration prompts a wider platform review, our [Zendesk features](https://www.bolddesk.com/blogs/zendesk-features) review can help you assess what else your team uses.

## Download the Zendesk AI agent migration checklist

The spreadsheet version includes an inventory sheet, separate checklists for Essential agents, legacy bot builder agents, and autoreplies, a flow-mapping sheet, and a go-live sign-off sheet. Use it to assign owners, set due dates, and record evidence.

[Download checklist](https://www.bolddesk.com/wp-content/uploads/2026/11/zendesk-ai-agent-migration-checklist.xlsx)

## Should you stay with Zendesk or evaluate a different platform?

If your current Zendesk setup meets your needs, migrating to the new AI agent experience may be the simplest option. Test the new experience and review automated resolution costs before rollout.

If your Zendesk renewal is approaching, see [Zendesk to BoldDesk](https://www.bolddesk.com/alternative/zendesk) to learn about migration support and contract buyout options for eligible customers.

If you’re comparing customer service platforms, test the same customer requests on each one. [BoldDesk](https://www.bolddesk.com/) brings tickets, customer conversations, a knowledge base, workflows, and an [AI Support Agent](https://www.bolddesk.com/support-agent) together.

Its assisted [Zendesk migration](https://www.bolddesk.com/zendesk-free-migration) moves support data, while AI flows and handoffs are rebuilt and tested separately. Compare BoldDesk with your current setup in a [15-day free trial](https://app.bolddesk.com/signup/?utm_source=blog&utm_medium=referral&utm_campaign=bolddesk).

**Related articles**

-   [Zendesk vs. BoldDesk (2026): Which Platform Is Right for You?](https://www.bolddesk.com/blogs/zendesk-vs-bolddesk)
-   [Breaking Down Zendesk Pricing: How Much Does It Really Cost in 2026?](https://www.bolddesk.com/blogs/zendesk-pricing)
-   [14 Zendesk Features Reviewed: Strengths and Limitations](https://www.bolddesk.com/blogs/zendesk-features)

## FAQs about Zendesk AI agent migration

### Is Zendesk Answer Bot being shut down in 2027?

Partly. Setups that still use Essential AI agents, bot builder answers and intents, or article autoreplies are migrated in early 2027, and the old functionality is removed no later than June 2027.

“Answer Bot” is an older name that can refer to different configurations, so check which one your account uses.

### What happens if we don’t migrate before the deadline?

Zendesk migrates remaining Essential agents in January 2027 and remaining legacy agents from the beginning of February 2027, with some exceptions. Article autoreplies keep sending, but without article recommendations.

Zendesk also doesn’t explain how an automatically migrated bot builder flow will behave, so migrating on your own schedule is the only way to control the timing and test the new agent before customers use it.

### Who is affected by the Zendesk AI agent migration?

Customers on Zendesk Suite or Support plans who use AI agents - Essential, legacy bot builder answers and intents, or autoreplies with articles. Customers who bought the AI agents - Advanced add-on aren’t affected by this retirement.

### Is there a migration tool for legacy bot builder flows?

Not yet. Zendesk’s migration tool currently covers Essential AI agents only.

Zendesk says a tool for legacy agents is planned for later in 2026. Until it’s released, rebuild answers as dialogues and intents as use cases.

### Can I undo a Zendesk AI agent migration?

No. Zendesk states that migrating an Essential AI agent can’t be undone. Migrate the agent, test it, and activate it only when you’re ready to switch.

### Does Zendesk’s migration tool copy conversation history?

No. The tool carries over settings, instructions, knowledge sources, branding, language settings, and channel connections. It doesn’t move historical conversations, analytics, insights, or live conversation memory, so export the reports you need first.

### Can we migrate one agent that serves both email and messaging?

Yes. The tool creates two agents: one for messaging and one for email, web form, and API channels. They start with the same configuration, so update both when you change shared instructions.

### Why do some articles say Zendesk retires its bots on December 10, 2026?

That date came from earlier Zendesk documentation. Zendesk’s current removal notice uses January and February 2027 for automatic migration and June 2027 for removal.

### Does Zendesk AI Expert cost extra?

Yes. Zendesk describes AI Expert as a recurring service subscription. Contact Zendesk sales or your account team for pricing.

### Does moving from Zendesk to BoldDesk automatically recreate our bots?

No. BoldDesk’s assisted migration covers support data such as tickets, contacts, and knowledge base articles, while AI flows and workflows need to be configured and tested separately before cutover.

For broader migration planning, see our [customer service platform migration](https://www.bolddesk.com/guides/help-desk-migration) guide.

ABOUT THE AUTHOR

[![Picture of Cherine Apondi Okumu](https://secure.gravatar.com/avatar/f771b5bfe6b54a4cdcaf6b96f012bdad55108583d44bb0f3ad4e2933b156d445?s=300&d=mm&r=g)](https://www.bolddesk.com/author/cherine-apondi-okumu)

[Cherine Apondi Okumu](https://www.bolddesk.com/author/cherine-apondi-okumu)

Cherine is a content strategist at Syncfusion, combining her writing expertise with a passion for technology to produce clear and engaging content. Always eager to learn, she embraces new challenges and stays updated on trends that enhance customer support.

Connect with the author on [LinkedIn](https://www.linkedin.com/in/cherine-okumu-300030353/).

[Read more articles by this author](https://www.bolddesk.com/author/cherine-apondi-okumu) 

Be the first to get updates

## Explore more content

[![Light blue AI help desk dashboard with robot icon, email, phone, headset, chat icons, and support agents at laptops](https://www.bolddesk.com/wp-content/uploads/2026/09/AI-help-desk-for-small-teams-1024x546.webp)](https://www.bolddesk.com/blogs/ai-help-desk-for-small-teams)

### [A Complete Guide to AI Help Desk for Small Teams (5-40 Agents)](https://www.bolddesk.com/blogs/ai-help-desk-for-small-teams)

-   [by Cherine Apondi Okumu](https://www.bolddesk.com/author/cherine-apondi-okumu)
-   September 25, 2026

[![AI customer service in healthcare assistant supporting a clinician with secure patient communication, compliance, and medical guidance.](https://www.bolddesk.com/wp-content/uploads/2026/09/AI-customer-service-in-healthcare-1024x546.webp)](https://www.bolddesk.com/blogs/ai-customer-service-in-healthcare)

### [AI Customer Service in Healthcare: HIPAA, PHI, and Safe Use](https://www.bolddesk.com/blogs/ai-customer-service-in-healthcare)

-   [by Flavian Atieno Odongo](https://www.bolddesk.com/author/flavian-atieno-odongo)
-   September 23, 2026

[![AI customer service agent using analytics and automation tools to improve support performance.](https://www.bolddesk.com/wp-content/uploads/2026/09/AI-customer-service-business-case-1024x546.webp)](https://www.bolddesk.com/blogs/ai-customer-service-business-case)

### [The AI Customer Service Business Case: What 2026 Research Supports](https://www.bolddesk.com/blogs/ai-customer-service-business-case)

-   [by Gibson Amisi Kashi](https://www.bolddesk.com/author/gibson-amisi-kashi)
-   September 21, 2026
