Bitwarden JSON Import to Passary
By Mihaly Kertesz · Updated
Passary’s Bitwarden importer accepts unencrypted JSON. This path does not decrypt Bitwarden encrypted exports or import an attachment ZIP. The readable JSON serves as a temporary migration file; compatible encrypted backups serve a different recovery purpose.
Bitwarden import JSON formats
Bitwarden offers readable and encrypted export formats. Passary rejects exports marked encrypted, while CSV uses a different schema from the JSON importer.
Bitwarden’s documented export controls identify the current options for each client. Unencrypted JSON remains readable throughout migration, including in any synchronized copies. Fictional values are sufficient for format support examples.
Bitwarden: export formats and coverage · Encrypted backups and migration formats
Bitwarden import item coverage
Organization-owned entries and attachments have separate export rules. A personal export may not contain every item visible through an account. Organization policy also determines whether work-owned records may be transferred.
Passary maps supported login, note, card and identity fields, folders, URL matching, custom fields and recognized TOTP data. Mapping support does not establish an equivalent for every Bitwarden feature or future item type.
| Data | Verification task |
|---|---|
| Logins | URLs, username, password and matching behavior |
| Notes/custom fields | Punctuation, Unicode and field types |
| Cards/identities | Individual mapped fields |
| TOTP | Stored secret, import status and supported behavior |
| Attachments/passkeys/organization data | Separate documented transfer and recovery scope |
Bitwarden import into a Passary vault
An encrypted pre-import copy preserves an existing destination. Passary’s Bitwarden action reads the selected JSON and reports outcomes inside the unlocked vault. The source vault remains available while the destination’s contents are compared.
- Destination vault and pre-import backup
- Unencrypted JSON from the intended Bitwarden account
- Bitwarden import action in Passary
- Imported, skipped and duplicate or conflict outcomes
- Representative supported item types
- Independent encrypted destination backup
Bitwarden import practice JSON
The downloadable file contains four invented records: a login, a secure note, an unusable card example and a fictional identity. It includes two login URLs, a folder, a custom field and a Unicode note with quotation marks. Its password and card fields are public, unusable examples.
Automated checks parse these exact bytes through Passary’s web JSON importer with four records and no skipped rows. Selected fields and the folder relationship are preserved. Separate checks reject the structure when marked encrypted and count an unsupported item as skipped. The sample is authored test data, not a Bitwarden account export or evidence of a completed vendor UI or Windows migration.
| Practice record | Expected parsed outcome |
|---|---|
| Login | Two URLs, fictional password, custom field and note |
| Secure note | Text including its second line |
| Unusable card | The literal NOT_A_REAL_CARD field |
| Fictional identity | reader@example.org and invented name |
| Folder | One folder associated with all four records |
Fictional JSON practice file · Practice-file sizes, hashes and evidence limits
Bitwarden import errors and skipped items
Encrypted-export rejection means the format is unsupported by this path; it does not indicate an incorrect export password. Malformed JSON can result from an incomplete download or a different format. A fresh source export helps distinguish file damage from unsupported structure.
Invented values can reproduce a skipped item or mapping difference without disclosing a password, TOTP seed or private note. The field type and sanitized error are more useful for format diagnosis than real secret contents.
Bitwarden import recovery and plaintext cleanup
A restore of a copied destination backup establishes a recovery path before the old vault is retired. Critical entries and account-specific recovery material matter alongside total counts.
Unencrypted migration JSON can remain in temporary and deleted-file locations. A compatible encrypted backup provides protected recovery storage; the migration JSON does not.