Home›Services›Vault to OpenBao

Move from Vault to OpenBao without breaking your apps

OpenBao is the open-source fork of HashiCorp Vault. It speaks the same API, so your applications keep working. We move your secrets, policies and login methods, re-point every client and test it — with a rollback ready at every step.

from $5,000 · fixed price Measured first, then fixed price and dates Same API for your applications
The problem

Vault moved to the Business Source License, and HashiCorp is now part of IBM.

What we do

Move secrets, policies and logins to OpenBao — in place or side by side — and re-point every client.

The result

Same API for your apps, an open-source licence, rollback ready at every step.

Is this you?

This service is for teams that run Vault today and want their secrets platform on an open-source licence.

Why teams are moving now

Two ways to migrate — we pick the safe one for you

OpenBao's own upgrade guide was tested on open-source Vault 1.14.1 with integrated (Raft) storage. Everything else needs the side-by-side route. We tell you which one applies in week one.

RouteWhen it fitsHow it works
In-place upgradeOpen-source Vault 1.14.x, integrated (Raft) storage, no external pluginsSnapshot first, then replace Vault with OpenBao node by node; the cluster keeps serving. Fastest route.
Side-by-sideVault Enterprise, Vault 1.15 or newer, Consul storage, external plugins, or a cluster you want to clean up anywayNew OpenBao cluster, configuration kept as code, secrets copied over the API, clients switched in batches. Both clusters run until the last client moves.

What we move

HashiCorp VaultBusiness Source License
OpenBaoopen source, OpenSSF project
Static secretsKV v1 / v2, with versions where needed
Copied and checked key by key
PoliciesACL policies, entity and group mappings
Moved as code, reviewed in a merge request
Login methodsKubernetes, OIDC, AppRole, LDAP, JWT for CI
Re-created and tested with a real login from each client type
Dynamic secretsDatabase and cloud credentials
Engines re-configured; credentials are issued fresh, not copied
CertificatesPKI engine, internal CA
CA moved or re-issued, depending on your trust chain
Encryption as a serviceTransit keys
In-place: kept as is. Side-by-side: keys restored from backup where the key allows it; otherwise a planned re-encryption of your data
AuditFile or socket audit devices
Re-enabled and connected to your log pipeline

What you get

A running OpenBao cluster your team understands, and a Vault you can switch off.

Inventory and route

Every secrets engine, login method, policy and client listed. Anything OpenBao handles differently is flagged before work starts.

OpenBao cluster

Highly available, with backups and a tested restore. Configuration kept in Git, so it can be rebuilt.

All clients switched

Applications, CI jobs and Kubernetes workloads read from OpenBao. Each batch is checked before the next one moves.

Unseal and recovery

Unseal method agreed and tested, recovery keys handed over to named people on your side.

Runbook

How to add a secret engine, rotate a key, restore from backup, upgrade OpenBao. Written for your engineers, not for us.

Handover session

One live session with your team, then Vault is decommissioned when you say so.

How it goes

The order is always the same. How long each step takes depends on your volume — the measurement in step 1 sets the price and the dates.

  1. Step 1 · 1–3 days

    Inventory and route

    We list mounts, login methods, policies and clients, check versions and plugins, and choose in-place or side-by-side. You get the plan and the final fixed price.

  2. Step 2

    Build and rehearse

    Backup taken and restore tested. OpenBao set up and rehearsed on a copy, so the real cut-over has no surprises.

  3. Step 3

    Move

    In-place: node by node. Side-by-side: secrets copied, clients switched in batches, lowest risk first. Rollback ready at every step.

  4. Step 4

    Handover

    Runbook, live session, recovery keys to your people. Vault is switched off once every client is confirmed on OpenBao.

What we need from you

  • Admin access to Vault in a non-production copy, and supervised access to production.
  • Servers or a Kubernetes cluster for OpenBao (or permission to create them).
  • An owner for each group of client services to approve their switch.
  • Agreed change windows and the people who will hold recovery keys.

Not included

  • Changing application code beyond configuration (address, login settings).
  • Buying or installing HSM hardware.
  • Rebuilding Vault Enterprise features that OpenBao does not have — if any apply to you, we say so in week one.
  • Cleaning up secrets nobody uses — we flag them and you decide.
from $5,000

Fixed price, agreed after the measurement in step 1. Paid by milestone: inventory, build, migration, handover.

What changes the price

  • Route — in-place is faster than side-by-side.
  • Number of secrets engines and login methods, and how many client services use them.
  • PKI and Transit — certificate chains and encryption keys need the most care.
  • Clusters and regions — one cluster or several, with or without disaster recovery.

Questions teams ask

Will our applications need code changes?

Usually not. OpenBao keeps the Vault API, so most clients only need a new address. Things that can break: tools that check the old token format, and plugins OpenBao does not ship. We find these in week one.

We run Vault Enterprise. Can we still move?

Yes, using the side-by-side route: a new OpenBao cluster, configuration and secrets copied over, clients switched one by one. OpenBao's in-place upgrade guide only covers the community edition, so we don't take shortcuts with Enterprise.

Is there downtime?

Not for your applications if we plan it well. In-place, nodes are upgraded one at a time while the cluster keeps serving. Side-by-side, both clusters run in parallel and clients move in batches.

Does OpenBao have namespaces?

Yes. Namespaces arrived in OpenBao 2.3 in 2025. If you use Vault Enterprise namespaces, we map them one to one in the migration plan.

What about auto-unseal and HSMs?

OpenBao supports auto-unseal. Which method fits you depends on your KMS or HSM; we confirm it in week one, before you pay for the migration itself.

Often done together

Tell us which Vault you run

Version, storage and how many services use it — that's enough for a price range on a 30-minute call.

Pick a 30-minute slot Opens our booking calendar in a new tab · or write to info@dvs.hk
Sources — public vendor announcements and documentation, for orientation only; not legal advice. Vault is a trademark of HashiCorp, an IBM company.
  1. HashiCorp: HashiCorp adopts Business Source License (Aug 10, 2023)
  2. IBM Newsroom: IBM completes acquisition of HashiCorp (Feb 27, 2025)
  3. OpenSSF: OpenBao joins the OpenSSF (Jun 17, 2025)
  4. OpenBao: 2.3 release notes
  5. OpenBao: Vault to OpenBao migration guide
Book a 30-minute call