migration planner

kp2bw

details
KeePass 11 items · 4 attachments · 1 passkey
Folder Collection Recycle Bin
Bitwarden 9 items · 4 attachments · 1 passkey

Tree in KeePass

  • KeePass database 11
    • Archive 1
      • 2021 1
        • Archive Box
    • Internet 2
      • Banking 2
        • Payroll KP changed
        • Stripe
    • Vault root 1
      • Root Admin new in KP
    • Work 5
      • Engineering 1
        • GitHub both changed
      • Servers 2
        • Production SSH BW changed
        • Router
      • Shared 2
        • Deprecated VPN BW changed
        • Shared VPN KP changed
    • Recycle Bin 2
      • Old 2
        • Old SaaS new in KP
        • Retired Jira KP changed

Tree in Bitwarden

  • My vault 9
    • Folders 9
      • Archive 1
        • 2021 1
          • Archive Box same
      • Internet 2
        • Banking 2
          • Payroll KP changed sync to BW
          • Stripe same
      • Unfiled 1
        • Root Admin new in KP create
      • Work 4
        • Engineering 1
          • GitHub both changed protect BW
        • Servers 2
          • Production SSH BW changed protect BW
          • Router same
        • Shared 1
          • Retired Jira KP changed skip
          • Shared VPN KP changed sync to BW
      • Recycle Bin 1
        • Old 1
          • Deprecated VPN BW changed protect BW
          • Old SaaS new in KP skip
  • Organization vault 0
    • No organization changes
Filters
Running again Pick the situation you are in when this command hits an existing Bitwarden vault. continue reading
Target Choose whether items land in an organization or your personal vault. continue reading
Tree mapping Controls how KeePass groups become Bitwarden placement. continue reading

Command

.env

KP2BW_KEEPASS_PASSWORD=<keepass password>
KP2BW_BITWARDEN_PASSWORD=<bitwarden password>

Run

kp2bw vault.kdbx