Convert mysqldump to DuckDB
Upload a .sql file and get back a DuckDB file. Types are preserved rather than flattened to text. Free, no registration, up to 10MB.
Click to upload or drag and drop
CSV, Excel, SQLite, SQL, DBF (max 10 MB)
How your data is typed in DuckDB
Generated from the converter's own DuckDB type mapping — this is what it actually emits, not an example.
| Your data | DuckDB type |
|---|---|
| Whole number | BIGINT |
| Decimal (money) | DECIMAL(10,2) |
| Floating point | DOUBLE |
| True / false | BOOLEAN |
| Date | DATE |
| Date and time | TIMESTAMP |
| Short text | VARCHAR |
| Long text | VARCHAR |
| Binary data | BLOB |
Working from a mysqldump file
mysqldump writes a plain-text .sql file with a very consistent shape, which makes it one of the easiest dumps to read: its own syntax announces the dialect, and its rows are inline rather than in a separate archive.
- →Every mysqldump file contains ENGINE=InnoDB or AUTO_INCREMENT, which is exactly what the dialect detection looks for, so backtick-quoted identifiers and MySQL types parse without you choosing anything.
- →mysqldump packs many rows into one extended INSERT by default, and each tuple in it becomes a row, so there is no need to dump again with --skip-extended-insert.
- →The file is decoded as UTF-8 with unreadable bytes replaced, so a legacy latin1 dump arrives with damaged accented text. Dump with --default-character-set=utf8mb4, or run the file through iconv first.
- →mysqldump --tab is not a dump at all: the schema goes to a .sql file and the rows to headerless tab-separated .txt files. Neither half is convertible on its own, and the data files have no header row to name their columns, so dump again without --tab.
Decimals and text in the .duckdb file
DuckDB takes the source's declared types more nearly unchanged than any other target here, which makes the two places where it cannot the things worth reading: the width of a decimal, and the length of a string.
- →DECIMAL tops out at 38 digits, so a wider source column is clamped rather than refused: an Oracle NUMBER(50,10) is created here as DECIMAL(38,10), and the scale is never allowed to grow past the precision holding it.
- →A decimal that declared no scale gets six places for its fraction rather than none, inside that same rule: a source precision of 10 becomes DECIMAL(10,6), one of 5 becomes DECIMAL(5,5), and one that declared no precision either becomes DECIMAL(18,6).
- →Strings become VARCHAR with no length attached to them. DuckDB's VARCHAR is unbounded, so no column has to be sized in advance and no row can be turned away for being longer than the column it goes in.
Reading mysqldump
- →Parsed with a real SQL parser, not regular expressions, so a value containing a closing parenthesis or a semicolon cannot split a row in half.
- →CREATE TABLE types, primary keys, NOT NULL and AUTO_INCREMENT are all read from the dump.
- →The source dialect is detected from the dump itself — MySQL, PostgreSQL and SQL Server dumps all parse.
Writing DuckDB
- →A real .duckdb file, not a script — open it straight away with the DuckDB CLI.
- →DuckDB has genuine DECIMAL and BOOLEAN types, so nothing is flattened on the way in.
What you get
A ZIP containing database.duckdb. If anything about your data needed a judgement call, a _warnings.txt explains it.
Questions
- Is converting mysqldump to DuckDB free?
- Yes. Files up to 10MB convert free with no account. There is a limit of five conversions per day per IP address.
- Will my mysqldump data keep its types in DuckDB?
- Yes — that is the point. Whole numbers, decimals, dates and booleans are mapped to real DuckDB types rather than everything becoming text. The mapping table above shows exactly what you get.
- Do you store my file?
- No. The file is written to a temporary directory, converted, and the directory is deleted as soon as your download has been sent.