Migrate from Neon to Layerbase
Move your Neon Postgres to a managed Layerbase database in one guided pass. Paste a Neon API key, pick a project, and we copy the schema and data. Read-once, your Neon project is never modified, and credentials are never stored.
Using Neon Auth? Passwords and sessions live in Stack Auth, not in your database, so they do not migrate. Your users keep their profiles and set a new password on first sign-in. Regular Postgres tables migrate normally.
Why switch
Why teams leave Neon
Flat, predictable pricing
A real Postgres on the Free tier, then $5/mo Solo or $15/mo Pro. No compute-hour metering, no storage line items, no bill that changes shape when traffic does.
Keep your branching workflow
Layerbase Postgres supports database branching too. Migrate the main branch, then branch it for previews and experiments the way you already work.
A guided, read-once migration
Paste a Neon API key and we list your projects. Pick one and we copy the schema and data in a single pass. If you only have a pooled connection string, paste it anyway: we switch to the direct endpoint automatically.
Plain Postgres, no lock-in
Standard connection strings, pooled and direct, TLS by default, daily backups, and a web SQL console. Your drivers, ORMs, and tooling work unchanged.
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
Connect your account
In the Neon console, copy the connection string from your project dashboard. If you only see a pooled string, paste it anyway: we switch to the direct endpoint automatically.
- 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 Neon 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.
Questions
Common Neon migration questions
Will my Neon project be modified?+
No. The migration is read-once: we connect, copy the schema and data, and disconnect. Nothing is written to your Neon project and it keeps running throughout.
Does Neon Auth come across?+
Partially, and we are upfront about it: Neon Auth stores passwords and sessions in Stack Auth, not in your database, so they cannot migrate. Your users keep their profiles and set a new password on first sign-in. Regular Postgres tables migrate normally.
I only have a pooled connection string. Does that work?+
Yes. Paste it and we switch to the direct endpoint automatically before copying, so the migration does not run through the pooler.
What does it cost?+
Postgres is on the Layerbase Free tier, so you can migrate and evaluate without a credit card. Paid plans start at $5 a month when you need more databases or resources.
Ready to leave Neon?
Sign in, and the migration wizard opens with Neon already selected. Your source is read once and never modified, so there is nothing to undo if you change your mind.