Migrate from PlanetScale to Layerbase
PlanetScale runs MySQL and Postgres, and Layerbase hosts both. Paste a service token and we move a MySQL database to managed MySQL or MariaDB using a short-lived read-only password we mint and then delete. A PlanetScale Postgres database comes across with its connection string. Read-once either way, and nothing is written back.
Why switch
Why teams leave PlanetScale
Both engines, standard tools
PlanetScale runs MySQL and Postgres; Layerbase hosts both, with normal connection strings, TLS, daily backups, and a web SQL console on either side. mysqldump, psql, your ORM, and every client you already use work unchanged.
Flat plans from $5 a month
MySQL and MariaDB run on the $5/mo Solo plan and up, and Postgres has a real Free tier. One price for the database: no row-read counters or per-branch charges to model before you know your bill.
A safe, disposable credential
For the MySQL database you pick we mint a short-lived read-only password, copy from it, then delete it. Your real credentials never leave PlanetScale and nothing is written to the source.
Land on the engine you want
A PlanetScale MySQL database can land on Layerbase MySQL or MariaDB, which are wire-compatible. PlanetScale Postgres lands on Layerbase Postgres, branching included. Pick the target during the import.
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
Paste a PlanetScale service token and its ID (Settings, then Service tokens). We list your databases; for the one you pick we mint a short-lived read-only password, copy from it, then delete it. The token needs an org-level read-databases permission.
- 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 PlanetScale 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 PlanetScale migration questions
Will my PlanetScale database be modified?
No. For a MySQL database we mint a short-lived read-only password, copy the schema and data in one pass, then delete that credential. A Postgres source is read through the connection string you supply. Nothing is written to PlanetScale either way.
Can you migrate PlanetScale Postgres, not just MySQL?
Yes. PlanetScale Postgres is standard Postgres, so it comes across with a connection string: choose the Other Postgres source in the wizard and paste it. The service-token flow below is the guided path for PlanetScale MySQL databases.
What does the service token need?
An org-level read-databases permission (Settings, then Service tokens). We use the token once to list your databases and mint the temporary read-only password, and it is never stored.
Do I need to stop writes during the copy?
The copy is a single point-in-time pass, so writes that land after it starts are not included. For an exact cutover, pause writes briefly or re-run the migration into a fresh database at switch time.
Is there a free tier?
Postgres has a Free tier, so a PlanetScale Postgres database can land at no cost. MySQL and MariaDB start on the $5/mo Solo plan. Every plan includes the full dashboard, backups, and TLS.
Ready to leave PlanetScale?
Sign in, and the migration wizard opens with PlanetScale already selected. Your source is read once and never modified, so there is nothing to undo if you change your mind.