Moving in from self-hosted Vaultwarden

Uploading an existing data directory is not built yet. For now, moving in means each person exports their vault from your server and imports it into the new one. Your own server keeps working in the meantime, so you can also wait.

What moves and what does not

Export and import carry each person's items and folders, and an organisation's items and collections through the organisation's own export.

Accounts, master passwords, two-step login settings and organisation membership have to be set up again, as does the server address in every client. Attachments and Sends move only if the export format includes them.

Steps

Create your Libreyard instance and your own account on it. See getting started.
Invite the others. See inviting family members. Each creates an account on the new instance. They may reuse their old master password.
Each person exports their vault from the old server, as JSON, from the web vault or an app. Vaults are encrypted per person, so nobody can do this for someone else.
Each person imports into the new instance: point a client at the new address, log in, import the file with the format "Bitwarden (json)". See importing.
Recreate organisations on the new instance, invite the members, and import each organisation's export into it.
Check, then delete the export files. They are not encrypted unless you chose an encrypted format.
Keep the old server until everyone has confirmed their vault is complete. Then stop it, and keep its data directory for a while longer.

The address changes

Custom domains are planned and not available at sign-up. Your vault's address becomes https://NAME.libreyard.app, so every client has to be logged out and pointed at it. When custom domains arrive, moving in and moving out again become a DNS change.

Moving back out

The other direction needs no export or import. You download the data directory and start it. See leaving.

Next: Inviting family members