Migrate from PlanetScale to Layerbase
Move your PlanetScale database to managed MySQL or MariaDB on Layerbase in one guided pass. Paste a service token, pick a database, and we copy the schema and data with a short-lived read-only password we mint and then delete.
Why switch
Why teams leave PlanetScale
Standard MySQL, standard tools
A plain MySQL or MariaDB with normal connection strings, TLS, daily backups, and a web SQL console. mysqldump, your ORM, and every client you already use work unchanged.
Flat plans from $5 a month
MySQL runs on the $5/mo Solo plan and up. 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 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.
MariaDB if you want it
The same migration can land on MariaDB, which is wire-compatible with MySQL. Pick whichever target fits your stack 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.
Questions
Common PlanetScale migration questions
Will my PlanetScale database be modified?+
No. We mint a short-lived read-only password, copy the schema and data in one pass, then delete that credential. Nothing is written to your PlanetScale database.
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 MySQL tier?+
MySQL starts on the $5/mo Solo plan. If you want to evaluate first, the migration also targets MariaDB, and every plan starts with a full-featured dashboard, backups, and TLS included.
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.