Migrate from Crunchy Bridge to Layerbase
Move your Crunchy Bridge Postgres to a managed Layerbase database in one guided pass. Copy the connection URI for the postgres role and we copy the schema and data. Read-once, your cluster is never modified, and credentials are never stored.
Still comparing? Crunchy Bridge alternatives
Why switch
Why teams leave Crunchy Bridge
A free tier to land on
Crunchy Bridge has no free plan: the smallest Hobby cluster is a paid cluster, billed by the minute. A Layerbase Postgres is $0 on the Free tier, then $5/mo Solo or $15/mo Pro, so you can migrate a side project and evaluate it before you decide anything.
Branching, not another cluster
A preview environment on Bridge is a second cluster with a second bill. Layerbase Postgres branches copy-on-write in seconds, so a migration rehearsal, a CI run, or an agent gets its own copy of the data without provisioning anything.
The rest of your stack in the same account
Crunchy is Postgres and only Postgres. Layerbase Cloud runs 18 engines in one dashboard, so the Valkey cache and the search index your app also needs sit next to the Postgres instead of on two more vendors.
One connection string, one pass
Copy the postgres role URI from the Connection tab and paste it. We connect once over TLS, copy the schema and data, and disconnect. Nothing is written to your cluster and it keeps serving your app throughout.
How it works
Four steps, one pass
- 1
Create a free account or sign in
Sign in with Google or GitHub. No credit card is needed to start, and the migration wizard opens with this platform already selected.
- 2
Paste your connection string
Open your cluster in the Crunchy Bridge dashboard and go to the Connection tab, then copy the connection URI for the postgres role: postgres://postgres:password@p.abc123.db.postgresbridge.com:5432/postgres?sslmode=require. The application role works too, but it is not a superuser, so pick postgres if your schema has extensions or objects that role does not own. If you use the cb CLI, cb uri <cluster> prints the same string.
- 3
Pick what to migrate and name it
Choose what to bring over, give the new Layerbase database a name, and start the migration. Progress streams live in the dashboard.
- 4
We copy it in one pass
The migration reads from Crunchy Bridge once and never writes to it. Credentials are used for the copy and never stored. When it finishes, you land in your new database with a live TLS connection string.
FAQ
Common Crunchy Bridge migration questions
Crunchy Data was acquired by Snowflake. Is Crunchy Bridge going away?
Nothing like that has been announced, and we are not going to imply it. Here is what is on the record: Snowflake acquired Crunchy Data in June 2025, and Snowflake Postgres, built on Crunchy technology, reached general availability in February 2026. Crunchy Bridge is still sold, still onboarding, and still under its own name, with no sunset date and no migration deadline published. What did change is who owns the roadmap. If you would rather not find out later what a data-cloud roadmap means for a small managed cluster, moving now is a calm decision rather than an urgent one, and this page is here for that. If Bridge is working for you, staying is a perfectly good answer.
Where do I find my connection string?
Open the cluster in the Crunchy Bridge dashboard and go to the Connection tab, which lists a URI per role. Copy the one for the postgres role. The application role also works, but it is not a superuser, so the postgres role is the safer pick when your schema has extensions or objects application does not own. The cb CLI prints the same string with cb uri <cluster>.
Do I need the Crunchy CA certificate?
No. Crunchy Bridge requires TLS on every connection and we connect over TLS, so sslmode=require is all you need. The sslrootcert form in the Crunchy docs is for sslmode=verify-full, which pins the certificate they hand you. Leave sslmode at require and paste the URI as it is.
Will my cluster be modified?
No. We connect with the credentials in the URI you paste, read the schema and data once, and disconnect. Nothing is written back and your cluster keeps serving your app. This is a one-shot copy rather than replication: there is no live sync afterwards, so plan a cutover instead of expecting the two to stay in step.
Does my cluster firewall need changing?
Usually not. A new Crunchy Bridge cluster ships with firewall rules allowing 0.0.0.0/0 and ::/0, so it is already reachable. If you have replaced those with specific rules, add one that allows the copy while it runs, because we do not connect from a fixed address.
What am I giving up?
Crunchy is a Postgres specialist and it shows. Bridge offers larger single instances than our shared plans, high availability with a standby, per-minute scaling of compute and storage, Postgres major versions the day they land, and the Crunchy team behind support. If you are running a large production Postgres that needs those, staying is the right call. Layerbase is the better fit for a small to mid-sized database that wants flat pricing, branching, a free tier, and the rest of your data stack in one account.
Ready to leave Crunchy Bridge?
Sign in, and the migration wizard opens with Crunchy Bridge already selected. Your source is read once and never modified, so there is nothing to undo if you change your mind.