Einstein Bots to Agentforce is now a documented upgrade path: if your org still runs an Einstein Bot, Salesforce offers a faster way to start the move. At Dreamforce 2026, the company listed an Einstein Bots upgrade among its announcements, described as generally available. The idea: convert an existing bot into an Agentforce agent instead of rebuilding it from a blank screen.
This post covers what Salesforce documents about the conversion, what you should still plan to do by hand, and a cautious way to approach it. Where Salesforce has not published a detail, we say so. Use it as a planning guide for any Einstein Bots to Agentforce project.
Einstein Bots to Agentforce: what Salesforce actually announced
The announcement page says you can click Upgrade Agent on Agentforce Labs to convert an existing Einstein Bot into an Agentforce Service Agent or Help Agent. The Help documentation adds that the current bot keeps running while you review and adjust the new agent.
That last point matters. This is not a switch that flips your live bot off. The documented behavior is that the tool creates a separate agent, so the original bot stays available.
One status detail to watch
The Dreamforce page lists the feature as GA. However, the Salesforce Help article we opened, Create AI Agents From Einstein Bots (Beta), still labels the Upgrade Agent tool as a beta service governed by Beta Services Terms. Documentation often lags announcements, but we could not confirm which label is current for your org. Check the Help article and your release notes before you plan around either one.
Why this is happening: Einstein Bots is in Maintenance Mode
Salesforce Help states: “Starting August 17, 2026, Einstein Bots is in Maintenance Mode. Existing Einstein Bots continue to be supported and can be used after August 17, 2026. However, no new features or enhancements will be added, and we recommend using Agentforce for new AI agent implementations.” You can read it in the Create an Einstein Bot article.
In plain terms: your existing bots are supported and keep working, but they will not get new capabilities. We did not find an official end-of-life date in the pages we opened, so do not assume one exists or does not exist. Salesforce’s direction is clearly toward Agentforce, and that is the real reason to start planning.
What converts when you upgrade a bot to Agentforce
According to the Help documentation, in an Einstein Bots to Agentforce conversion the Upgrade Agent tool analyzes your bot configuration and generates matching Agentforce Service Agent components:
- Dialogs become subagents, based on grouped dialogs with similar intents.
- Action steps become agent actions.
- Intents are carried into the new agent structure.
A second Help article, Upgrade Einstein Bot to Agentforce Service Agent, describes the input more broadly as bot dialogs, intents, dialog steps, variables, entities and training data. Treat that as the scope the tool reads from, not a promise that every element comes across intact.
| Einstein Bot element | Becomes in the Agentforce Service Agent |
|---|---|
| Dialogs (grouped by similar intent) | Subagents |
| Action steps | Agent actions |
| Intents | Carried into the new agent structure |
| Flows, Apex, integrations | Reuse is possible, but must be reviewed and tested |
The first three rows of this Einstein Bots to Agentforce mapping come from Salesforce Help. The last row is our planning advice, not a Salesforce statement.
What does not convert, or is unclear
This is where you need to be careful. The Help article we reviewed does not list what fails to convert or any limitations, so treat the list of exclusions as unknown until you test a conversion yourself. Salesforce tells you to review and configure the new agent while the old bot stays live, so plan to test thoroughly before you switch any traffic.
Some community writers are more specific. The Concret migration guide argues that dialog trees, NLU training data and named conversation variables have no direct Agentforce equivalent, while Flows, Apex classes and external integrations can usually be reused with minor updates. A second community article makes a similar case. These are author opinions, not Salesforce statements, so use them as a prompt for your own review rather than as fact.
The practical lesson for Einstein Bots to Agentforce projects is the same either way: expect the conversion to give you a draft, not a finished agent.
Prerequisites for converting Einstein Bots to Agentforce
For Einstein Bots to Agentforce conversions, the Salesforce Help pages above list:
- Editions: Enterprise, Performance, Unlimited, or Developer Edition with Foundations or Agentforce 1 Editions. Enhanced Messaging channels have their own edition requirements.
- Interface: Lightning Experience.
- An existing Einstein Bot in a connected org, production or sandbox.
- Bot permissions: Customize Application, or Modify Metadata, or Manage Bots.
- Agent permissions: Manage Agentforce Service Agents and Manage AI Agents, plus Agentforce Default Admin or Customize Application.
The Help article describes two ways to run the conversion: the Agentforce Labs web tool, or a Claude Code route that uses Salesforce CLI (version 2.0.0 or later) and Salesforce’s published skills. With the web tool, a production org is added automatically, while a sandbox must be connected manually. You can also upload a bot package.
The pages we opened did not mention Data Cloud requirements for the conversion itself, so confirm this with your Salesforce account team rather than assuming either way.
What the Agentforce agent may cost
Salesforce does not appear to publish a price for the conversion tool itself. The cost question is about running the agent afterward. On its Agentforce pricing page, Salesforce lists Flex Credits at $500 per 100,000 credits, and also lists a per-conversation option at $2 per conversation. Prices and packaging change, so confirm current terms for your contract.
For any Einstein Bots to Agentforce plan, the key point for ops leaders is that usage-based models behave differently from a bot you have run for years. Model your real monthly conversation volume before you commit. If you are weighing options more broadly, our comparison of Claudeforce vs Agentforce may help frame the trade-offs.
Einstein Bots to Agentforce: a safe migration approach
1. Inventory your Einstein Bots before you convert
List every active bot, its dialogs, the Flows and Apex it calls, the channels it serves and its monthly volume. Find the dialogs that carry most of the traffic.
2. Convert in a sandbox first
Run the tool against a sandbox copy, and treat the first Einstein Bots to Agentforce run as a rehearsal. Because the original bot stays live, you can inspect the generated agent in Agentforce Builder without touching customers.
3. Review the Einstein Bots to Agentforce draft line by line
Check the generated subagents, actions and instructions against what your bot really does. Look for anything that did not carry across, and rebuild it deliberately.
4. Test with real conversation examples
Use anonymized transcripts from your own history. Test edge cases, escalation to a human, and anything involving sensitive data.
5. Consider a hybrid handoff
You do not have to cut over all at once. Salesforce documents how to transfer conversations from an enhanced bot to an Agentforce Service Agent using an Omni-Channel flow with a Route Work action. A Salesforce developer blog describes using the bot as a front-line router that passes complex inquiries to specialized agents. That lets you move one topic at a time.
6. Activate gradually
Turn the new agent on for one channel or one topic first, watch the results, and keep the old bot available until you are confident.
Release timing also matters. If you are lining up changes with your release calendar, see our notes on the Salesforce Winter ’27 release.
Einstein Bots to Agentforce pre-migration checklist
- Confirm your edition includes Foundations or Agentforce 1.
- Confirm the required bot and agent permissions are assigned.
- Document each bot’s dialogs, Flows, Apex and channels.
- Pull monthly conversation volume and escalation rates.
- Check the current status (beta or GA) of the Upgrade Agent tool.
- Ask Salesforce about Data Cloud and pricing for your contract.
- Pick one low-risk, high-volume topic to start with.
- Run the first conversion in a sandbox.
- Define human escalation and test it.
- Decide who signs off before activation.
Einstein Bots to Agentforce: frequently asked questions
Does the conversion replace my live bot?
No. Salesforce says the tool creates the new agent separately, so your existing bot remains available while you review and configure the new agent. Plan to test the new agent before you route any live traffic to it.
Is Einstein Bots being shut down?
Not according to the pages we opened. Salesforce says Einstein Bots entered Maintenance Mode on August 17, 2026: existing bots remain supported, but no new features or enhancements are coming. We found no official end-of-life date.
What do I need before I can convert a bot?
You need an Enterprise, Performance, Unlimited or Developer Edition org with Foundations or Agentforce 1, Lightning Experience, an existing bot, and the bot and agent permissions listed above.
Will everything in my bot carry over?
Do not assume so. Dialogs, action steps and intents are converted, but Salesforce’s Help article does not list what is left out, so we could not confirm exclusions. Plan to review and rebuild some pieces manually.
How much will the new agent cost?
The conversion tool’s cost is not stated in the sources we opened. Running the agent is priced separately; Salesforce lists Flex Credits at $500 per 100,000 credits and a $2 per conversation option. Confirm current pricing for your contract.
Getting help with the move
Einstein Bots to Agentforce conversion is the easy part. Deciding what the agent should do, how it hands off to people, and what it will cost to run takes planning. If you want a second set of eyes, Ashapura Softech can help through our Salesforce Agentforce consulting services, and you can contact us to talk it through. If you are still choosing a partner, our Agentforce implementation partner guide explains what to look for.
