1Password is hired to keep a company's logins and secrets in one encrypted place and share them with the right people. Moving that job is mostly a security exercise, not a software one. Below: the business prices as published, the one open-source option we verified, and a staged migration that keeps the old vault as a fallback.
Once a vault holds the company's logins, everyone's daily work runs through it. Browser extensions, shared vaults and recovery arrangements all depend on it, and nobody volunteers to be the person who moves it.
Seat counts also drift. People leave without being removed, contractors are added for a project, and a plan tier is bought for one feature. The line on the books is small compared with the risk, so it rarely gets reviewed.
Only alternatives we have checked. An open-source project is listed with the license its repository reports, on the date shown; one whose license could not be read as a single standard id is not offered as open source. Read the license guide before running any of them.
| Alternative | Kind | License | Read from |
|---|---|---|---|
| Vaultwarden | Open source | AGPL-3.0 | Vaultwarden repositoryChecked Oct 25, 2026 |
Each feature below is what the product's own page or README says, linked to where we read it on the date shown. Pros and cons are limited to what those pages state and to what the path itself changes. We do not rank products on quality.
| Plan | Price as published | Includes | Read from |
|---|---|---|---|
| Teams Starter Pack | $2.49 per user per month, billed yearly | Listed as sharing passwords and sensitive data, role-based permissions, developer tools and security alerts. 10-user minimum, up to 20 users. | 1Password business pricingChecked Oct 25, 2026 |
| Business | $8.99 per user per month, billed yearly | Everything in the Teams Starter Pack, plus integrations with identity providers such as Okta and Entra ID, and role-based vault sharing. 1-user minimum. | 1Password business pricingChecked Oct 25, 2026 |
List prices as printed on the vendor's page on the checked date, in US dollars per user per month, billed yearly, excluding tax. Prices may differ at checkout. Only business plans are shown; the page also lists personal plans and an Enterprise option whose details were not read.
A password vault is a security system, so "hard" or "moderate" is the honest rating for moving it, and we rate this one moderate. The savings can be real on a large seat count, but the risk is in the days when secrets exist in two places and in an export file. If the saving is small, leaving the vault where it is and trimming seats is often the better trade.
Vaultwarden, an open-source server, is the alternative we verified. Its repository lists the AGPL-3.0 license on the checked date. That license carries obligations you should read, and its network-use terms apply if you modify the software and let others use it over a network. Running it makes you the operator, responsible for updates, backups and who can reach the server. For a comparison with another hosted vault, see LastPass.
Samples are made up and are not 1Password's prices. Type in the figures from your own invoice or order form.
The honest yearly cost of running open-source software yourself, set against the bill it replaces, with the seat count where it stops paying.
Paid seats against seats in use: what the idle ones cost a year, and what you save by right-sizing at renewal.
Arithmetic only, not tax, accounting or legal advice. Check the figures against your own order form.
Go in stages and keep the old vault alive throughout. Nothing is deleted until the new one has carried real work for a month.
List seats, shared vaults and owners. Count the entries in each vault so you can compare after the import, and mark which credentials many people share.
Name one administrator and one backup for the replacement. If nobody can take that on, choose a hosted product instead of running a server.
Set up the replacement with two or three people and import a small test set. Check sign-in, autofill, sharing and account recovery the way people actually use them.
Export from a trusted machine, never over email or chat. Import to the new vault, compare entry counts per vault, and delete the export and every copy as soon as the import is checked.
Rotate credentials that were widely shared or that former staff may have seen: banking portals, registrars, cloud consoles, admin accounts. Do the most sensitive ones first.
Move teams in groups. Set the old vault to read-only so nothing new is saved there, and ask each team to confirm they can reach what they need.
After a full month of normal use, keep a final export only if you need a record and store it under the same rules. Then end the plan inside the contract's notice window.
Run the vendor report for QuickBooks Online or Xero, then open the free audit.
General information, not legal advice. See cancelling without penalties. Last reviewed Oct 25, 2026. Product names belong to their owners and are used only to identify them.
Send us the export and see which lines are worth a second look. A connected version is planned. 1Password is one of the lines worth a look.
Worked example. Type over it.
Result
| Self-hosting, per year | Amount |
|---|---|
| Hosting, backups, tooling | 720.00 |
| Admin and restore-test time | 2,640.00 |
| Total | 3,360.00 |
| One-off set-up (not in the yearly total) | 1,200.00 |
The saving holds only if the time is real. Price the admin hours at what that person's time costs the company, not at zero.
Worked example. Type over it.
Result
“In use” is your call: last sign-in in the past 30 or 90 days from the vendor's admin report. A seat for someone on leave is not idle.