Migration

Switch from 1Password to HexVault

3 min · Export from 1Password, import to HexVault

Moving from 1Password to HexVault takes about five minutes: export a CSV, then import it. Your 1Password Secret Key protects your account, not the export file — so handle the exported file carefully and delete it afterward.

Where to import: open your HexVault vault and go to Settings → Data → Import Passwords, choose 1Password, and drop in the file you export below.

Step 1 — Export from 1Password

  • In 1Password 8: choose Export → CSV format (not .1pux).
  • In 1Password 7: File → Export → All Items → CSV.
  • Save the .csv (HexVault also accepts the legacy .1pif).

Handle the export file carefully. It is unencrypted plaintext — anyone who opens it has your passwords. Keep it only as long as the import takes, then delete it and empty your trash.

Step 2 — Import into HexVault

  • Open HexVault and go to Settings → Data → Import Passwords.
  • Choose 1Password as the source.
  • Drop in the CSV file you just exported. HexVault parses it and re-encrypts every entry in your browser with your master password before anything is sent — we only ever receive ciphertext.
  • Review the preview and confirm.

A note on the Secret Key

1Password’s Secret Key is a genuinely good defence: it means a leaked master password alone cannot open your vault. It also does not travel with your export — the CSV you produce is plaintext. HexVault reaches a similar goal differently, by making the master password itself expensive to attack with memory-hard Argon2id key derivation. See the full HexVault vs 1Password comparison →

Compare HexVault and 1Password in detail →

Step 3 — After you import

  • Delete the export file and empty your trash — it is plaintext.
  • Run a security check. HexVault flags reused, weak, and breached passwords so you can fix the worst first.
  • Turn on two-factor for your HexVault account.

Import happens in your browser: your file is parsed and re-encrypted locally with your master password before anything is sent. Your key is derived with Argon2id and entries are sealed with AES-256-GCM. How the encryption works →  ·  All import sources →