If you tried to create a new agent in Salesforce over the past few months, you may already have noticed: the button in Setup is gone. Agents are now built in the new Agentforce Builder, and their logic is defined in Agent Script. For orgs that already run agents, that raises a practical question. Do you need to do anything, and if so, when?

What has changed

Salesforce made the new Agentforce Builder available in February 2026, alongside the existing builder. Since the week of 13 July 2026 that is no longer a choice: new agents can only be created in the new builder. You find it in Agentforce Studio, through the App Launcher.

For existing agents nothing changes for now. Salesforce states on its own migration page that agents built in the legacy builder keep working and remain editable. No retirement date has been announced. Salesforce does say that no new features or enhancements are planned for the legacy builder. All new development goes into the new one.

What makes Agent Script different

In the legacy builder you described an agent mainly through instructions in plain language. The language model then decided for itself which step to take. That works, but it makes behaviour hard to predict and hard to test.

Agent Script combines that open reasoning with fixed logic. You define in script what must always happen in a particular way, for example a check before a record is updated, and leave the language model free only where flexibility is needed. The builder offers a Canvas view and a Script view, so admins and developers can work on the same agent.

Some capabilities are only available in the new builder. Salesforce lists, among others:

  • Agent Script itself, with its mix of fixed and open logic;
  • choosing a language model per part of the agent;
  • agents that orchestrate other agents;
  • Agentforce Voice.

Migrating: when and how

Because legacy agents keep running, there is no deadline forcing your hand. Still, it is wise not to let it drift. Every new capability passes your existing agents by, and the longer you wait, the more has to change at once later on.

Salesforce offers two routes: an upgrade tool in Agentforce Studio that converts an agent to Agent Script, and a CLI-based approach for teams that work with version control. Note one detail: as soon as you activate the rebuilt agent, Salesforce automatically deactivates the legacy version. So test first, and only activate once the new version behaves the way you expect.

A migration is also a good moment to review which data and actions an agent is allowed to use. That applies in particular to agents that process information from outside, such as leads from a web form. Treat that input as untrusted and give the agent no broader permissions than its task requires.

Not every AI step needs an agent

An agent is strong when a conversation can go in several directions. Many AI uses in Salesforce are simpler: writing a summary, drafting an email or classifying a field at a fixed point in a process. A full agent is often more than that requires. With our AI Prompt Builder you call a language model as a step in an ordinary Salesforce Flow, with a fixed prompt and a predictable outcome.

Not sure which agents to migrate, or whether an agent is the right solution at all? Our page on Agentforce explains how we design and configure agents. Get in touch and we will review your org together.