MySQL schema converter
CREATE TABLE statements and get the PostgreSQL, SQL Server, Oracle, SQLite or MariaDB DDL that a DBShifts migration creates — the same converter, with every type that changes on the way flagged.No sign-up. Your schema is converted in memory and not stored. Nothing is connected to or run.
From MySQL to
788 / 50,000
Questions
How do I convert a MySQL schema to PostgreSQL?
Paste your CREATE TABLE statements (mysqldump --no-data or SHOW CREATE TABLE gives you them), pick PostgreSQL and convert. AUTO_INCREMENT keys become SERIAL or BIGSERIAL, TINYINT(1) becomes BOOLEAN, DATETIME becomes TIMESTAMP, each ENUM becomes its own CREATE TYPE, unsigned integers are widened so no value overflows, and indexes and foreign keys follow as separate statements so the tables can be created in any order.
Is this the same conversion a DBShifts migration does?
Yes. The statements are read the way DBShifts reads a live MySQL database, and the DDL comes from the same converter a migration runs. We check that by loading test schemas into a real MySQL, reading them back, and requiring identical output for every target engine.
Why was a type or default refused?
The converter reads the MySQL types, defaults and keys it has been checked against. A spatial type, a generated column or an expression default it has not been checked against is refused with a message rather than guessed. A full migration reads those from your database directly.
What do the warnings mean?
Every column is matched against the target's type map. A wider type is safe (an unsigned INT needs a bigger signed integer). A change of meaning keeps the data but loses a rule, like an ENUM becoming free text where the target has no enum type. Data loss means the target type cannot hold every value the source can.
Is my schema stored?
No. It is converted in memory and returned; the request body is not logged or saved. Up to 50,000 characters and 50 tables at a time, 20 conversions a minute per network. Only CREATE TABLE and CREATE INDEX statements are read; nothing is ever run.
Move the data to PostgreSQL too
A migration creates this schema, copies every row, then checks each table arrived intact with row counts and checksums — with a dry run first and a rollback if you need one.
Other free tools
Text-to-SQL safety checker
Paste SQL an AI wrote: is it read-only, which tables does it touch, and what should worry you.
SQL query converter
A MySQL query rewritten for PostgreSQL, SQL Server, Oracle or SQLite, with what behaves differently.
Read-only database user generator
Exact commands for a read-only user on six engines, every variant tested on real servers.
Data receipt verifier
Paste an agent's result and check that DBShifts returned exactly that data, against a ledger that cannot be edited.