Move your passwords between managers without losing half of them

Every password manager exports CSV. No two agree on the column names, the order, or how a two-factor secret is written. Pick your route below and get a file the destination actually accepts — converted in your browser, never uploaded.

Popular migrations

• LastPass → Bitwarden
• Chrome → 1Password
• Chrome → Bitwarden
• LastPass → 1Password
• 1Password → Bitwarden
• Chrome → Apple
• Chrome → Proton Pass
• Bitwarden → 1Password
• LastPass → Proton Pass
• 1Password → Proton Pass
• Dashlane → Bitwarden
• Chrome → KeePassXC

See all 210 converters →

How it works

1. Export your vault from your current manager as CSV.
2. Drop it onto the converter for your route. It's parsed and rewritten in your browser tab.
3. Download the converted file and import it into the new manager.
4. Verify a handful of entries, then delete both files.

More on what happens to each field →

Would rather not do this online at all? Download the converter as one HTML file and run it from your own disk with the network switched off — same tool, no connection needed.

Supported managers

Bitwarden · 1Password · LastPass · Google Chrome · Dashlane · KeePassXC · NordPass · Proton Pass · Keeper · Mozilla Firefox · Apple Passwords · RoboForm · Enpass · Microsoft Edge · Safari

Why not just import the file directly?

Sometimes you can — a few managers ship a dedicated importer for the biggest competitors. But the common failure modes are quiet ones. LastPass files secure notes in the same CSV as logins and marks them with a fake http://sn URL, so a naive import turns every note into a broken login. Keeper reads its CSV positionally with no header row, so one column out of place shifts every password into the wrong field. Apple's Passwords app only accepts full otpauth:// URIs and silently ignores the bare Base32 secrets most managers export, which you discover the day you're locked out of an account. These converters handle those cases explicitly and tell you what didn't fit.