SwapSQL

// live migration

Server-to-server migration, no dump files

Connect your source and target databases, press start. SwapSQL reads one engine, writes the other, and hands you a full report when it's done.

Open live migration free ≤ 5 MB · 2/day

e-mail sign-in · credentials never stored · ssl enforced

01

Connect

Enter host, port, database and user — or paste a full postgresql://… connection string and the fields fill themselves.

02

Test

One click verifies both connections and shows the server version and table count before anything runs.

03

Migrate

Tables, data, indexes and keys are transferred engine-to-engine, with a report of table and row counts at the end.

// endpoints

Works with the servers you already run

MySQL sources & targets

  • mysql 5.7+ / 8.x — self-hosted
  • amazon rds / aurora mysql
  • google cloud sql · azure database
  • digitalocean / any reachable host

PostgreSQL sources & targets

  • postgresql 12 – 18 — self-hosted
  • supabase (session pooler) · neon
  • amazon rds / aurora postgres
  • google cloud sql · azure database

All four directions

Cross-engine — MySQL → PostgreSQL and PostgreSQL → MySQL — plus same-engine copies (MySQL → MySQL, PostgreSQL → PostgreSQL) for moving between servers or providers. Connections you've tested are remembered in your browser only; nothing is stored on our servers.

// faq

Frequently asked questions

How does live migration work?

You enter connection details for a source and a target database (or paste a connection string — it is split into fields automatically). SwapSQL connects to both over SSL, reads the source engine-to-engine, writes into the target, and gives you a full report. Nothing is stored on our side; credentials travel only through the job and are never written to disk.

Which databases can I connect?

Any reachable MySQL 5.7+/8.x or PostgreSQL 12–18 server: self-hosted, RDS, Cloud SQL, Azure, DigitalOcean, Supabase (use the Session pooler connection string) and Neon included. SSL is required automatically for hosts on the public internet.

Which directions are supported?

All four: MySQL → PostgreSQL, PostgreSQL → MySQL, and same-engine copies (MySQL → MySQL, PostgreSQL → PostgreSQL) for moving between servers or providers.

Is it free?

Yes — live migration is included on the free plan for source databases up to 5 MB, twice a day. The Pro plan ($9/month) removes the size and daily limits.

Will it overwrite my target database?

Tables in the target with the same names are replaced — the interface warns you before starting. Use an empty target database unless you know what you're doing.