Migrate a Local Connected App to an External Client App

Use the automated process to create a local external client app that replaces your existing local connected app. 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
Tip
Tip Instead of completing this task manually, get help from Setup with Agentforce. For example, tell the Setup agent, “Migrate the Acme connected app to an external client app.” For more information, see Identity Management in Setup with Agentforce.
  1. From Setup, in the Quick Find box, enter App Manager, and then select App Manager.
  2. 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.
  3. Click Migrate to External Client App.
  4. Confirm that the app is local and that it doesn’t use the username-password flow.
  5. 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. After it's created, make all changes to the new external client app. Changes made to the external client app don’t change the read-only connected app that created it. If you delete the external client app, then the connected app becomes active again. However, 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.