Switching password managers does not have to mean exposing your credentials or starting from scratch. This password manager migration checklist walks through preparation, secure export, import verification, passkeys, shared vaults, browser autofill, and safe account deletion so you can move to a new provider with fewer surprises.
Overview
A password vault migration has two distinct risks: losing access to important records and creating a temporary copy of sensitive data that could be exposed. Treat the move as a controlled change, not a simple app installation. Keep the old vault available until the new one has been checked, and avoid deleting the old account immediately after an apparently successful import.
Before you begin, identify what you are moving. A vault may contain more than usernames and passwords, including secure notes, recovery codes, identity records, payment cards, Wi-Fi credentials, attachments, passkeys, shared folders, and emergency-access settings. Export and import tools do not always handle every item type in the same way.
Use this basic sequence:
- Prepare both accounts and your recovery methods.
- Review the source vault and remove unnecessary clutter.
- Export only through the provider's official application or website.
- Import into the destination vault using a supported format.
- Verify records, sharing, autofill, and recovery access.
- Securely remove temporary export files.
- Keep the old account available until your checks are complete.
For a work or family migration, document who owns each shared vault and who needs access before changing anything. A personal migration may be completed in one session; an organization-wide move should be tested with a small group first.
Checklist by scenario
Before exporting any vault
- Confirm that you can sign in to the destination account and access its recovery method.
- Save or verify the destination account's emergency recovery information, if the provider offers it.
- Update the source vault's master password if it is weak, reused, or known to be exposed.
- Install pending updates for the password-manager apps and browser extensions you will use.
- List important categories: logins, secure notes, identities, cards, recovery codes, attachments, shared items, and passkeys.
- Review duplicates, obsolete accounts, test records, and entries that should not be retained.
- Check whether the source supports an encrypted export. If the only available export is plain text, plan to create it on a trusted device and delete it immediately after import.
During export and import
- Use the official export workflow rather than a browser extension or unofficial conversion website.
- Work on a device you control, preferably one with disk encryption, screen locking, and current security updates.
- Do not email, message, or upload an unencrypted vault export for convenience.
- Confirm the file format selected for the destination provider. A mismatched format can produce an incomplete or incorrectly mapped import.
- Watch for fields that require manual mapping, such as custom fields, notes, folders, tags, and one-time-password secrets.
- Record the number of imported items and compare it with the source vault. The total will not always match exactly if duplicates or unsupported record types were removed, so investigate differences rather than assuming they are harmless.
If you use passkeys
Do not assume that passkeys move like ordinary passwords. Portability depends on the passkey's storage method, device platform, account provider, and the password manager's current capabilities. Before deleting the old vault, sign in to important services using the new arrangement or create an alternative sign-in method through the service's official security settings. Keep recovery codes in the new vault only after confirming that they work and are not outdated.
If you use shared or family vaults
- Identify every shared collection and its members before migration.
- Decide whether each item should remain shared, become private, or be moved to a different group.
- Verify permissions with a test account or a noncritical record.
- Confirm that former members no longer retain access where access should be removed.
- Check whether attachments, notes, and item history are included in the new sharing model.
If you use a password manager for work
Separate business records from personal records before exporting. Follow your organization's rules for handling credentials, service accounts, shared secrets, and administrator access. Test the migration with a limited, noncritical set of entries and define a rollback plan. Do not place company credentials in a personal vault or send an export to an unmanaged device.
After importing
- Open several high-value records, including email, banking, cloud administration, and identity-provider accounts.
- Test autofill without submitting a login form unnecessarily.
- Check that usernames, passwords, notes, URLs, time-based codes, and custom fields are intact.
- Verify browser extensions and mobile autofill settings on every device you use.
- Check emergency access, account recovery, shared vault permissions, and trusted contacts.
- Change passwords for critical accounts if an unencrypted export was created or stored in a location you cannot fully control.
What to double-check
| Area | What to verify | Why it matters |
|---|---|---|
| Export security | Whether the file is encrypted, where it is saved, and when it is deleted | An export can expose the entire vault outside the manager's normal protections. |
| Record coverage | Counts, folders, tags, secure notes, attachments, and custom fields | Importers may support ordinary logins better than less common record types. |
| Passkeys | Which passkeys transferred and whether critical services still accept them | Passkeys may follow different portability rules from passwords. |
| Shared access | Members, roles, collections, and removed users | A migration can unintentionally broaden or interrupt access. |
| Autofill | Browser, desktop, and mobile settings | Multiple installed extensions can cause incorrect or unsafe autofill behavior. |
| Recovery | Master-password recovery, emergency access, backup codes, and trusted devices | A working vault is not enough if you cannot recover it after device loss. |
Pay particular attention to high-impact accounts. Start with your primary email, identity provider, financial accounts, cloud consoles, source-code repositories, and domain registrar. These accounts can be used to reset or take over many others. If your phone number is part of account recovery, review its protections using this SIM swap and phone number security checklist.
Common mistakes
- Deleting the old vault too soon: Keep it read-only or otherwise unused until a deliberate verification pass is complete.
- Leaving an export on the desktop: Plain-text exports can remain in downloads folders, backups, sync services, or the recycle bin. Remove them from each location and empty the relevant trash or recycle area.
- Assuming a successful import is complete: A confirmation message may not identify unsupported notes, attachments, passkeys, or shared items.
- Keeping duplicate records indefinitely: Duplicates make it harder to know which password is current. Compare entries, preserve the newest verified record, and remove redundant copies.
- Forgetting browser and mobile settings: Disable the old autofill extension only after the new one works, then remove unused extensions and apps.
- Reusing the same master password: A provider change is a good time to create a unique, strong master password and store recovery information separately where appropriate.
- Migrating through untrusted tools: Online converters and scripts can receive the full contents of a vault. Use them only if you have assessed the code, handling, and trust model; otherwise, use an official format or manual transfer.
If you suspect the export was exposed, treat the vault as compromised: secure the destination account, rotate passwords for important services, revoke active sessions where available, and review account activity. A broader account review can follow the digital account security audit checklist.
When to revisit
Revisit this checklist whenever you change password-manager providers, replace a primary device, merge family or work vaults, or discover that a provider has changed its export, import, passkey, or recovery features. It is also useful before seasonal planning cycles when teams review access, shared credentials, and emergency procedures.
Set a reminder to review the migration result after a short period of normal use. Confirm that autofill behaves correctly, shared access remains appropriate, and no important account was left only in the old vault. Repeat a fuller credential cleanup periodically, especially after a breach notification, suspected phishing event, or major change to your devices. For incident-related guidance, see what to do after a data breach.
Final action: do not delete the old password manager until you have verified critical logins, passkeys, shared access, recovery options, and export cleanup. Once those checks pass, revoke old sessions, remove unused browser extensions and apps, securely delete temporary files, and close the old account only if you no longer need its records or recovery options.