Move your database in three clicks.
Paste a connection string. We pg_dump, restore, verify with checksums, hand you a new URL.
Five steps. None of them yours.
We do the actual work. You paste a string, click a button, and swap an environment variable when we're done.
We connect read-only to your source PostgreSQL. Standard libpq URI works.
Using standard PostgreSQL tools internally (pg_dump). No proprietary protocols, no special agents.
Same indexes, foreign keys, sequences, common extensions. Your data lands ready to use.
Tables, row counts, indexes - checked end-to-end with checksums before we hand you the new URL.
Drop the new URL into your app's environment variable and redeploy. Your old database is still there if anything looks off.
If something doesn't look right, don't switch. Your old database is untouched. Free, no obligation.
Coming from a specific provider?
Each guide is written for the exact dashboard you're starting from, with screenshots and the connection-string menu path.
Flat monthly pricing, lighter dashboard, your own auth.
Flat monthly bill instead of a usage meter.
Cut your bill by more than half.
MySQL → PostgreSQL with honest disclosure.
Also supported
Any standard PostgreSQL provider with a connection string works. If it speaks libpq, we can migrate it.
The honest version
Your source database isn't touched, but your app needs an environment-variable swap and a restart. Aim for low-traffic time.
Under 5 GB: typically 2-5 minutes. 5-50 GB: 10-45 minutes. Over 50 GB: email us and we'll plan it together.
Common ones migrate cleanly. If you use something unusual (custom procedures, MySQL syntax), ask us first.
What separates a clean migration from a messy one
Verify before you trust the new database
We connect read-only and restore onto PostgreSQL 16 while your app keeps using the old database. Treat the copy as unverified until you point a staging app at it and click through your real flows. Only then does it earn production traffic.
Cutover is one variable; rollback is doing nothing
Going live is swapping DATABASE_URL and restarting, as long as a deploy. The old database stays live the whole time, so if anything looks wrong you point the variable back. We never delete or modify your source; you do, once it has run clean for a few days.
Size your pool before you flip
The most common post-migration surprise is connections, not data. Serverless functions and aggressive ORMs open more than you expect, and a new host enforces its limits. Decide your pool size and reuse one pool per process before cutover.
Flag exotic extensions and files early
Common extensions (uuid-ossp, pgcrypto, pg_trgm, citext, PostGIS, pgvector) migrate cleanly; tell us about anything exotic or a custom role hierarchy first. Uploads live in object storage, not the database, so plan the file move as a parallel track.
Migration FAQ
Will my app go down?
Only for the seconds it takes to update an environment variable and restart your app. Your source database is never touched - until you swap the URL, your old database is still serving traffic.
Do you charge for migration?
No. Migration is free. You start paying when you decide to use your new Swyftstack database.
What if it fails?
Nothing changes on your side. Source database untouched. Email us and we'll fix it - most migration issues are minor (an unusual extension, a missing role) and we resolve them in under an hour.
How big can my database be?
Under 5 GB: 2-5 minutes. 5-50 GB: 10-45 minutes. Over 50 GB: email us and we'll plan it together - we've done multi-hundred-GB migrations without downtime.
What about extensions?
Common ones (uuid-ossp, pgcrypto, pg_trgm, citext, PostGIS, pgvector) all migrate cleanly. Unusual extensions: ask us first.
Start a migration - free until you switch.
Paste a connection string. Watch the progress bar. Get a new URL. Walk away anytime, no charge.