Create an External Client App from a Connected App
Use the automated process to create external client apps that replace your existing
local connected apps. After migration, the old connected app remains as a read-only version in App
Manager. External client apps created through migration are secure.
Required Editions
Available in: Lightning Experience
Available in: Professional, Performance, Unlimited, and
Developer Editions
User Permissions Needed
To create local External Client Apps
Create, edit, and delete External Client Apps
From Setup, in the Quick Find box, enter App Manager, and then
select App Manager.
Open the connected app by clicking the name.
If the connected app is eligible for migration, the Migrate to External Client
App button is available.
Click Migrate to External Client App.
Confirm that the app is local and that it doesn’t use the username-password flow.
Click Migrate.
A window opens with a link to the new external client app.
After an external client app is created from a connected app, the connected app remains
as a read-only version. All changes must be made to the new external client app. The changes
made to the external client app don’t change the read-only connected app that created the
external client app. If the external client app is deleted, then the connected app becomes
active again, but the settings and policies remain as they were when the external client app
was created.
After migration, the migrated connected app doesn't show up in
Notification Delivery Settings or the Briefcase connected app assignment.
Did this article solve your issue?
Let us know so we can improve!
Loading
Salesforce Help | Article
Cookie Consent Manager
General Information
Required Cookies
Functional Cookies
Advertising Cookies
General Information
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.