We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.
ConsentLeg.Interest
label
label
label
label
Select An Org
Modal Body...
Upcoming Mandatory Changes to Public Key Infrastructure (PKI)Read More
Salesforce Enforces New Security Requirements in Summer 2026Read More
Identifies the configurations of a connected app and creates an identical external
client app to replace it. After connected app migration, the connected app remains in the App
Manager list but is read only.
Required Editions
Available in: Lightning Experience
Available in: Enterprise, Performance, Unlimited, and
Developer Editions with Foundations, or Agentforce 1 or Einstein
1 Editions
Note This action is no longer being updated. We recommend that you use Setup with Agentforce,
which can help with many more administrative tasks and is automatically updated with new
functionality. For more information, see Setup with Agentforce.
API Name
MigrateConnectedApp
Reference Action Type
Standard Action
Reference
Action
Migrate Connected App (migrateConnectedApp)
Does this action execute one or more prompt templates?
No
Guidelines and Considerations
This agent action calls the Migrate Connected App standard invocable action, which disables
the connected app and creates an external client app with identical settings and policies.
To provide a connected app summary, the agent might ask for the connected app's application
ID. The application ID is found in the URL for the connected app settings page. It's an
alphanumeric string that starts with 06P and appears in the URL after
applicationId%3D.
Before migrating the connected app to an external client app, you must identify the connected
app to migrate. Only local connected apps can be migrated to external client apps. Connected
apps that use the OAuth 2.0 Username Password flow can’t be migrated to external client apps,
because external client apps don’t support that flow.