Moving 545 Passwords from Bitwarden's Cloud to Vaultwarden: the YubiKey Detour and the Count That Lied
For years I kept my password vault in Bitwarden’s cloud on a Premium subscription. It worked, it was cheap, and the clients were lovely. Then Bitwarden’s licensing direction this year gave me the nudge, on top of a reason I’d already settled on: I wanted the vault on hardware I own, behind my own TLS and my own backups.
The clients stay exactly the same. Vaultwarden speaks the Bitwarden API, so the browser extensions, desktop app and phone apps just get a new server URL — the change is where the bytes live, not how I touch them.
What follows is the honest version: a migration designed so my master password never passed through the AI assistant I do my homelab work with, a YubiKey detour of my own making, and three item counts for one vault that disagreed until I learned which to trust.