How to Switch Password Managers Safely in 2026

Switching password managers is manageable, but the export file can contain your entire digital identity in readable form. The safest migration is staged: prepare recovery, use an encrypted export when the destination supports it, validate important accounts, and keep the old manager until you have a tested fallback.

This guide is provider-neutral. Import formats, passkey support, shared-vault permissions, and two-factor-token handling vary by the exact products involved.

Before exporting

Confirm that you can still sign in to the old manager and that its account email, recovery method, and emergency material are current.
Create a recovery plan for the new manager: account password, Secret Key or equivalent setup material, emergency contact, and an offline copy where appropriate.
List the accounts that matter most: primary email, banking, domain registrar, cloud storage, payment services, and the accounts used to recover everything else.
Check whether the destination supports your source's native format. If not, plan a temporary conversion and expect some fields, attachments, passkeys, or shared-vault permissions to require manual work.
Decide whether the old and new managers will overlap briefly. Do not delete the old vault before you have validated the new one.

Use the safest export format available

Prefer a password-protected or encrypted export that the destination can actually import. Bitwarden's current documentation distinguishes encrypted JSON from plaintext CSV/JSON and recommends encrypted JSON for security and completeness; an account-restricted export may only work in the account that created it, while a password-protected export is intended for another account.

Bitwarden export formats and warnings

If your migration requires CSV or plaintext JSON:

Export on a trusted, updated device rather than a public computer.
Do not email the file, upload it to a general cloud folder, or leave it in Downloads.
Import it immediately into the intended destination and confirm the destination accepted the expected number of items.
Delete every copy, including temporary conversion files and cloud-sync copies. Emptying the recycle bin helps, but no deletion method can guarantee recovery is impossible on every SSD, backup system, or malware-infected device.
If you suspect the file was exposed, change the affected passwords from the new vault and revoke active sessions where the service supports it.

Do not confuse an encrypted export with a universal backup. Some encrypted formats are account-specific or cannot be imported by another provider.

Import in a controlled order

Import a small sample first if the destination allows it. Then:

Import the remaining logins, secure notes, identities, and cards.
Check for duplicate items. Some importers create a new record for every row instead of matching existing entries.
Verify usernames, URLs, custom fields, attachments, notes, folders, and collections.
Recreate shared vaults, family permissions, and organization collections manually when the export does not preserve them.
Do not purge the old vault until the new manager reports the expected item count and you have tested the critical accounts.

Bitwarden documents that imports may create duplicates and that unsupported formats may need conditioning. That is a useful warning even when Bitwarden is not your destination.

Bitwarden import FAQ

TOTP, passkeys, and recovery codes need special handling

Password records are not the whole account. A migration may not carry over:

TOTP seeds or authenticator-app entries.
Passkeys stored by the old manager or device platform.
Recovery codes, security keys, trusted-device state, and active sessions.
Shared-vault permissions, emergency contacts, and administrator roles.

Before disabling the old manager, sign in to each critical service and confirm its second factor works from the new setup. Keep recovery codes in the new manager only after you have tested them, and keep at least one offline recovery path for the password manager itself.

For example, Bitwarden documents that vault-synced TOTP data is exported separately from Bitwarden Authenticator exports. That is why “the import completed” is not proof that two-factor access transferred.

Bitwarden Authenticator import/export details

Validate the new vault before rotating everything

Use a checklist, not memory. Test:

Primary email sign-in and password reset.
Banking and payment sites without making a live transaction.
Domain registrar and hosting accounts.
Cloud storage and social accounts.
Browser autofill on each device and browser profile.
Mobile autofill and passkey prompts.
Shared vault access for every family or team member.
Emergency or account-recovery procedures.

If a password was reused or weak, migrate first and then rotate it in priority order. Rotating hundreds of passwords during an unverified migration makes it harder to determine whether a failure came from the old credential, the new vault, or a broken recovery flow.

Keep the old manager temporarily

Keep the old account available while you validate important logins and discover records that did not import. Disable its browser extension or autofill if the two managers compete, but do not delete the account just because the new app opens successfully.

After validation:

Export an encrypted backup from the new manager if its format is recoverable and suitable for your use.
Record the new manager's recovery instructions and renewal terms.
Sign out of and uninstall the old manager's apps and extensions.
Delete plaintext exports and conversion files.
Close the old account only after checking its deletion and retention policy and confirming that no shared vault or family member still depends on it.

What not to do

Do not paste a plaintext vault into an online converter.
Do not send the export through email or a chat app.
Do not publish a backup to a repository or shared drive.
Do not delete the old manager before testing recovery and autofill.
Do not assume TOTP, passkeys, attachments, or organization permissions transferred.
Do not rotate every account simultaneously without a prioritized recovery plan.

Frequently asked questions

Is CSV safe for a password-manager migration?

CSV is useful for compatibility but normally contains readable secrets. Use it only when necessary, minimize its lifetime, avoid copies, and delete it immediately after validating the import. Use an encrypted destination-supported export when possible.

How long should I keep the old manager?

There is no universal number of days. Keep it until your highest-risk accounts, second factors, shared access, and recovery process have all been tested. The correct stopping point is evidence, not a calendar deadline.

Will my two-factor codes transfer?

Not necessarily. TOTP and authenticator exports are product-specific, and passkeys may be stored separately from ordinary login fields. Confirm each critical account's second factor manually.

Should I change all my passwords after switching?

Change weak, reused, exposed, or high-value passwords first. A migration alone does not require an indiscriminate reset if the export was handled safely, but an exposed plaintext export should be treated as a credential incident.

Bottom line

A safe password-manager switch is a controlled migration: prepare recovery, use an encrypted export when it is genuinely portable, protect any plaintext file, validate critical accounts and second factors, keep the old manager until the evidence is good, then remove every temporary copy. The destination's import screen saying “complete” is only one checkpoint—not proof that your passwords, passkeys, TOTP, attachments, and shared access all survived.