Source instructions: Bitwarden web app documentation. UnumVault parser coverage uses synthetic fixtures; source-version migration is still under validation.
Reference documentation reviewed 14 October 2026.
Export from your current app.
- Sync your Bitwarden vault so the export reflects your latest items.
- In the web app, open Tools → Export and choose your individual vault.
- Select .json, the plaintext format, for the initial planned UnumVault importer.
- Confirm the export and save it locally. Keep it private until the import is verified.
What we’re validating.
- The development importer maps basic credentials, notes, and supported authenticator values.
- Launch validation covers richer item types, custom fields, folders, reporting, and duplicate handling.
- Unsupported passkey or item data must appear in the migration report.
Know what needs extra care.
- Plaintext JSON is different from encrypted JSON. Encrypted exports are outside the first importer’s scope.
- Bitwarden’s JSON includes richer item types than CSV; attachments use a separate ZIP route.
- Individual exports exclude organization-owned data. Trash and Sends are excluded from exports.
- Account-restricted encrypted exports are tied to the originating Bitwarden account.
Finish the move with confidence.
Our release workflow will ask you to review the report, verify representative credentials and authenticator settings, and create an encrypted backup. Keep your source manager available until all unresolved items have a migration action.
Remove plaintext exports when you’re done and check for extra copies in Downloads, Trash, backups, or synced folders. Deleting a file does not guarantee secure erasure.