Neon to MySQL converter

Neon runs PostgreSQL — export it, convert it, run it on MySQL. Two ways to migrate.

Upload a dump file

Free

Export your Neon database with pg_dump, upload the file, and get MySQL 8-ready SQL — uuid, jsonb, arrays and time zones mapped properly, output verified on a real MySQL server.

// converter

Drop your mysqldump file here or browse .sql or .sql.gz — up to 10 MB free

uploads deleted on completion real engine, not regex free account, e-mail only

Live Neon-to-MySQL

Free up to 5 MB

No dump file needed. Paste your Neon connection string and your MySQL connection details — SwapSQL reads from one and writes to the other.

✓ Paste your Neon connection string directly
✓ Test both connections before starting
✓ Tables, data, indexes and keys transferred directly
✓ Full report when the migration completes
✓ Works with any Neon branch — just use the right connection string

Open live migration

Compare plans — or start free, upgrade when you need it.

Step 1 — Export your Neon database

Find your connection string in the Neon console under your project's Connection Details panel. Select the branch you want to export.

pg_dump "postgresql://[user]:[password]@[endpoint-id].us-east-2.aws.neon.tech/[dbname]?sslmode=require" > dump.sql

# compress for faster upload:
gzip dump.sql

Step 2 — Convert it

Upload dump.sql (or .sql.gz) above. The dump is restored into an isolated PostgreSQL sandbox, the schema is read directly from the live catalog, translated to MySQL DDL, and the data is exported as efficient batched INSERTs.

Step 3 — Import into MySQL

mysql -u USER -p -e "CREATE DATABASE mydb CHARACTER SET utf8mb4"
mysql -u USER -p mydb < dump.mysql.sql

Careful type mapping

uuid → CHAR(36), gen_random_uuid() defaults → (uuid())
jsonb / json → MySQL JSON
Arrays → JSON arrays (queryable with JSON_EXTRACT, JSON_LENGTH)
timestamptz → UTC DATETIME(6) with microseconds
Enum types → native MySQL ENUM with the same labels
Identity / serial → AUTO_INCREMENT continuing from the right value

The full mapping table documents every type, including the lossy ones (interval, tsvector, ranges) — those are stored as text and flagged in your conversion report, never silently mangled.

// faq

Frequently asked questions

Can I convert a Neon database to MySQL?

Yes. Neon runs standard PostgreSQL, so any tool that converts PostgreSQL to MySQL works. Export your Neon database with pg_dump, upload it above, and download MySQL-ready SQL.

How do I export my Neon database?

Copy your connection string from the Neon console, then run pg_dump "postgresql://[user]:[password]@[host]/[database]?sslmode=require" > dump.sql.

What happens to Neon-specific features like branching?

Neon branches are a platform feature, not a database-level concept. When you export with pg_dump, you export the data from whichever branch your connection string points to. The conversion handles the data itself — tables, columns, indexes, constraints.

Are uuid columns preserved?

Yes — uuid columns become CHAR(36) in MySQL, and gen_random_uuid() defaults are mapped to MySQL's (uuid()) function. All existing uuid values transfer as-is.

What about jsonb columns?

PostgreSQL jsonb maps to MySQL JSON. Your data stays queryable using MySQL's JSON functions (JSON_EXTRACT, JSON_VALUE, etc.).

Can I migrate without a dump file?

Yes — live migration is included on the free plan for source databases up to 5 MB (two per day). Paste your Neon connection string as the source and your MySQL server as the target, and SwapSQL transfers everything directly. The Pro plan removes the size and daily limits.

Chat with us