Bring your passwords with you.
Easy migration should also be careful migration. Our plan starts with your source export, a local preview, and a report that accounts for every item.
Your vault belongs in the native app.
This website never accepts vault uploads. The future import workflow runs locally on your Mac. Local import foundations are implemented; migration coverage and release validation remain underway.
1Password
.1puxA local 1PUX importer is implemented in the development build. We’re checking field coverage and data preservation before recommending production migration.
Read the migration planBitwarden
Plaintext .jsonThe local JSON parser and import preview are implemented, with duplicate choices. Production migration coverage is still being validated.
Read the migration planApple Passwords
Mac .csvA local CSV parser, preview, and import workflow are implemented in development code. Source field coverage and authenticator migration are still being checked.
Read the migration planKeePass & KeePassXC
.kdbx evaluationKDBX4 is the development vault format. KeePass and KeePassXC migration will follow independent interoperability and field-preservation validation.
Read the migration planDashlane
CSV exportA provider-specific CSV importer is on the roadmap after the first three launch formats. We’ll validate the collection of exported files, not just a login sheet.
Read the migration planA little clarity at every step.
- 01
Export locally
Use your current manager’s official export guide. Protect the file; many formats contain readable secrets.
- 02
Preview the move
Inspect item counts, source vaults, duplicates, and unsupported data before writing to the destination.
- 03
Import & review
See which items moved, what was preserved, and anything that still needs your attention.
- 04
Verify & back up
Check sample logins and authenticator settings, make an encrypted backup, then clean up the source export.
A migration report is part of the feature.
Different source formats carry different data. Attachments, shared items, custom fields, and passkeys need specific checks. We’ll publish tested source versions and field coverage before labeling a provider supported.
See the release requirements