Migrating, Importing, or Transferring Non-Okta MFA Codes in Okta Verify

While Okta Verify supports non-Okta OTP codes, it does not support importing existing Multi-Factor Authentication (MFA) codes from other authenticator applications or automatically transferring non-Okta OTP accounts between devices for security reasons. When configuring a new device, users must manually re-enroll each third-party account in Okta Verify on the new device.

• Okta Verify
• Multi-Factor Authentication (MFA) 
• Okta Identity Engine (OIE)
• Okta Classic Engine

Can Okta Verify import codes from other providers?

For security reasons, Okta Verify does not import or ingest existing MFA codes or seeds from other authenticator applications. Users must manually re-add third-party accounts to Okta Verify by re-enrolling within each individual service.

Transferring non-Okta accounts to a new device requires manual reconfiguration.

Okta Verify does not synchronize or automatically transfer non-Okta OTP accounts when users switch devices. Before discarding, wiping, or losing access to the original device, users must log in to each third-party service and reconfigure MFA on the new device.

NOTE: Users cannot retrieve non-Okta OTP codes if access to the Okta Verify application on the original device is lost.