Migrating Default Agentforce Agents
- Agentforce, Salesforce, CRM
- June 28, 2025
Table of Contents
Info
This post explains why Salesforce’s default Agentforce framework is being deprecated — and how to recreate your default agent using the new Agentforce Employee Agent (AEA) framework.
Why You Need to Migrate Your Default Agentforce Agent
Salesforce’s Agentforce framework is evolving. The next phase? The Agentforce Employee Agent (AEA) — Salesforce’s new standard for internal AI agents that help employees handle CRM tasks with less friction.
If you’re still using the default Agentforce framework, heads up: it’s now deprecated and will be removed in a future release. If you rely on the default agent built on that old foundation, it will stop working when the old framework is retired.
There’s no automatic upgrade — you’ll need to manually recreate your default agent using the new AEA framework to keep your workflows running smoothly and unlock the latest AI improvements.
What’s Actually Changing?
The default Agentforce framework made it easy to spin up a basic AI agent for common internal tasks — like record lookups or summaries. But the new Agentforce Employee Agent framework (AEA) takes that same idea and gives it a bigger engine.
By moving to AEA, you get:
- Smarter orchestration for multi-step tasks
- More advanced prompt templates and flows
- Better performance and reliability
- A solid base for future AI agent features
Custom agents you’ve already built are not affected by this change — but if they’re on the old foundation, upgrading them to AEA can be a smart move too.
How to Recreate Your Agent
This is important: there’s no “Migrate” button. Migration here means rebuilding.
Here’s what to do:
- Check for your default agent
- Open Agent Builder in Salesforce.
- Confirm you still have a default agent that uses the old framework.
- Recreate it in AEA
- In Agent Builder, create a new agent — this time using the Agentforce Employee Agent (AEA) framework.
- Rebuild the same logic, prompt templates, and any related flows.
- Test thoroughly to make sure the new agent works as expected.
- Replace and remove
- Once your AEA version is live, retire or delete the old default agent to avoid confusion.
No Hard Deadline — But Don’t Wait
Salesforce hasn’t published a specific end-of-life date yet — the docs just confirm the default framework will be removed in a future release.
That means you technically have time — but waiting too long risks a last-minute scramble. It’s best to rebuild now while you can test and refine without pressure.
Should You Upgrade Custom Agents Too?
You don’t have to — but it’s worth a look. If your custom agents are built on the old default base, moving them to the AEA framework means better orchestration and future compatibility.
And if you’re planning new internal agents, you should definitely build them in AEA from day one.
Final Thoughts
Salesforce’s Agentforce Employee Agent is the next logical step in making AI more useful for everyday CRM work — not just for customers, but for your team too.
Rebuilding your default agent on the AEA framework is your chance to modernize what you already have — and set your team up to do even more with AI moving forward.
✅ Need help planning your rebuild, refining your flows, or exploring what else AEA can do? Contact Built With Intent — we’ll help you get it right.
Sources
For further details, see the official Salesforce docs.
