Skip to content

Migrate to and from other plugins

Jump to bottom
Rookiestyle edited this page Jan 18, 2021 · 2 revisions

KeePassOTP can import OTP data stored by KeeOTP and KeeTrayTOTP.
KeePassOTP can also export OTP data so that it can be processed by above plugins/applications.
KeePass2Android, KeePassXC and Strongbox use the same otpauth-format as KeePassOTP, no data migration is required.

KeePass

OTP data is stored in several fields as described here: KeePass otp

Restrictions when migrating OTP data from KeePass to KeePassOTP: None

Restrictions when migrating OTP data from KeePassOTP to Keepass:

  • Creation of of Steam OTP is not supported
  • KeePassOTP.TimeCorrection is ignored when migrating to KeeOTP
  • For HOTP, only SHA1 hash algorithm is supported
  • For HOTP, the only valid length is 6 digits

SHA1 are the default values, which means: As long as you were not explictly told to set different values in KeePassOTP's advanced option, you won't face any migration issues.

KeeOTP

OTP data is stored in a string field named otp and is set up like this:
key=<secret>&step=<step>&size=<size>

field meaning
key TOTP secret
step TOTP timestep, optional - default is 30 seconds
size OTP length, optional - default is 6 digits

Restrictions when migrating OTP data from KeeOTP to KeePassOTP: None

Restrictions when migrating OTP data from KeePassOTP to KeeOTP:

  • Only TOTP is supported by KeeOTP
  • Only BASE32 encoded OTP secrets are supported by KeeOTP
  • Only SHA1 hash algorithm is supported by KeeOTP
  • KeePassOTP.TimeCorrection is ignored when migrating to KeeOTP

BASE32 and SHA1 are the default values, which means: As long as you were not explictly told to set different values in KeePassOTP's advanced option, you won't face any migration issues.

KeeTrayTOTP / TrayTOTP

OTP data is stored in two string fields.

field meaning
TOTP Seed OTP secret
TOTP Settings additional parameters and is set up like this: <step>;<size>;<timecorrection_url>

TOTP settings:

field meaning
step TOTP timestep
size OTP length, S in case a Steam OTP is to be generated
timecorrection_url URL to compensate a huge time difference between your computer and the login page, optional

Restrictions when migrating OTP data from KeeTrayTOTP to KeePassOTP: None

Restrictions when migrating OTP data from KeePassOTP to KeeTrayTOTP:

  • Only TOTP is supported by KeeTrayTOTP
  • Only BASE32 encoded OTP secrets are supported by KeeTrayTOTP
  • Only SHA1 hash algorithm is supported by KeeTrayTOTP

BASE32 and SHA1 are the default values, which means: As long as you were not explictly told to set different values in KeePassOTP's advanced option, you won't face any migration issues.

Clone this wiki locally