How to migrate from 1Password Business to Passbolt

Move 1Password Business to self-hosted Passbolt: inventory the vaults, rebuild them as shared folders, onboard every person, import the CSV, re-enter the rest.

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

  • Passbolt imports the CSV the 1Password desktop app exports: title, username, website, password and notes come across, while one-time password seeds and custom fields do not.
  • The 1Password CSV has no vault column, so each shared vault is rebuilt as a Passbolt folder shared with a group, and its items are moved into that folder after the import.
  • Every person installs the extension, creates their key and keeps a recovery kit before anything is shared with them; on Pro, account recovery is switched on before the first invitation.
  • The export is plaintext, so it is made on a managed laptop, imported in the same sitting, checked against the vault item count and deleted the same day.
On this page (14)

Moving from 1Password Business to Passbolt is a short import inside a longer rebuild. Passbolt reads the CSV that the 1Password desktop app exports and brings across each login’s title, username, website, password and notes. The structure does not come with it: the file has no column for the vault an item came from, so shared vaults are rebuilt as folders shared with groups. What the CSV leaves out is re-entered from a list. And every person sets up the Passbolt browser extension and their own key before anything can be shared with them, which is where most of the time goes. This guide covers the order we run it in.

Why teams move from 1Password Business to Passbolt

Three reasons come up again and again.

  • Sharing you can account for. Passbolt encrypts every secret separately, in the browser, for each person allowed to read it, and folders, groups and per-item rights decide who that is. On Pro, every read and permission change shows in the item’s activity.
  • Where the vault is held. 1Password keeps vaults in its own cloud. Passbolt runs on machines you choose and can answer only on your private network.
  • Open code. Passbolt is published under AGPL-3.0-or-later, and the Community Edition is free with no user limit.

What you give up is 1Password’s own apps and the breadth of its item types: Passbolt’s content types are passwords, one-time codes, notes, custom fields and PIN codes, and files are not one of them. Single sign-on, directory sync, account recovery and the policies are Pro features. And someone has to run the server, which is the part Pilae takes on. If what your people mostly need is a personal password manager each, the other route is Vaultwarden, covered in our guide to moving from 1Password to Vaultwarden. For the wider comparison, see 1Password alternatives.

Step 1: inventory each vault

The CSV decides what is quick and what is manual, so count before anyone exports.

  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. Count by category in each vault. Login and Password items travel in the CSV. Secure notes, credit cards, identities, documents and the other categories do not, and neither do custom fields such as security questions, file attachments or passkeys, even on a Login item. One-time password seeds are in the file, but Passbolt’s importer skips them. Write down how many of each there are, and where: that list is the work in step 6.
  3. Name an owner for each shared vault. They decide what moves, manage the group that replaces the vault’s members, and sign off the result.
  4. Retire what nobody uses. A 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.
  6. Decide about private vaults. Passbolt is built around what a team shares. Agree whether people move their private items into their own unshared Passbolt items, or keep personal passwords elsewhere.

Step 2: map vaults to folders and groups

Design the structure before anyone imports, so items land where they belong.

1Password Business Passbolt Note
Private vault A person’s own items, shared with nobody
Shared vault Folder shared with a group
Vault members or a group Group, with at least one group manager Created by an administrator
View Items can read
Create, Edit, Archive and Delete Items can update Includes deleting
Manage Vault is owner In Passbolt, owners can also read
Login and Password items Password Imported from the CSV
One-time password TOTP secret on the item Re-entered
Secure note Note Re-entered
Card, identity, other categories Custom fields, or a note Re-entered
Document or file attachment No equivalent Kept elsewhere
Tags Tags Not imported; tags are a Pro feature

Folders take their permissions at three moments. Every item and every folder keeps its own list of permissions. Passbolt’s sharing guide explains that a shared folder’s permissions reach an item when the folder’s permissions change, when the item is created in it, and when the item is moved into it. So each folder is shared with its group first, then filled: items moved in take the folder’s permissions, and Passbolt shows who gains access before it applies anything.

Groups belong to their managers. Only an administrator creates a group, and every group has at least one group manager. Adding someone to a group means encrypting each of the group’s secrets for that person’s key, in the browser of someone who can read them, so only a group manager can add members; an administrator who is not one cannot. Make each vault owner the manager of its group. A person’s key is created during their setup, so folders are filled once the people in their groups have finished step 4.

With a directory, on Pro. The LDAP connector synchronises users and groups from Active Directory or OpenLDAP. It never adds anyone to a group that already shares passwords: it notifies the group managers instead, because only their browser can encrypt for the newcomer. Let the first synchronisation fill the groups before any folder is shared with them. SCIM, also on Pro, provisions users only, not groups.

Step 3: set up recovery and policies, then invite

Whatever applies from a person’s first sign-in has to be in place before the first invitation.

  1. Prove the mail relay. Invitations arrive by email, and nobody can set up an account without one.
  2. On Pro, switch on account recovery. Under Organisation settings, Account recovery, choose a policy. With Prompt, new users must accept when they register, so every key is covered from the start; Opt-out and Opt-in leave the choice to each person. Then set the organisation recovery key. Passbolt’s account recovery guide gives its most secure option as creating it offline, keeping it offline, for example in a safe, and rotating it after each use. Each recovery request is approved with that key and its passphrase, by an administrator or by someone whose role allows reviewing recovery requests.
  3. On Pro, set the policies: the minimum strength of each person’s passphrase, the generator settings for new passwords, and the second factors people must use.
  4. On Pro, connect single sign-on if you want it. Passbolt works with Keycloak, Microsoft Entra ID, Google, AD FS and other OpenID Connect providers, matches people by email address, and lets signing in through the provider replace the passphrase.
  5. On the Community Edition, there is no account recovery. Each person’s recovery kit and passphrase are the only way back to their key, and the invitation tells people so.

Step 4: onboard every person

People set up their own key; nobody can do it for them. Start with a pilot group, usually IT, then go vault by vault.

Each person’s setup, before anything is shared with them

  1. Invitation: An administrator creates the account, or the directory does on Pro, and Passbolt emails a link.
  2. Extension: The link installs the Passbolt browser extension, which holds the key and does the encryption.
  3. Passphrase: The person chooses the passphrase that protects their private key.
  4. Recovery kit: They download the kit, their private key encrypted with that passphrase, and keep it safe.
  5. Security token: A colour and three letters that mark genuine Passbolt dialogs.

On Pro, the setup also asks each person to enrol in account recovery, as the policy requires. Phones come afterwards: the iOS and Android apps connect to an account already set up in a browser, by scanning a QR code from the mobile section of the person’s profile.

  • Follow up on pending accounts. The users workspace shows Activation pending for anyone who has not finished, and Resend invite sends a new link when the first one has expired.
  • Make the recovery kit stick. A new laptop or browser is set up from the kit and the passphrase. A person who skipped the download can still get the kit from their profile, under Keys inspector, while their current browser works.
  • Create the groups with their members and managers once the people in them are active.

Step 5: export, import and file each vault

The export

1Password’s desktop app exports a whole account, not one vault. On a Mac, choose File, then Export; on Windows and Linux, the ellipsis at the top of the sidebar, then Export. Choose the account, enter its password (or sign in through your identity provider, if 1Password is unlocked that way), choose CSV and select Export Data, as in 1Password’s export instructions. The CSV holds Login and Password items only, with their title, website, username, password, one-time password, favourite and archived status, tags and notes. It has no column for the vault and no custom fields.

Because the file holds every vault the exporter may export, their private vault included, keep vaults apart one of two ways:

  • One vault at a time, through a temporary 1Password member given a single shared vault with Export Items. Its own private vault starts empty, so its export holds that vault, plus any it reaches through a group every member joins. This is the route our Vaultwarden guide describes; check each file’s count before importing it.
  • One export of everything, sorted into folders afterwards against the step 1 list. Workable for a few small vaults.

The import

In Passbolt, choose Import next to Create, select the CSV, and keep Import folders ticked: Passbolt then puts the file’s items in a new folder named after the import, import- and a timestamp, and names it in the summary. On Pro, Add a unique import tag marks each item as well. The report counts items imported, partially imported and not imported.

The importer maps each row’s title, username, website, password and notes. It ignores the one-time password, favourite, archived and tag columns, so any archived item in the file arrives as an ordinary one. Notes become the item’s note, a secret encrypted alongside the password.

  1. Create the vault’s folder and share it with its group, at the level the mapping set.
  2. Move the imported items into it by dragging them onto the folder. The Confirm permissions dialog lists everyone who will gain access: read it before saving. Each person who gains access means one encryption per secret, done in the browser of the person moving the items, so a large vault shared with a large group takes a while.
  3. Check the count against the vault’s Login and Password items from step 1. go-passbolt-cli, Passbolt’s command-line tool, lists a folder’s items without opening them: passbolt list resource --folder <folder-id> -c id.
  4. Open a sample: usernames, websites and notes in place.
  5. Delete the file, empty the trash, and take the vault away from the migration member before giving it the next one.

The export file is plaintext

1Password states it plainly: exported files are not encrypted, and anyone with access to one can read every password in it. Export on a managed laptop with full-disk encryption, into a local folder no cloud service syncs. Never email the file, put it in chat or store it online. Import in the same sitting, check the count, then delete the file and empty the trash the same day.

A route that keeps vaults and one-time codes

Passbolt also imports KeePass databases, and for a KDBX file written by KeePassXC its importer maps groups to folders, one-time codes and custom fields. KeePassXC, an open-source password manager, imports 1Password’s 1PUX export, which carries the fields the CSV leaves out, and creates one group for each vault. So 1PUX into KeePassXC, saved as a KDBX database and imported into Passbolt, keeps more than the CSV does. It adds a tool and a second file to the handling, both on the same laptop, so try it on a pilot vault and compare the result before relying on it.

Step 6: re-enter what the CSV leaves out

Work through the step 1 list vault by vault, while 1Password is still open. Notes and custom fields need encrypted metadata, which new Passbolt instances use by default.

  • One-time codes. Edit the item, choose Add secret, then TOTP, and paste the key or upload a screenshot of the QR code. The preview shows the current code: compare it with 1Password’s before saving.
  • Secure notes become Notes, a content type of their own.
  • Cards, identities, bank accounts and SSH keys become custom fields, label and value pairs, or a note.
  • Custom fields on logins, such as security questions and backup codes, become custom fields on the same item.
  • Documents and file attachments. Passbolt stores no files, so each one needs a home, chosen with its owner, before 1Password closes.
  • Passkeys. 1Password’s desktop apps do not export them; its iOS and Android apps export through the Credential Exchange standard to apps that support it. Otherwise each passkey is created again on its website and kept where you decide.

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 Passbolt only, or the two drift apart.
  2. One autofill. Remove the 1Password browser extension once the Passbolt one is in, so two extensions do not offer to fill every form.
  3. Sign off. Each vault owner checks their folder against the inventory, re-entered items included.
  4. Rotate what narrowed. Where Passbolt gives fewer people access than 1Password did, change those credentials: losing access does not undo what someone has already read.
  5. Close. Remove the migration member, delete any export left behind, and let the subscription lapse at renewal once nobody opens 1Password.

Running Passbolt in production

Passbolt is small, but a restore needs more than its database.

  • MariaDB, the upstream default. PostgreSQL is supported only on a fresh install, so the choice is made once.
  • The server key pair. It proves the server to every browser extension and encrypts the mail, sign-on and directory settings stored in the database, so it is backed up with the data, with the JWT keys the mobile apps sign in with.
  • Mail and time. An SMTP relay for invitations, recovery and share notices, and an NTP-synced clock, because OpenPGP sign-in and one-time codes fail when the server clock drifts.
  • HTTPS, which the mobile apps, single sign-on and SCIM require.

Pilae operates Passbolt this way, on a machine of its own, on your premises or in Pilae Cloud, answering only on your private network, with phones reaching it through one hardened gate. The database, the server key pair, the JWT keys and the compose file go offsite daily, encrypted, in the country your contract names, and on Enterprise a restore test every month, recorded in the console, decrypts a test secret. The Pilae Agent tests each upgrade on a copy, waits for your approval and applies it in your window, with the previous version ready.

Let Pilae run the move

Pilae runs 1Password Business to Passbolt migrations at a fixed price: the inventory of each vault, the folder and group design, the server with its recovery and policies, the onboarding of every person, the imports with their counts checked, the re-entry list and the parallel run. Where your requirements need Pro, the subscription is held in your name. Then we operate Passbolt 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

Can Passbolt import a 1Password export?

Yes, the CSV. Passbolt's importer recognises the CSV that the 1Password desktop app exports and brings across each item's title, username, website, password and notes. That CSV holds Login and Password items only and leaves out custom fields, and the importer does not read its one-time password column, so secure notes, cards, one-time codes, documents and passkeys are listed per vault and re-entered by hand.

Do our 1Password vaults and permissions come across?

No. The CSV has no column for the vault an item came from, and carries no permissions. Each shared vault is rebuilt in Passbolt as a folder shared with a group, at can read, can update or is owner, and its items are moved into that folder after the import.

Do we need Passbolt Pro?

Not to share passwords: folders, groups, sharing, one-time codes and the mobile apps are in the free Community Edition. Single sign-on, LDAP and SCIM provisioning, account recovery, the activity log, tags, and password, passphrase and MFA policies need a Pro subscription, held in your name. Without account recovery, a person who loses both their recovery kit and their passphrase loses the items only they could read.

Is Passbolt open source?

Yes. The whole codebase, Pro features included, is published under AGPL-3.0-or-later by Passbolt SA, and the Community Edition is free with no user limit. Pro features switch on with a paid subscription key. The Passbolt name is a registered trademark and is not licensed with the code.

How long does a 1Password to Passbolt migration take?

It depends on the number of shared vaults, the number of items the CSV leaves out and how quickly every person completes their setup, not on the number of passwords. The inventory settles the scope, and Pilae quotes the setup, the imports and the onboarding 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%.