Hi everyone,
I’m new to Bitwarden/Vaultwarden and coming from a KeePass background. I’m currently setting up self-hosted Vaultwarden Instance on a virtual server at work and need to migrate multiple separate KeePass databases. My question is not about the import process itself but rather the best way to structure and manage these databases within Bitwarden/Vaultwarden, as the organisation/collection/folder structure is not 100% clear to me.
My current idea:
- One organization for the company
- Three collections, each representing one of the former KeePass databases
- Inside each collection, use folders to replicate the existing KeePass categories
My question: Is this the best approach or is there a better way to handle multiple separate databases in Vaultwarden? Maybe 3 organisations and different collections as folders? (but I guess the users would have to register seperatly for each organization/database?
Has anyone set up a similar structure and can share their experience or suggest improvements? Thanks in advance!
This is our current structure:
Database 1: IT Administration
│
├── Server Access
│ ├── Entry 1
│ ├── Entry 2
│
├── Network
│ ├── Entry 3
│ ├── Entry 4
│
├── Cloud Services
│ ├── Entry 5
│ ├── Entry 6
Database 2: Employee Credentials
│
├── Email & Communication
│ ├── Entry 7
│ ├── Entry 8
│ [...]
