App branding migration
App branding migration lets you upgrade your org to Identity Engine while keeping your existing apps and Okta-hosted brand experiences on Classic Engine. This lets you migrate each app and brand to Identity Engine on your own schedule, which limits the risk of disrupting your users.
Most orgs upgrade to Identity Engine in a single step using the self-service upgrade process. Use app branding migration instead if any of your apps use a customized, Okta-hosted sign-in experience that you need to migrate on its own schedule, separately from the rest of your org.
Okta's own first-party apps, such as the Admin Console, are automatically upgraded and always run on Identity Engine. You don't need to fix every customized app before you upgrade: move your lowest-risk apps first, confirm that each one works, and roll back a single app to Classic Engine if it doesn't. Every other app keeps its existing Classic Engine pipeline until you switch it, but it can't use the Identity Engine capabilities that your org gained by upgrading, such as Okta FastPass, device assurance policies, Identity Engine authentication policies, and self-service registration.
When you enable app branding migration, Okta clones your existing Classic Engine brands into Identity Engine brands, so you can prepare your Identity Engine sign-in experience without touching your live Classic Engine customizations. When you're ready, switch to the new Identity Engine brand.
To complete your upgrade using app branding migration, follow these steps: