LastPass
CSV export → preview → import. Two-factor codes come along.
Switch
Moving your passwords works like moving house: pack a box in your old app (the export), carry it over, unpack it here, and then — this part matters most — get rid of the box.
tigerpassword figures out what kind of file you gave it, shows a preview first — "here is what I would add" — and writes nothing until you add --commit. Items that already exist are skipped rather than doubled. Nothing is ever sent over the internet; the file is read on your computer.
vault-cli import ~/my.vault ~/Downloads/export-file
vault-cli import ~/my.vault ~/Downloads/export-file --commit
Each one tells you where that app hides its export button and what comes across.
CSV export → preview → import. Two-factor codes come along.
1PUX export with attachments and passkeys where included.
Plain JSON export (not the encrypted one).
No export: the .kdbx opens directly with your KeePass password.
Each browser exports a CSV from its password settings; the same one-line import reads it.
SafeInCloud XML, a generic CSV with a column mapper, and Electrum, Sparrow and MetaMask wallet files (seed phrases stored safely).
--keep-duplicates if you truly want copies.Comparing before you decide? Every manager in one table · vs 1Password · vs Bitwarden