Import & Export FAQs
This article contains frequently asked questions (FAQs) regarding import & export.
A: If we don't have official support for the service you are using, manually condition a
.json for import into Bitwarden. For more information about how to do this, see Condition a Bitwarden .csv or .json.
A: As of Safari 15.0, you can export passwords from Safari in a
.csv file. Once you do, condition your .csv to meet Bitwarden's format and import your data.
A: You can import items into existing collections by appropriately conditioning a
.json before before importing, or you can define new collections within your import file on order to create new collections when you upload the file. Learn how.
A: File attachments must be manually migrated to your Bitwarden vault, as they are currently not included in bulk import operations.
Please note that storage of file attachments is available only for premium users, including members of paid organizations (families, teams, or enterprise).
A: Every import operation creates every new record as an item in your vault, regardless of whether matching vault items already exist in your vault. Prior to import, we recommend either:
Editing your import file to only include net-new vault Items.
Purging your vault before an import operation.
Individual vaults can be purged from the Settings → My Account page. Organization vaults can be purged from the Organization Settings → Organization Info page.
A: The following formats are supported out-of-the-box:
If your format is not listed below, manually condition a Bitwarden .csv or .json.
Ascendo DataVault (csv)
Avast Passwords (csv)
Avast Passwords (json)
BlackBerry Password Keeper (csv)
F-Secure KEY (fsk)
GNOME Passwords and Keys/Seahorse (json)
Kaspersky Password Manager (txt)
KeePass 2 (xml)
Password Agent (csv)
Password Boss (json)
Password Dragon (xml)
Password Safe (xml)
Sticky Password (xml)
True Key (csv)
Universal Password Manager (csv)
Zoho Vault (csv)