Migrate from Aiven to Layerbase
Move your Aiven PostgreSQL or Valkey to a managed Layerbase database in one guided pass. Copy the Service URI out of the Aiven Console and we copy the schema and data. Read-once, your Aiven service is never modified, and credentials are never stored.
Still comparing? Aiven alternatives
Why switch
Why teams leave Aiven
One plan, not one bill per service
Aiven prices every service on its own hourly meter and charges for each one separately, so a Postgres, a Valkey, and a second Postgres are three line items that each start again from zero. Three of Aiven's smallest paid services is $15 a month across three meters. On Layerbase they are three databases inside one $5/mo Solo plan, sharing one pool and one bill.
A free tier that is a database, not one slot per product
Aiven gives you one free service per service type at 1 GB of RAM, and powers it off when it goes idle. The Layerbase Free tier is $0 with 2 databases and 5 GB of storage, and you pick the engines: Postgres today, Valkey tomorrow, without a second free-service slot to spend.
Built for the database, not the data platform
Aiven is a data platform where Kafka, Flink, and OpenSearch are the headline and a small Postgres is a side dish. Layerbase is 18 database engines in one dashboard with backups, branching, a web query console, and wake-on-connect on every one of them.
Your Service URI is the whole migration
Copy the Service URI from Connection information in the Aiven Console and paste it. We connect once over TLS, copy the schema and data, and disconnect. Nothing is written back to Aiven 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 Aiven for PostgreSQL service in the Aiven Console, then Overview, then Connection information, and copy the Service URI: postgres://avnadmin:password@pg-yourproject.a.aivencloud.com:12345/defaultdb?sslmode=require. Aiven assigns a random high port rather than 5432, so paste the whole string instead of rebuilding it by hand. defaultdb is the database Aiven creates for you; if your tables live in another one, change the name at the end of the path. If your plan runs a standby, the Replica URI on the same page works here too and keeps the read off your primary.
- 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 Aiven 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 Aiven migration questions
Where do I find my Aiven connection string?
In the Aiven Console, open the service and look at the Overview tab. Connection information holds the Service URI: a postgres:// string for Aiven for PostgreSQL and valkeys:// for Valkey. Copy the whole thing. Aiven assigns a random high port rather than the engine default, so rebuilding the string by hand is the usual way this goes wrong.
I have an Aiven for Redis service. Can I migrate that?
Almost certainly it is a Valkey service now. Aiven for Redis became Aiven for Caching in 2024, Caching services were automatically upgraded to Aiven for Valkey after 31 March 2025, and Caching was decommissioned from 15 October 2025. Copy the valkeys:// Service URI and migrate it into a Layerbase Valkey or Redis database: the two speak the same wire protocol, so it copies straight in either way.
Can I migrate my Aiven MySQL?
Not through the wizard yet. Aiven MySQL dumps need a specific mysqldump flag our importer does not pass yet, so the guided path would fail partway rather than cleanly. It is coming. Today the manual route works: mysqldump with --single-transaction --set-gtid-purged=OFF, then restore that file into your Layerbase MySQL database from its query console, which takes a SQL file.
Do I need the Aiven CA certificate?
No. Aiven requires TLS and we connect over TLS, so sslmode=require on the end of the Service URI is all you need. The certificate Aiven offers in the console is for sslmode=verify-ca or verify-full, which pin the private CA that project uses. Leave the parameter at require and paste the string as it is.
Does my Aiven service need to be reachable?
Yes, and by default it already is: Aiven leaves the IP filter on a new service at 0.0.0.0/0, so most services need no change. If you have narrowed the IP filter, widen it while the copy runs, because we do not connect from a fixed address. A service reachable only over VPC peering or PrivateLink cannot be dialed from outside Aiven at all. One more thing worth checking on a free service: Aiven powers idle free services off, and a powered-off service cannot be dialed, so start it before you begin.
Can I migrate my Aiven ClickHouse or Kafka?
Not through this wizard yet. Layerbase Cloud hosts ClickHouse, but the migration path into it is not built, so a ClickHouse move is still a manual export and import today. Kafka, Flink, and OpenSearch have no Layerbase equivalent: if those are the load-bearing part of your Aiven bill, staying is the right call.
What does it cost?
Postgres and Valkey are both on the Layerbase Free tier, so you can migrate and evaluate without a credit card. Paid plans are $5 a month on Solo and $15 a month on Pro, and every database in your account shares that one plan rather than billing separately.
Ready to leave Aiven?
Sign in, and the migration wizard opens with Aiven already selected. Your source is read once and never modified, so there is nothing to undo if you change your mind.