---
title: "Migrate SQLite to MySQL in your browser"
description: "Migrate a SQLite database to MySQL: convert the .db file or its dump into a script with the same tables, keys and data, and a report of every change."
canonical: https://intosql.com/sqlite-to-mysql
last_updated: 2026-10-15
---

# Migrate SQLite to MySQL in your browser

Drop a SQLite database file (.db, .sqlite, .sqlite3) or the SQL that sqlite3's .dump writes, and download a script for MySQL with the same tables, keys, indexes and data. Each column gets the type its values fit, and every value MySQL can't hold as it is is listed in the report.

[SQLite to MySQL migration guide](https://intosql.com/docs/migrations/sqlite-to-mysql)

[SQLite to MySQL data types](https://intosql.com/docs/types/sqlite-to-mysql)

## What changes from SQLite to MySQL

Each row is a rule the converter applies, with the report line it writes when the rule changes something in your data.

| In SQLite | In MySQL | Report line |
| --- | --- | --- |
| declared types (any text: VARCHAR(255), DATETIME, BOOLEAN, JSON or none) | the type every value in the column fits |  |
| BOOLEAN, BOOL | tinyint(1) |  |
| TEXT, VARCHAR(n), CHAR(n), CLOB | varchar(n) up to 1024 characters, text types beyond |  |
| DECIMAL(p,s), NUMERIC | the exact type when every value fits it, else a double |  |
| BLOB, and columns holding bytes | blob types |  |
| DATE, DATETIME, TIMESTAMP holding ISO 8601 text | date, datetime(p) |  |
| JSON holding JSON text | json |  |
| Infinity in REAL columns | NULL | `invalid_value_null` |
| INTEGER PRIMARY KEY, AUTOINCREMENT | AUTO_INCREMENT, continuing after the highest id or sqlite_sequence's |  |
| COLLATE NOCASE | exact comparison (utf8mb4_bin) | `case_insensitive_collation` |
| generated columns | generated columns, STORED or VIRTUAL as in the source |  |
| generated columns with functions IntoSQL doesn't write, and the || operator | a plain column | `generated_not_translated` |
| defaults with functions IntoSQL doesn't write (strftime, randomblob) | no default | `default_not_translated` |
| CHECK constraints | translated |  |
| CHECK constraints with functions IntoSQL doesn't write | not created | `check_skipped` |
| partial and expression indexes | not created | `index_skipped` |
| foreign keys (unenforced unless PRAGMA foreign_keys=ON) | foreign keys, loaded with FOREIGN_KEY_CHECKS=0 |  |
| foreign keys to tables the dump doesn't create | not created | `foreign_key_skipped` |
| primary keys holding NULL, and NOT NULL columns with values that become NULL | NOT NULL dropped | `not_null_relaxed` |
| views, triggers and virtual tables (FTS, R*Tree) | listed in the report | `not_converted_objects` |
| dumps without CREATE TABLE (--data-only) | types read from the values | `no_schema` |
| expressions in INSERT values other than the text functions dumps write | NULL | `expression_value` |
| NUL characters in text | kept |  |
| text that isn't valid UTF-8 | the bad bytes as the replacement character | `invalid_utf8_replaced` |
| text decoded twice (ñ) | copied as it is | `mojibake_suspected` |

## Load the script into MySQL

The script creates the tables, copies the rows, then adds keys, indexes and foreign keys, so it loads fast and stops at the first error.

```shell
mysql --default-character-set=utf8mb4 mydb < sqlite.mysql.sql
```

Foreign keys are created as the dump declares them, with FOREIGN_KEY_CHECKS=0 while the rows load, so a row that points to a missing row doesn't stop the load.

For a large dump, run the client on the same machine as the server, and raise max_allowed_packet if a single row is very large.

IntoSQL Pro loads the file straight into MySQL from the desktop app or the command line, without writing a script.

## Dump SQLite for the best result

The converter reads what the dump holds. These options keep more of your data in it:

- The database file itself converts as it is, read page by page in your browser. Close the app that writes to it first, so no change is left behind in its -wal file.
- sqlite3 app.db .dump > app.sql writes the same database as SQL, which converts too, as .sql or .sql.gz.
- DB Browser for SQLite writes that SQL with File, Export, Database to SQL file, and so does Python's iterdump().

## What isn't converted

Views and triggers are written in SQLite's own language. They are listed in the report by name, never dropped silently, so you can rewrite them for MySQL. Virtual tables, such as FTS5 and R*Tree, are listed too, and their shadow tables are left out.

## Questions about SQLite to MySQL

### Is my dump uploaded?

No. The converter runs in your browser and reads the dump from your disk in pieces, so it never leaves your computer. The desktop app and the command line convert on your computer too.

### How large can the dump be?

The converter never holds the whole dump in memory: it reads the file twice, by ranges, and writes the script as it goes. Multi-gigabyte dumps convert in the browser, in the desktop app and with the command line.

### Can I convert the .db file itself?

Yes. Drop the .db, .sqlite or .sqlite3 file: it is read in your browser and never uploaded. Text with NUL characters and every digit of a double arrive as stored, which a .dump can cut short.

### Which SQLite versions can the dump come from?

Database files from SQLite 3.0 on, in UTF-8 or UTF-16, and dumps from the sqlite3 shell's .dump or Python's iterdump(). Every test file and dump comes from sqlite3 3.31 to 3.54, STRICT and WITHOUT ROWID tables included, and is compared with its source cell by cell.

### How are column types decided when SQLite doesn't enforce them?

The declared type is a hint and the values decide: a column becomes an integer, decimal, double, date, datetime, tinyint(1), blob or text type when every value fits it. Text in a key or with a default is varchar(768), so MySQL 5.7 can index it.

### Are INTEGER PRIMARY KEY and AUTOINCREMENT kept?

Yes. An INTEGER PRIMARY KEY becomes AUTO_INCREMENT, every row keeps its id, and the next id continues after the highest one, or after sqlite_sequence's value with AUTOINCREMENT.

### What about views and triggers?

They are listed in the report by name and not converted, because each database writes them in its own language.

### Which MySQL versions does the script load on?

MySQL 5.7 and later. Every test dump loads on 5.7 and 9, stopping at the first error if anything goes wrong.

## From SQLite

- [SQLite to PostgreSQL](https://intosql.com/sqlite-to-postgresql)
- [SQLite to MariaDB](https://intosql.com/sqlite-to-mariadb)
- [SQLite to SQLite](https://intosql.com/sqlite-to-sqlite)
- [SQLite to SQL Server](https://intosql.com/sqlite-to-sql-server)
- [SQLite to Oracle](https://intosql.com/sqlite-to-oracle)

## Into MySQL

- [MySQL to MySQL](https://intosql.com/mysql-to-mysql)
- [MariaDB to MySQL](https://intosql.com/mariadb-to-mysql)
- [PostgreSQL to MySQL](https://intosql.com/postgresql-to-mysql)
- [SQL Server to MySQL](https://intosql.com/sql-server-to-mysql)
- [Oracle to MySQL](https://intosql.com/oracle-to-mysql)

## Guide and every pair

- [MySQL to SQLite](https://intosql.com/mysql-to-sqlite)
- [SQLite to MySQL migration guide](https://intosql.com/docs/migrations/sqlite-to-mysql)
- [SQLite to MySQL data types](https://intosql.com/docs/types/sqlite-to-mysql)
- [Every database pair](https://intosql.com/database-migration)