Upgrade
Clavitor imports from 14 sources — every major password manager, every Chromium browser, Firefox, and Safari. More than any other vault. Every field, every type, every custom entry.
Supported sources
If you've been storing passwords in your browser, that counts too. Chrome, Edge, Brave, Arc, Vivaldi, Opera — they all export the same CSV. Firefox has its own format and we support that as well.
Credentials, cards, identities, notes, SSH keys, software licenses, databases, servers. Full 1PUX and CSV support.
Credentials, cards, identities, notes, custom fields. JSON export.
Credentials, cards, identities, notes, TOTP, custom fields. Full JSON export including aliases.
Credentials, cards, identities, notes, SSH keys, software licenses, databases, Wi-Fi, servers. CSV export.
Credentials, cards, identities, notes, TOTP. CSV and JSON export.
Credentials, cards, identities, notes. CSV export.
Credentials, cards, identities, notes, SSH keys, TOTP, custom fields. JSON export.
Credentials, notes, custom strings. CSV export.
Credentials, notes, TOTP. CSV export with native TOTP support.
Credentials, identities, notes, custom fields. CSV export.
Credentials, cards, identities, notes, TOTP, custom fields. JSON export.
Chrome, Edge, Brave, Arc, Vivaldi, Opera — all use the same CSV format. Passwords and notes.
Passwords via CSV export. Separate format from Chromium.
Passwords and TOTP via CSV export with OTPAuth URIs. macOS and iOS.
What gets imported
Most password managers handle credentials and maybe cards. Clavitor imports 11 entry types — including SSH keys, databases, software licenses, and crypto wallets. If your old vault stored it, Clavitor keeps it.
| Clavitor | 1Password | Bitwarden | Proton | LastPass | Dashlane | |
|---|---|---|---|---|---|---|
| Credentials | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| TOTP / 2FA | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Cards | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Identities | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Secure Notes | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| SSH Keys | ✓ | ✓ | ✓ | |||
| Software Licenses | ✓ | ✓ | ✓ | |||
| Databases | ✓ | ✓ | ✓ | |||
| Wi-Fi | ✓ | ✓ | ||||
| Servers | ✓ | ✓ | ✓ | |||
| Crypto Wallets | ✓ | |||||
| Custom Fields | ✓ | ✓ | ✓ | ✓ | ✓ | |
| Per-field encryption tiers | ✓ |
How it works
Export from your current password manager — every one of them has an export function. Then drag the file into the Clavitor web UI. No cloud, no third party, no LLM ever touches your data. The importer maps every field deterministically based on the source format — it knows exactly where each password manager puts each field.
Every field is protected by vault encryption at rest. On top of that, sensitive fields get a second layer: passwords and API keys are encrypted again with Credential Encryption (L2) — your agents can decrypt these. Identity fields like card numbers, SSNs, and passport numbers get Identity Encryption (L3) — only your hardware key can unlock them. Two layers, always.
Custom fields, TOTP seeds, notes, attachments metadata — if your old vault stored it, Clavitor imports it. Fields that don't have a direct mapping become custom fields. Nothing is silently dropped.
Your old vault encrypted everything the same way. Clavitor assigns each field to the right tier automatically. Your SSN gets hardware-key protection. Your API keys stay agent-accessible. The right security for each piece of data.
On hosted plans, Clavitor recognizes API keys by pattern during import — OpenAI, AWS, GitHub, Stripe, and more. They're separated into their own category automatically, so your agents can find and use them without digging through generic password entries.