Migrate from Turso to Layerbase
Move your Turso database to managed libSQL on Layerbase in one guided pass. Paste your database URL and an auth token, and we copy the schema and data with every SQLite type preserved. Read-once, your Turso database is never modified.
Why switch
Why teams leave Turso
No per-row read billing
A Layerbase libSQL database costs the same however many rows you read. Flat plans with a free tier, so a traffic spike is a good day, not a billing event.
Everything comes across intact
Schema and data copy with every SQLite type preserved, including triggers and generated columns. What you query on Turso is what you query on Layerbase.
Same protocol, same clients
Layerbase libSQL speaks the same protocol your app already uses. Swap the URL and auth token in your libSQL client and keep shipping.
A database with a dashboard
Web SQL console, daily backups, TLS by default, and database branching. Manage it next to your Postgres and Redis instead of in another tab.
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 your Turso database URL (libsql://... from `turso db show <db> --url`) and an auth token (`turso db tokens create <db>`). We read the database over HTTP and copy its schema and data into a new managed libSQL database, preserving every SQLite type. No per-row read limits, flat pricing.
- 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 Turso 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 Turso migration questions
How do I get my database URL and token?+
From the Turso CLI: `turso db show <db> --url` prints the libsql:// URL and `turso db tokens create <db>` mints an auth token. Paste both into the migration; the token is used once and never stored.
Will my Turso database be modified?+
No. We read the database over HTTP in a single pass, copy the schema and data, and disconnect. Your Turso database keeps serving traffic throughout.
Do triggers and generated columns survive?+
Yes. The migration recreates the schema faithfully, including triggers and generated columns, and preserves every SQLite type byte for byte.
Does my app code change?+
Only the connection details. Layerbase libSQL uses the same client libraries, so you swap the database URL and auth token and everything else stays as-is.
Ready to leave Turso?
Sign in, and the migration wizard opens with Turso already selected. Your source is read once and never modified, so there is nothing to undo if you change your mind.