Migrate MariaDB to MariaDB
Certified — live-tested pathSame-engine MariaDB migrations are how you move between hosts, clouds, or versions — and they still fail in the boring ways: half-copied tables, stale sequences, missing indexes. DBShifts moves the schema and every row, defers constraints for speed, reseeds counters, and proves the result with row counts and checksums.
Free tier · no credit card
Run the upgrade tool after the binaries change
After a newer MariaDB starts on an existing data directory, the system tables keep their old structure until mariadb-upgrade (formerly mysql_upgrade) runs. Until then some features and grants behave unpredictably, and the errors point at the system schema rather than at your tables.
It is a one-line step and the most commonly skipped one. Put it in the runbook immediately after the server starts on the new version, before the application reconnects.
MariaDB and MySQL are no longer the same database
A MariaDB-to-MariaDB move should stay that way. The two forked years ago and have diverged: MariaDB's JSON type is an alias for LONGTEXT with a validity check rather than a binary format, it has its own sequences and system-versioned tables, and replication between the two works only in limited combinations.
If a hosting change offers a 'MySQL-compatible' target, treat it as a cross-engine migration and check those features, rather than assuming a dump will load unchanged.
Galera clusters upgrade one node at a time
If the source is a Galera cluster, the move is usually a rolling upgrade: one node leaves, upgrades, rejoins and catches up before the next one goes. When a node has been away too long to catch up incrementally, it receives a full state transfer, copying the whole dataset over the network, so database size sets how long each node is out.
A cluster running mixed versions is a transitional state during the upgrade, not somewhere to stay. Plan the node order, and check the release notes for which versions can run side by side.
MariaDB → MariaDB conversion notes
Engine-specific rules baked into the conversion and transfer pipeline — verified by live certification of this exact pair.
- MariaDB's JSON columns (LONGTEXT + json_valid CHECK) are detected and mapped to real JSON types on targets that have them.
- Engine-specific CHECK constraints like json_valid() are filtered on targets that don't support them — data still migrates.
- Display-width unsigned types (bigint(20) unsigned) are recognized and widened correctly.
Frequently asked questions
Is MariaDB to MariaDB migration production-ready in DBShifts?
Yes. MariaDB to MariaDB is a certified pair: it passes the live certification suite on real MariaDB and MariaDB servers, which checks schema fidelity, row counts, type-aware checksums and paging across batches.
What changes in a same-engine MariaDB migration?
Structurally nothing changes — types map one-to-one. The risks are operational: half-copied tables, sequences left pointing at 1, and indexes that never got rebuilt. DBShifts reseeds counters to MAX(id)+1, defers then rebuilds constraints and indexes, and proves the copy with row counts and checksums.
Can I keep MariaDB and MariaDB in sync after the initial migration?
Yes, until you cut over. DBShifts reads the row-based binary log (binlog_format = ROW). With zero-downtime mode on, the log position is captured before the first row is copied, so writes made during the copy are replayed afterwards.
Go deeper
How We Live-Certified All 49 Migration Paths
The certification harness behind this page's claims.
Big-Bang, Trickle, or CDC: Choosing Your Migration Strategy
Pick by two numbers: the downtime you can afford, and how fast the source changes.
Reference
Compared with other tools
Ready to move MariaDB to MariaDB?
Set up in under two minutes. Validation and rollback included.
Start Free Migration