Start using a password manager without locking yourself out
Secure the vault, migrate a few important accounts, test recovery and handle plain-text exports carefully.
In brief
A password manager stores unique credentials so one reused password does not connect all your accounts. The first job is securing the vault and its recovery, not importing everything and deleting the old method immediately.
Start with email and a few important accounts, then expand after you have confirmed access on the devices you actually use.
Understand recovery before migration
Find out whether a forgotten vault password can be recovered and by whom. Store the required emergency information somewhere secure and independent. Do not assume support can unlock an end-to-end encrypted vault merely because you can prove payment for the account.
Make a small migration work
Add the exact login URL, username and password for a known account. Test autofill on its genuine site, then change reused passwords to unique ones through that service. Inspect duplicate entries and old usernames rather than importing a list and assuming it is correct.
Handle exports as sensitive documents
If moving from another manager, read its export format and encryption status. Keep an unencrypted export off shared or synchronized folders and remove it after verifying the import, using appropriate device protections. Keep backups in a documented secure form; deleting the original vault before testing the replacement risks losing access.
Tools for this task
Before you act
The recovery options differ by product. An unlocked vault, exposed recovery material or a plain-text CSV export can reveal sensitive data.
What to do next
- Choose a manager whose device support and recovery model you understand.
- Create a strong unique vault credential, enable supported MFA and secure recovery information.
- Move a small set of accounts, test sign-in and recovery, then continue the migration.
