SQLite to MySQL Migration Converter
Create a MySQL schema and data draft locally, with explicit type mappings and unsupported-feature notes. No account or installation required. Your original file stays unchanged.
How to convert
- Open an unencrypted .db, .sqlite or .sqlite3 file in the workspace.
- Select a table to browse it, or write a query. Filters and sorting apply across the database.
- Choose Export data, select MYSQL, and save the complete export.
What the download contains
Exports ordinary tables and data for an empty MySQL database using InnoDB and utf8mb4. INTEGER maps to BIGINT, REAL to DOUBLE, TEXT to LONGTEXT and BLOB to LONGBLOB. NUMERIC affinity becomes text. NOT NULL is preserved; primary/foreign keys, other constraints, defaults, indexes, views, triggers, collations and AUTO_INCREMENT need manual recreation. Generated values are materialized. MySQL DDL implicitly commits: use a disposable test database first. Mixed incompatible values fail. Limits: 100,000 rows, 256 columns per table and 16 MiB SQL.
-- SQLite INTEGER -> MySQL BIGINT
-- SQLite TEXT -> MySQL LONGTEXT
-- SQLite BLOB -> MySQL LONGBLOBReview the migration before importing
The converter exports the whole database, regardless of your selected table or query. Read the mapping report in the workspace and SQL comments. This is a starting point for migration, not a schema-equivalent backup.
- Adjust target types, keys, constraints and defaults for your application.
- Import into an empty disposable target database using its native client.
- Compare row counts, exact IDs, NULLs, text, BLOBs and representative queries.
- Recreate indexes, relationships and ID generation, then test your application before replacing any production database.
SQLite Lab does not connect to MySQL or PostgreSQL. Target-server restoration has not been verified here. Virtual/shadow tables and incompatible mixed storage types are rejected.
Target database type referenceComplete export, bounded preview
The grid displays a bounded preview. CSV, JSON, Excel and PDF export runs one read-only SELECT again against the current database; it respects any LIMIT in your query. It does not rerun writes or export cached results. To export a whole table, select Current table with applied filters and sorting. Export one table per download.
File size and browser support
Rows are processed in chunks with progress and cancellation. Browsers with direct file saving write to disk; other browsers use a download limited to 64 MiB. Exceeding that limit fails explicitly instead of downloading a partial result. Large individual values and query execution limits still apply. Saved SQLite imports use browser storage; temporary database imports are limited to 100 MiB.
Keep a database backup
Use Export database for a complete SQLite snapshot, including full BLOBs. CSV and JSON are data formats, not schema-preserving backups. SQL dumps contain transaction commands that the workspace deliberately rejects; restore them in an external SQLite client.
Read the export guide · SQLite viewer · Convert CSV to SQLite