Convert mysqldump to SQLite3
Upload a .sql file and get back a SQLite3 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 SQLite3
Generated from the converter's own SQLite3 type mapping — this is what it actually emits, not an example.
| Your data | SQLite3 type |
|---|---|
| Whole number | BIGINT |
| Decimal (money) | NUMERIC(10,2) |
| Floating point | REAL |
| True / false | BOOLEAN |
| Date | DATE |
| Date and time | TIMESTAMP |
| Short text | TEXT |
| Long text | TEXT |
| 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.
The .sqlite3 name and what carries over
The 3 in sqlite3 is the file format version and the name of the command-line tool, not a property of your conversion. One database file arrives, and the two things worth knowing about it are what it is called and what it leaves behind.
- →The file inside the zip is always database.sqlite, whichever spelling brought you to this page. Rename it to database.sqlite3, or to whatever a framework expects, once you have it - the header is what identifies it, never the extension.
- →An auto-increment column arrives holding all of its values and nothing that assigns new ones. No AUTOINCREMENT keyword is written, and the column is declared BIGINT rather than exactly INTEGER, so it is not an alias for the rowid either: rows you insert later have to supply their own key.
- →Only the rows are transactional. The very first CREATE TABLE runs in autocommit, and everything after it - that table's rows, and every later table - sits in one transaction that commits after the last row. A conversion that fails partway therefore leaves a file holding an empty shell of the first table and nothing else. You never receive that file: the zip is only assembled once the writer has returned.
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, SQL Server and Oracle dumps all parse. In an Oracle export, DATE keeps its time of day, TO_DATE values are read as timestamps, and an empty string becomes NULL, as Oracle stored it
Writing SQLite3
- →Columns get real declared types rather than everything being TEXT.
- →Primary keys and NOT NULL constraints are preserved.
- →A money column is declared DECIMAL_TEXT(10,2): because the type name contains TEXT, SQLite keeps 19.99 as written instead of converting it to a float. SQLite itself does arithmetic in floating point, so for exact sums in SQL pick the DuckDB target.
- →The same text storage means ORDER BY, min(), max() and comparisons treat money as text, so 99.23 sorts above 1007.64. Write CAST(column AS REAL) there; the README in the zip lists the columns.
What you get
A ZIP containing database.sqlite. If anything about your data needed a judgement call, a _warnings.txt explains it.
Questions
- Is converting mysqldump to SQLite3 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 SQLite3?
- Yes — that is the point. Whole numbers, decimals, dates and booleans are mapped to real SQLite3 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.