At Dreamforce ’25, Salesforce unveiled a completely redesigned Agentforce Builder, powered by a new declarative language called Agent Script. The original builder, which Salesforce now refers to as the Legacy Agentforce Builder, is still functional, but the platform’s future clearly sits with the new experience.
If you have agents live in production today, this article is for you. We are not walking through the migration steps. Salesforce documentation covers that well. Instead, we are explaining why the move from the legacy builder to the new one belongs on your roadmap now, rather than later.
The Legacy Builder Is Still Working, But It Is Standing Still
Agents built in the legacy Agentforce Builder continue to run, and Salesforce has confirmed they will continue to work for the foreseeable future. The catch is that the legacy builder is no longer where new investment is going. The enhanced Atlas Reasoning Engine, Agent Script, Agent Canvas, and the deeper observability tooling all live in the new builder.
That has a knock-on effect. Every future capability Salesforce releases is likely to land in the new builder first, and in most cases, only there. Agents stuck on the legacy platform will fall further behind in reasoning quality, debuggability, and integration depth as each release ships.
Salesforce Agenty Builder Migration Is a Project, Not a Sprint Task
The most important practical point is that moving an agent from the legacy builder to the new one is not a one-click upgrade. Each agent needs to be redeployed in the new builder, tested, and rolled into production individually. You cannot run both versions of the same agent in production simultaneously, so cutover planning is critical.
That makes the migration a scoped project rather than a developer task you slot into a sprint. It needs sandbox time, defined rollout windows, and someone responsible for validating behavior before go-live. Organizations with a portfolio of 10 or more agents should be planning the work now, even if execution occurs in phases.
What’s New in Agentforce Builder 2.0?
Once your agents are running in the new builder, the upgrade unlocks capabilities that were previously unavailable.
What Is Agent Script?
Agent Script is the headline feature. It is a declarative markup language built for the Atlas Reasoning Engine, giving builders full programmatic control over how an agent reasons, branches, and acts.
The legacy builder relied on topic-based configuration, leaving much of the agent’s behavior in a black box. Agent Script changes this by exposing explicit reasoning paths you can read, edit, and trace. Deterministic logic and natural-language prompts sit side by side, so you can hard-code the steps that must happen reliably and let the model handle the rest. Salesforce calls this Hybrid Reasoning.
What Is Agent Canvas?
Agent Canvas is the document-style, low-code editor that sits on top of Agent Script. It presents your agent configuration as clear, structured visual blocks, each one a readable summary of the underlying script.
The result is a single artifact that serves two audiences. Admins and business analysts build visually without writing code. Developers drop into the script directly when complexity demands it. Both views stay in sync, with the builder writing the Agent Script in the background as you visually edit. This removes the boundary that often stalls handoffs in legacy agent projects.
Better Observability and AI-Friendly Workflows
The new builder also brings improved testing and tracing tools, allowing teams to validate agent behavior with far greater visibility than the legacy experience provided. Because Agent Script is code, the new builder fits naturally into modern AI-assisted development workflows, including teams using the Salesforce MCP server with tools like Claude Code.
Plan the Move Before It Becomes Urgent
Migration is rarely a matter of if. It is a matter of when. The longer agents sit in the legacy builder, the larger the functionality gap grows between what your agents can do and what newly built agents can. Starting with one or two pilot migrations now lets you size the work, build confidence, and avoid scrambling later when timelines firm up.
Need Help Migrating Your Agentforce Agents?
Migrating a portfolio of production agents is rarely a one-person job. If you would like an experienced Salesforce consultancy to scope the work, redeploy your agents in the new builder, and validate behavior before go-live, Advanced Cloud Solutions can help.
Leave a Reply