Importing passwords into V4ult
V4ult can import credentials from a CSV file exported by another password manager or browser, with automatic column detection for Chrome, Bitwarden, LastPass and KeePass, and manual mapping for anything else.
V4ult's importer (Profile → Settings → Import) reads a CSV file and lets you map its columns to V4ult's credential fields: name, username, password, URL and notes.
For four common export formats — Chrome, Bitwarden, LastPass and KeePass — V4ult recognizes the column headers automatically and pre-fills the mapping, based on the header row of the CSV. If your export comes from a different manager (1Password, Dashlane, NordPass, Proton Pass, Safari, Firefox, Edge, etc.), the import still works: you just map each column to the right field yourself in the same screen.
What's important to know before migrating: this importer only brings in login credentials (name, username, password, URL, notes). It does not import OTP/TOTP secrets, cards, identification documents, QR codes or secure notes, even if your old manager's export includes them — those need to be added to V4ult separately after the import. Every imported credential is encrypted on-device with the same AES-256-GCM used for credentials created manually; import respects your plan's credential limit and won't exceed it.
Advantages
- Automatic column detection for four common export formats
- Manual mapping covers any other CSV-exporting password manager
- Imported credentials get the same on-device encryption as manually entered ones
Related
Frequently asked questions
Which password managers does V4ult auto-detect when importing?
Chrome, Bitwarden, LastPass and KeePass CSV exports are recognized automatically. Any other CSV export can still be imported by mapping its columns manually.
Does importing bring over two-factor codes, cards or notes too?
No. V4ult's importer only transfers login credentials (name, username, password, URL, notes). OTP secrets, cards, identification documents, QR codes and secure notes are not imported and need to be added separately.
Is imported data encrypted the same way as data I type in manually?
Yes. Each imported credential is encrypted on-device with AES-256-GCM before syncing, exactly like a credential created through the normal form.