--- title: "Migrate MySQL to MariaDB in your browser" description: "Migrate a MySQL or MariaDB database to MariaDB: convert its dump into a script with the same tables, keys and data, and a report of every change." canonical: https://intosql.com/mysql-to-mariadb last_updated: 2026-10-15 --- # Migrate MySQL to MariaDB in your browser Drop a dump from mysqldump, mariadb-dump, mysqlpump, phpMyAdmin or Adminer, as .sql or .sql.gz, and download a script for MariaDB with the same tables, keys, indexes and data. Every value MariaDB can't hold as it is, and every object it doesn't carry, is listed in the report. [MySQL to MariaDB migration guide](https://intosql.com/docs/migrations/mysql-to-mariadb) [MySQL to MariaDB data types](https://intosql.com/docs/types/mysql-to-mariadb) ## What changes from MySQL to MariaDB Each row is a rule the converter applies, with the report line it writes when the rule changes something in your data. | In MySQL | In MariaDB | Report line | | --- | --- | --- | | utf8mb4_0900_* and utf8mb4_uca1400_* collations | utf8mb4_unicode_520_ci for utf8mb4_0900_* (utf8mb4_bin for binary ones) | `collation_replaced` | | zero, partial or impossible dates (0000-00-00, 2024-02-30) | kept | | | TIME | TIME, durations included | | | TINYINT(1), BOOL | TINYINT(1) | | | UNSIGNED and ZEROFILL | kept | | | ENUM and SET, the '' error value included | kept | | | JSON | JSON (LONGTEXT checked by MariaDB) | | | NUL bytes in text | kept | | | AUTO_INCREMENT | AUTO_INCREMENT with the table's counter | | | MyISAM AUTO_INCREMENT on the second column of a key, in a table that isn't MyISAM in the dump | an index on the column and one counter for the table | `myisam_group_autoincrement` | | ON UPDATE CURRENT_TIMESTAMP | kept | | | generated columns | VIRTUAL or STORED as in the source | | | generated columns with functions IntoSQL doesn't read | a plain column | `generated_not_translated` | | INVISIBLE columns | INVISIBLE columns | | | CHECK constraints | kept | | | CHECK constraints with functions IntoSQL doesn't read | not created | `check_skipped` | | CHECK ... NOT ENFORCED | not created | `check_not_enforced` | | expression defaults, and defaults on TEXT, BLOB, JSON and GEOMETRY | kept | `default_not_translated` | | functional indexes, KEY ((expr)) | not created | `index_skipped` | | keys and indexes on a prefix, c(20) | kept | | | FULLTEXT indexes | kept | | | SPATIAL indexes | kept | | | foreign keys | kept, loaded with FOREIGN_KEY_CHECKS=0 | | | GEOMETRY, POINT, POLYGON... | kept, with each value's SRID | | | INET4, INET6, UUID (MariaDB) | kept | | | BINARY, VARBINARY, BLOB | kept | | | PARTITION BY | one table | `partitions_dropped` | | WITH SYSTEM VERSIONING (MariaDB) | WITH SYSTEM VERSIONING, starting from the current rows | | | Aria, ColumnStore, CONNECT, Spider, RocksDB (MariaDB) | kept | | | CREATE SEQUENCE (MariaDB) | CREATE SEQUENCE with its next value | | | views, triggers, procedures, functions and events | listed in the report | `not_converted_objects` | | NOT NULL columns with values that become NULL | NOT NULL dropped | `not_null_relaxed` | | text that isn't valid in its character set | the bad bytes as the replacement character | `invalid_utf8_replaced` | | text decoded twice (ñ) | copied as it is | `mojibake_suspected` | | dumps without CREATE TABLE | types read from the values | `no_schema` | | geometries in a dump without CREATE TABLE | GEOMETRY | | | SET NAMES utf8 from utf8mb4 tables | converted, with a warning | `dump_lost_four_byte_chars` | | dumps without SET NAMES whose text isn't UTF-8 | read as Latin-1 (Windows-1252) | `charset_guessed` | | sjis, cp932, gbk, big5 dumps | read as UTF-8, with a warning | `unsupported_charset` | | UNHEX('..'), CONVERT(b'..', UNSIGNED), CONVERT(".." USING x), ST_GeomFromText('..') in rows | evaluated | | | other expressions in rows | NULL | `expression_value` | | DEFAULT in VALUES | the column's default value | `default_keyword_filled` | | DEFAULT in VALUES without a literal default | NULL | `default_keyword_null` | | REPLACE and INSERT IGNORE | plain rows | `replace_as_insert` | | types IntoSQL doesn't know | LONGBLOB | `unknown_type` | | values that don't fit their column | NULL | `invalid_value_null` | | unreadable geometries | NULL | `bad_geometry` | | TIMESTAMP | kept, loaded in the time zone the dump states | | | VECTOR(n) (MariaDB 11.7+) | json with the floats as an array | `type_replaced` | ## Load the script into MariaDB 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 mariadb --default-character-set=utf8mb4 mydb < mysql.mariadb.sql ``` Foreign keys are created as the dump declares them, with FOREIGN_KEY_CHECKS=0 while the rows load, as mysqldump does. 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 MariaDB from the desktop app or the command line, without writing a script. ## Dump MySQL for the best result The converter reads what the dump holds. These options keep more of your data in it: - --default-character-set=utf8mb4 keeps emoji and other 4-byte characters, which a utf8 dump loses before the converter sees it. - --hex-blob writes binary columns as hexadecimal, which survives copying between systems. - --routines --triggers --events add those objects to the dump, so the report can list them. ## What isn't converted Views, triggers, stored procedures, functions and events are written in each database's own language. They are listed in the report by name, never dropped silently, so you can rewrite them for MariaDB. ## Questions about MySQL to MariaDB ### 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. ### Does it read MariaDB dumps? Yes. Dumps from mariadb-dump and from MariaDB 10.3 to 12 convert the same way, including MariaDB's INET6, INET4 and UUID columns. ### What happens to 0000-00-00 dates? MariaDB keeps them: the script sets a SQL mode that accepts zero and impossible dates while it loads, so they arrive as they are. ### Are AUTO_INCREMENT values kept? Yes. AUTO_INCREMENT stays as it is, and the table's counter continues where the dump left it. ### Does TINYINT(1) become boolean? It stays TINYINT(1), as in the source, so every value keeps its number. ### What about stored procedures and triggers? They are listed in the report by name and not converted, so you can check each one against MariaDB before recreating it. ON UPDATE CURRENT_TIMESTAMP stays as it is. ### Which MariaDB versions does the script load on? MariaDB 10.11 and later. Every test dump loads on 10.11 and 11.4, from MySQL 5.7 to 9 and from MariaDB. ## From MySQL - [MySQL to PostgreSQL](https://intosql.com/mysql-to-postgresql) - [MySQL to MySQL](https://intosql.com/mysql-to-mysql) - [MySQL to SQLite](https://intosql.com/mysql-to-sqlite) - [MySQL to SQL Server](https://intosql.com/mysql-to-sql-server) - [MySQL to Oracle](https://intosql.com/mysql-to-oracle) ## Into MariaDB - [MariaDB to MariaDB](https://intosql.com/mariadb-to-mariadb) - [PostgreSQL to MariaDB](https://intosql.com/postgresql-to-mariadb) - [SQL Server to MariaDB](https://intosql.com/sql-server-to-mariadb) - [SQLite to MariaDB](https://intosql.com/sqlite-to-mariadb) - [Oracle to MariaDB](https://intosql.com/oracle-to-mariadb) ## Guide and every pair - [MariaDB to MySQL](https://intosql.com/mariadb-to-mysql) - [MySQL to MariaDB migration guide](https://intosql.com/docs/migrations/mysql-to-mariadb) - [MySQL to MariaDB data types](https://intosql.com/docs/types/mysql-to-mariadb) - [Every database pair](https://intosql.com/database-migration)