<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content

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

Okta Classic Engine
Devices and Mobility
Okta Identity Engine

Overview

Okta Verify for iOS version 9.70.0 and later supports exporting third-party Time-Based One-Time Password (TOTP) accounts to a new device using Bluetooth. Android devices will receive this capability in a future release. For unsupported versions or platforms, users must manually re-enroll each third-party account in Okta Verify on the new device.

Applies To

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

Solution

Can Okta Verify import codes from other authenticator applications?

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.

 

Exporting Non-Okta Accounts to a New Device Depends on the Operating System and Application Version

Okta Verify for iOS version 9.70.0 and later allows users to transfer third-party TOTP accounts to a new device using Bluetooth. Android devices will support this feature in a future release.

 

For unsupported versions or platforms, Okta Verify does not synchronize or automatically transfer non-Okta One-Time Password (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 they lose access to the Okta Verify application on the original device.

 

Related References

Loading
Migrating, Importing, or Exporting Non-Okta MFA Codes in Okta Verify | Okta Support