How to migrate from 1Password to Vaultwarden

Move 1Password to self-hosted Vaultwarden: shared vaults as collections, a safe 1PUX export, the Bitwarden importer and what you re-add by hand.

Start with one workloadThe steps

Written for
The engineer who will do the work
Or run by Pilae
At a fixed price, then operated

In short

  • Vaultwarden is an unofficial AGPL-3.0 server for the official Bitwarden apps, and those apps import the 1PUX file that 1Password exports in plain text.
  • 1Password exports a whole account and the importer does not keep vault names, so each shared vault goes through a temporary member that can export only that vault, then into its collection.
  • File attachments are uploaded again by hand, and passkeys, which the 1Password desktop export leaves out, are registered again with each site.
  • Every export file is imported, checked against the item count in 1Password and deleted on the day it is made.
On this page (11)

Moving from 1Password to Vaultwarden is an export and an import, done once for each shared vault and once for each person. Vaultwarden is an unofficial server that implements the Bitwarden API, so the import is done by the official Bitwarden apps, from a file that 1Password writes in plain text. Most items come across intact. What takes planning is the structure around them: which shared vault becomes which collection, how each file is kept to one vault, and what the importer leaves out.

Why teams move from 1Password to Vaultwarden

Three reasons come up again and again.

  • Where the vault is held. 1Password keeps vaults in its own cloud, in US, Canadian or EU regions. Vaultwarden runs on machines you choose and can answer only on your private network.
  • No per-seat bill. 1Password is priced per user per month. A Vaultwarden server costs the machine it runs on and its operation, whatever the number of people.
  • An open server and familiar apps. Vaultwarden is published under AGPL-3.0, and staff use the Bitwarden browser extensions and apps, which many already know.

What you give up is 1Password’s own apps, which are polished, and its Secret Key: 1Password encrypts with the account password and a Secret Key, while the Bitwarden apps derive the vault key from the master password, so a master password policy matters more. Vaultwarden is an independent project, not associated with Bitwarden, Inc., and it follows changes in the Bitwarden apps rather than shipping them, so each server release is tested against the current apps before it goes in. And someone has to run the server, which is the part Pilae takes on.

Step 1: inventory vaults, people and items

  1. List the shared vaults with their members, groups and permissions, and the number of items in each. That count is what each import is checked against.
  2. Name an owner for each shared vault. They decide what moves and sign off the result.
  3. Count what will not import. File attachments, Document items and passkeys are re-added by hand in step 6, so it helps to know how many there are and where.
  4. Retire what nobody uses. A shared vault nobody has opened in a year is a candidate to leave behind.
  5. Check export rights. On 1Password Business, exporting a vault’s items needs the Export items permission on that vault.

Step 2: design the organisation and collections

Set up the structure before anyone imports, so shared items land in the right place.

1Password Vaultwarden, through the Bitwarden apps
Team or business account Organisation
Each person’s private vault My vault, each person’s own
Shared vault Collection
Vault permissions Collection permissions: view, edit or manage
Group Group, a beta feature in Vaultwarden
Item sharing link Send, for text and files
  • Collections and permissions. Each shared vault becomes a collection. Bitwarden’s permission levels are view items, view items with passwords hidden, edit items, edit items with passwords hidden, and manage collection.
  • Groups, or people directly. Vaultwarden supports groups, but its configuration marks them as a beta feature with known issues and leaves them switched off by default. Decide whether to switch them on, or to give people access to collections directly.
  • Policies before anyone joins. Master password requirements, two-step login, account recovery by an administrator and emergency access are all available in Vaultwarden. Set them first, so they apply from each person’s first day.

Step 3: stand up Vaultwarden and enrol people

  1. Close open sign-up. Vaultwarden lets anyone register by default. Turn sign-ups off and keep invitations, which let organisation administrators invite people even then. Keep the admin page off the internet.
  2. Enrol devices first if the server answers only on a private network: each laptop and phone joins it before its owner is invited.
  3. Invite people to the organisation. The Bitwarden process is invite, accept, confirm: a person accepts the email invitation by creating an account with a master password, then an administrator confirms them before shared collections appear.
  4. Install the apps. The Bitwarden browser extension, desktop and mobile apps connect to your server: on the sign-in screen, choose Self-hosted under Logging in on (Accessing, in the desktop app) and enter the server URL.

Vaultwarden can also let people sign in through an OpenID Connect provider such as Keycloak. The master password is still required: the vault is decrypted with it, on the device.

Step 4: import shared vaults into collections

Two facts shape this step. 1Password’s desktop app exports a whole account: the file holds every vault the person exporting is allowed to export, their private vault included, and there is no option to pick one vault. And the Bitwarden importer does not keep the vault an item came from. Items land where you import them, and only an item’s first tag survives, as a folder, or in an organisation as a collection nested under the one you chose. So a shared vault reaches its own collection only if the file holds that vault alone.

The items themselves come across well. Logins keep their one-time password seeds, and secure notes, cards, identities and SSH keys map to their Bitwarden types. Other 1Password categories, such as bank accounts or passports, arrive as the nearest Bitwarden type, with the remaining fields kept as custom fields.

1Password documents no way to export a single vault, and the importer cannot pick one out of a file. The workaround below is built from two features 1Password does document, the account export and the Export items permission set per vault, so check its result each time:

  1. Add a temporary member to 1Password for the length of the move. Its own vault starts empty, so its export holds only the shared vaults it can export, including any it reaches through a group every member joins.
  2. Give it one shared vault, with the Export items permission (on 1Password Teams, Allow Editing, which includes it).
  3. Export as that member from the 1Password desktop app: File, then Export on a Mac, or the ellipsis at the top of the sidebar, then Export, on Windows and Linux. Choose the account, enter its password, choose 1PUX and select Export Data, as in 1Password’s export instructions. CSV is not enough: it carries only Login and Password items, without custom fields.
  4. Import into the collection from the Admin Console of the Vaultwarden web vault: Settings, then Import. Choose the collection, the 1Password (1pux) format and the file.
  5. Check the count against the vault’s item count from step 1, which also shows whether the file held that vault alone, then open a few items with one-time codes, custom fields and several websites. Importing does not check for duplicates, so if a count is wrong, delete the imported items before trying again.
  6. Delete the file, empty the trash, and take the vault away from the migration account before giving it the next one.

The export file is plaintext

1Password states it plainly: anyone with access to an exported file can read every password in it. Handle each file the same way, whoever makes it.

Every export file, from creation to deletion

  1. Export: On an encrypted, managed laptop, into a local folder no cloud service syncs.
  2. Import: In the same sitting, into Vaultwarden.
  3. Check: Item counts compared with 1Password.
  4. Delete: The file deleted and the trash emptied the same day.

Export on the person’s own laptop, with full-disk encryption, never on a shared or remote machine. Save to a local folder that no cloud service syncs or backs up: on many laptops the Desktop and Documents folders are synced, so check before choosing. Never email the file, put it in chat or store it online. Leave the 1PUX file as it is; it is a ZIP archive, and unpacking it only makes more plaintext copies. Import in the same sitting, check the counts, then delete the file and empty the trash, the same day.

Step 5: import personal vaults

Each person exports their own account the same way and imports it into My vault: in the web vault, Tools, then Import; in the browser extension, Settings, Vault options, Import items; in the desktop app, Import. The format is 1Password (1pux). An item’s first tag becomes a folder.

Their file also holds every shared vault they are allowed to export, and those items are already in collections. On 1Password Business, the same workaround runs in reverse: remove the Export items permission on shared vaults from members while they export, so their file carries their private vault only. Check the first pilot export before everyone else exports. Where your 1Password plan has no such permission, people delete the copies of shared items from My vault after importing.

The Bitwarden desktop app and browser extension also offer a direct importer that reads a 1Password account without writing a file. It currently accepts only sign-in with the 1Password account password. Test it against your own server on the pilot before offering it to everyone.

Step 6: re-add attachments and passkeys

  • File attachments and documents. The 1PUX file contains them, but the Bitwarden importer leaves them out, and Document items arrive without their file. Each file is uploaded again to its item in Vaultwarden, downloaded from 1Password while it is still open, with the download deleted afterwards.
  • Passkeys. The 1Password desktop apps do not export passkeys; 1Password exports them only from its iOS and Android apps, through the Credential Exchange standard, which the Bitwarden mobile apps can receive. Test that route on the pilot with your server. Otherwise each passkey is registered again with its site, from the Bitwarden app.

Step 7: run both, then close 1Password

  1. Set an end date for the parallel run. From the first day, new and changed passwords go into Vaultwarden only, or the two drift apart.
  2. One autofill. Remove the 1Password browser extension once the Bitwarden one is in, so two extensions do not offer to fill and save on every page.
  3. Sign off. Each vault owner confirms their collection, and each person confirms their own items.
  4. Close the account. Remove the migration account, and end the subscription once nobody opens 1Password any more.

Running Vaultwarden in production

Vaultwarden is light, but it is the service people cannot work without.

  • PostgreSQL. Vaultwarden also runs on SQLite or MySQL; PostgreSQL is backed up and restored like every other database.
  • The data directory. Attachments, Send files and the key that signs sessions live there, and are backed up with the database.
  • Mail and one hostname. An SMTP relay for invitations, email second factor, emergency access and new-device notices. The Bitwarden apps require HTTPS, and every device is configured with the hostname, so it is chosen once.
  • Upgrades against the current apps. Each Vaultwarden release is tested against the current browser extension and mobile apps before it goes in.

Pilae operates Vaultwarden this way, with open sign-up off and the admin page reachable only on your private network. Backups are daily, encrypted and stored at a second site in the same jurisdiction, and on Enterprise a restore test every month is recorded in the console. The vault items in them are ciphertext the server cannot read. The Pilae Agent plans each upgrade, waits for your approval and applies it in your window. For the wider comparison, see our page on 1Password alternatives.

Let Pilae run the move

Pilae runs 1Password to Vaultwarden migrations at a fixed price: the inventory and collection design, the server and its policies, the shared vault imports with their counts checked, a written procedure for each person’s own export, and the parallel run. Then we operate Vaultwarden for you under a contract that, from the Business plan, includes a monthly availability commitment with service credits. See migration services for what the fixed price covers, or tell us how many people and vaults you have.

Questions

Is Vaultwarden open source?

Yes. Vaultwarden is published under the AGPL-3.0 licence. It is an unofficial server that implements the Bitwarden API and is not associated with Bitwarden, Inc. Your people use the official Bitwarden browser extensions, desktop, mobile and command-line apps, pointed at your own server.

Does everything in 1Password come across?

Most of it. The Bitwarden importer reads 1Password's 1PUX export and brings logins with their one-time password seeds, secure notes, cards, identities, SSH keys and custom fields. File attachments and the files of Document items are not imported, passkeys are not in the desktop export at all, and the vault each item came from is not kept.

How do we keep the export file safe?

Treat it as every password in it, in plain text, because that is what it is. Export on the person's own encrypted laptop into a local folder that no cloud service syncs, import in the same sitting, then delete the file and empty the trash. Never email it, share it or store it online.

Can people sign in with Keycloak or Entra ID instead of a master password?

Alongside it, not instead of it. Vaultwarden supports sign-in through OpenID Connect, which covers Keycloak and Entra ID, and once sign-in with email and master password alone is switched off, your identity provider decides who can sign in. The master password is still what decrypts the vault on the device, because the encryption keys are derived from it.

How long does a 1Password to Vaultwarden migration take?

It depends on the number of shared vaults and on how many people move their own items, not on the number of items. The inventory settles the scope, and Pilae quotes the setup, the shared vault imports and the rollout at a fixed price once it is done.

Let us run the move for you

An inventory, a parallel run and a cutover plan, at a fixed price. Then we operate the app.

Start with one workload

  • Go deeperSaaS migrationA fixed-scope migration off Google Workspace, Microsoft 365, Zapier, Airtable and ChatGPT to open-source apps, with a parallel run and a cutover plan.
  • CheckManaged operationsPatching, daily encrypted backups, monitoring and incident response for your open-source apps, under an SLA with an availability commitment of up to 99.9%.