You are here:
Decide Whether to Migrate and When
The question isn’t whether to move to the new Agentforce Builder. It’s when to get started and what to bring with you.
The new Agentforce Builder in Agentforce Studio is the future of Agentforce, designed to empower you to build more powerful, more predictable, and more portable agents. It gives you more control over agents and guardrails, and it’s the home of all future Agentforce innovations and improvements. New agent creation moves to the new builder only starting the week of July 13, 2026. In short, if you're building or running Agentforce agents today, the new builder is for you.
Getting started with the new builder doesn’t necessarily mean migrating your existing agents. Whether to migrate an agent depends on your investment in your existing agents and your business goals.
- If you haven’t started building yet: Get started in the new builder. You don’t have an agent to migrate, but the content in Preparing to Migrate and Planning and Designing for Agent Script may still be useful for you.
- If you’ve started building an agent in the legacy builder and you’re not yet in production: This is a great time to make the switch. At this stage, you can choose to migrate the agent you’ve started working on to maintain your progress. Or you can redesign it from scratch when experimentation is low-risk.
- If you’re currently in production with an agent built in the legacy builder: Migration is for you. This guide walks you through planning, implementing, and validating your migration with minimal disruption, and all of the tools available to get you there.
- If you have an agent that’s outdated or no longer in use: Skip the upgrade. Archive or delete the agent in the legacy builder. If you need a replacement, start fresh in the new builder.
If you decide to migrate your existing agent, expect your agent to change—for the better. The new Agentforce Builder is based on a fundamentally different reasoning engine than the legacy builder. Previously, the prompt-based reasoning engine sent all instructions to the LLM in a single reasoning phase. Now, the graph-based reasoning engine separates the agent's run-time behavior into roughly two phases: deterministic execution followed by reasoning.
Because of this architectural change, instructions from your existing agent can perform differently when migrated as is. Some of your instructions may need to be refactored into new patterns, not just new syntax. You may find that some of your lengthiest, most repetitive instructions can be reduced to a sentence or two. And in some cases, you may find that it’s easier to take a fresh approach to instructions, designing them with the capabilities and affordances of Agent Script in mind, than to attempt to retrofit them. Agentforce and other tools, as well as strategies in this guide, can help you identify which instructions need changes and suggest improvements.
Here are some resources that can help you understand the new run-time behavior of agents built in the new builder.
