Loading
Feature degradation | Gmail Email delivery failureRead More
Agentforce and Einstein Generative AI
Table of Contents
Filter by (0)Add
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

            Search all of Salesforce Help
            Search all of Salesforce Help
            Migrate from Agentforce (Default) to Agentforce Employee Agent

            You are here:

            1. Salesforce Help
            2. Docs
            3. Quickstart Your Einstein Generative AI Solution

            Migrate from Agentforce (Default) to Agentforce Employee Agent

            Discover the key differences between Agentforce (Default) and Agentforce Employee agent, and learn how to seamlessly migrate your default agents. The migration flow creates a new Employee agent with the same subagents and actions, variables and settings as your default agent. You can fine-tune your Agentforce (Default) agent into multiple employee agent personas, each specializing in different use cases, with improved access control and channel integrations.

            Required Editions

            Available in: Lightning Experience
            Available in: Enterprise, Performance, Unlimited, and Developer Editions. Required add-on licenses vary by agent type.
            User Permissions Needed  
            To build and manage Employee agents:

            Manage AI Agents

            OR

            Customize Application
            Important
            Important Starting June 17, 2025, Agentforce (Default) will not include new features or improvements and isn’t available in new Salesforce environments. We recommend migrating to Agentforce Employee agent for continued enhancements and support. If you plan to transition to Agentforce Employee agent or make related license changes, complete the migration of your existing Agentforce (Default) agents in advance to avoid potential disruption in agent availability. If you can't complete the migration in advance, you can create new agents after the transition, which can involve some downtime. See Migrate from Agentforce (Default) to Agentforce Employee Agent.

            What Are the Differences Between Agentforce (Default) and Agentforce Employee Agent?

            Compare Agentforce (Default) and Agentforce Employee Agent to understand differences in how agents are created, managed, and deployed. Use this comparison to decide which agent type fits your employee support needs.

            Capability Agentforce (Default) Agentforce Employee Agent
            Agent Creation Unlike other agent types, Agentforce (Default) is created by turning on the Enable the Agentforce (Default) Agent setting. Like other agent types, Agentforce Employee agents are created by launching the Agent Creator guided setup and selecting an Agentforce Employee Agent template.
            Multi-Agent Support You can only have one Agentforce (Default) agent per org. You can have multiple Agentforce Employee agents per org, so you can assist your employees with multiple, more tailored experiences.
            Template Support Agentforce (Default) doesn’t support templates. Agentforce Employee Agent supports templates, so you can quickly create agents for your employee use cases.
            User Access User access to Agentforce (Default) is managed through traditional permission set group assignments. User access to Agentforce Employee agents is managed with permission sets or profiles, in a convenient new user interface.
            Channel Support Agentforce (Default) can be deployed to Lightning Experience and the Salesforce mobile app. Agentforce Employee agents can be deployed to Lightning Experience, the Salesforce mobile app, and Slack. You can also connect Employee agents to Messaging for Web on Experience Cloud sites.
            Subagents & Actions Agentforce (Default) and Agentforce Employee agents have access to the same subagents and actions for employee use cases.
            Language Support Agentforce (Default) and Agentforce Employee agents support the same languages.

            How to Migrate from Agentforce (Default) to Agentforce Employee Agent

            Migrate from Agentforce (Default) to an Agentforce Employee agent in a few steps, with all configurations automatically carried over to the new agent.

            To migrate from Agentforce (Default) to Agentforce Employee Agent, you must have the required add-on license and Flex Credits provisioned. Plan to recreate any custom prompts, renamed actions, and visibility settings, such as permission sets or profiles that determine who can use the agent, in the new agent.

            1. From Setup, in the Quick Find box, enter Agents, and then select Agentforce Agents.
            2. From the dropdown menu for Agentforce (Default), select Migrate to an Employee Agent.
              If you don’t see the Migrate to an Employee Agent action, ensure Flex Credits are provisioned. Without Flex Credits, the migration tool isn’t available.
            3. Enter a name and API name for your Agentforce Employee agent.
            4. Click Create.
              The migration takes a few minutes, after which the new Agentforce Employee agent is ready to use. To use it, give users access and activate your agent.

            Manually Migrate Subagents and Actions from Agentforce (Default) to Agentforce Employee Agent

            Migrate from Agentforce (Default) to Agentforce Employee Agent to build agents for specific use cases, control access at the agent level, and connect to channels such as Lightning Experience, the Salesforce mobile app, and Slack.

            1. Create an agent from an Agentforce Employee agent template.
            2. Migrate your agent assets from Agentforce (Default) to your Agentforce Employee agent.
              1. If you use custom subagents or custom versions of standard subagents with Agentforce (Default), recreate them for your Agentforce Employee agent. Create a custom subagent, or add a standard subagent and edit it. We recommend copying and pasting your existing subagent fields, including instructions, into your new agent’s subagent fields.
              2. If you use custom actions with Agentforce (Default), add them to your Agentforce Employee agent. Your custom actions are available in the asset library and can be added to a custom subagent or a custom version of a standard subagent.
              3. If you use filters with Agentforce (Default), recreate them for your Agentforce Employee agent.
              4. If you use custom variables with Agentforce (Default), recreate them for your Agentforce Employee agent.
            3. If you use Agentforce Data Library with Agentforce (Default), assign your data library to your new Agentforce Employee agent.
            4. Give users access to your Agentforce Employee agent.
            5. Connect your Agentforce Employee agent to channels. Agentforce Employee agents can connect to Lightning Experience, the Salesforce mobile app, Slack, and Messaging for Web.
            6. Test your new agent to verify that it behaves as expected. To test individual conversations, start a preview conversation in Agentforce Builder. To test your agent’s behavior at scale, use Agentforce Testing Center. Learn more about testing and troubleshooting your agent.
            7. When you’re ready, activate your Agentforce Employee agent and deactivate Agentforce (Default).
             
            Loading
            Salesforce Help | Article