4

Importing data from Keepass or KeepassX

krikk edited this page 2024-04-10 20:26:12 +02:00

Table of Contents

• Introduction
• Different import results for Keepass and KeepassX
• Example
• Keepass database with name 'MyVault'
• Import via Keepass (CSV):
• Import via Keepass (XML):

Introduction

Bitwarden can import your data from a large number of applications.

The current importers let you only choose the format, not HOW the data is translated to Bitwarden.

Different import results for Keepass and KeepassX

Importing from Keepass or KeepassX gives complete different results, although they use the same Keepass 2.x kbdx database:

• Keepass CSV files are imported at the Organization level (owner of each entry) and translates the Keepass Groups into Bitwarden Collections.
• Keepass XML files are imported at the User level (owner of each entry) and translates the Keepass Groups into Bitwarden Folders with as main folder the name of the Keepass database.

It is a lot of work in Bitwarden itself to change Collections to Folders or to transfer ownership of all the entries. So depending on what you want, choose the appropriate method!

An alternative approach is to do the import with KP2BW - KeePass 2.x to Bitwarden Converter which supports more Keepass Features like file attachments, references and even more!

Example

Keepass database with name 'MyVault'

Groups:

• Group1
  • Group1Sub1
  • Group2Sub2
• Group2

Import via Keepass (CSV):

Owner = Organization

Collections:

• Group1
  • Group1Sub1
  • Group2Sub2
• Group2

Import via Keepass (XML):

Owner = Logged in User

Folders:

• MyVault
  • Group1
    • Group1Sub1
    • Group2Sub2
  • Group2

Note: you might have to create the main folder manually, as the import shows MyVault/Group1 as a Folder. Creating the folder MyVault shows the subfolders in the MMI.

Note2: you can edit the folders to remove the main folder 'MyVault', or edit the exported CSV file and remove the 'MyVault/' string in each entry before importing into Bitwarden.

FAQs

1. FAQs
2. Audits
3. Supporting upstream development

Troubleshooting

1. Logging
2. Bitwarden Android troubleshooting

Container Image Usage

1. Which container image to use
2. Starting a container
3. Using Docker Compose
4. Using Podman
5. Updating the vaultwarden image

Reverse Proxy

1. Proxy examples
2. Using an alternate base dir (subdir/subpath)

HTTPS

1. Enabling HTTPS
2. Running a private vaultwarden instance with Let's Encrypt certs

Configuration

1. Overview
2. Enabling admin page
3. SMTP configuration
4. Disable registration of new users
5. Disable invitations
6. Enabling WebSocket notifications
7. Enabling Mobile Client push notification
8. Other configuration

Database

1. Using the MariaDB (MySQL) Backend
2. Using the PostgreSQL Backend
3. Running without WAL enabled
4. Migrating from MariaDB (MySQL) to SQLite

Security

1. Hardening Guide
2. Password hint display
3. Enabling U2F and FIDO2 WebAuthn authentication
4. Enabling YubiKey OTP authentication
5. Fail2Ban Setup
6. Fail2Ban + ModSecurity + Traefik + Docker

Performance

1. Changing the API request size limit
2. Changing the number of workers

Customization

1. Translating the email templates
2. Translating admin page
3. Customize Vaultwarden CSS
4. Disabling or overriding the Vault interface hosting

Backup

1. General (not docker)
2. Backing up your vault

Development

1. Building binary
2. Building your own docker image
3. Git hooks
4. Differences from the upstream API implementation

Alternative deployments

1. Pre-built binaries
2. Creating a systemd service
3. Third-party packages
4. Deployment examples
5. Disable the admin token

Other Information

1. Importing data from Keepass or KeepassX
2. Changing persistent data location
3. Syncing users from LDAP
4. Caddy 2.x with Cloudflare DNS
5. Logrotate example