CSV to MySQL
MySQL diverges from Postgres in small but breaking ways: AUTO_INCREMENT instead of SERIAL, DATETIME instead of TIMESTAMP, and a native ENUM type that Postgres has to fake with a check constraint or a separate type.
SchemaSnap targets those differences directly. A low-cardinality text column (a handful of short repeated labels, like a status field) is emitted as a real MySQL ENUM(...) list instead of a plain VARCHAR, and every other type maps to the closest MySQL equivalent.
Example
Run on a small sample CSV at build time, so this is real output, not a mockup.
Table structure (Postgres baseline)
CREATE TABLE customers (
id SERIAL PRIMARY KEY,
name VARCHAR(32) NOT NULL,
email VARCHAR(32) NOT NULL,
plan VARCHAR(32) NOT NULL,
price NUMERIC(10,2) NOT NULL,
signup_date DATE NOT NULL
);
Generated SQL (MySQL)
CREATE TABLE customers (
id INT AUTO_INCREMENT PRIMARY KEY,
name ENUM('Ava Chen','Liam Diaz','Mia Chen','Noah Patel') NOT NULL,
email VARCHAR(32) NOT NULL,
plan ENUM('free','pro','trial') NOT NULL,
price DECIMAL(10,2) NOT NULL,
signup_date DATE NOT NULL
);
Try it
Drop a .csv file here, or click to choose one. Or just paste below.
Paste or drop a CSV, then hit Convert. Nothing you enter here leaves your browser.