# Convert MariaDB to MySQL

> Convert MariaDB to MySQL on Layerbase. Review compatibility, copy into a new database, and check the verification report before switching.

Canonical: https://layerbase.com/convert/mariadb-to-mysql
Generated from Layerbase source: 2026-11-08

Move MariaDB tables into MySQL after reviewing MariaDB-only types, sequences, collations, and authentication. The target requires a plan that includes MySQL.

## How it works

1. **Review the pre-check.** Open your source database in Layerbase Cloud and choose Convert. Read the compatibility notes before creating the target.
2. **Create a new target.** Choose a name for the new database. Your plan must include the target engine.
3. **Copy the database.** Layerbase copies into the new target. The source stays in place while you check the result.
4. **Verify and cut over.** Read the verification report and test your application against the target. Stop source writes for the final copy, then switch your connection when you are satisfied.

## What is verified before cutover

- Source and target row counts are compared for the tables listed in the report. The report states how many tables were checked and whether any counts differ.
- If verification is unavailable, the report says so. Row counts do not prove that every value or database object is identical; test your queries before cutover.

## What does not carry over unchanged

- Stored procedures, functions, and scheduled events are not copied. Recreate them on the target.
- Custom DEFINER clauses can fail to restore or change an object's security context. Review them before copying.
- Triggers are copied, but their behavior needs a spot-check on the target.
- MariaDB UUID, INET4, INET6, and VECTOR columns and sequences need changes before copying to MySQL.
- uca1400 collations are mapped to the nearest utf8mb4_0900 equivalent. Sorting and uniqueness behavior need a spot-check.
- The direct port requires a client that supports caching_sha2_password. MySQL 9 clients cannot use the pooler port.

## Conversion questions

### Does conversion delete my source?

No. Conversion creates a separate target. Review it before choosing whether to decommission the source.

### Can I keep writing during cutover?

Writes made after the copy are not continuously replicated. Plan a write freeze for the final copy and check the target before switching your application.

### Which plan do I need?

MySQL starts on Solo. Your plan must include MySQL before you create the conversion target.

## Choose a source database

[Choose a source database](https://layerbase.com/cloud)

[All conversion paths](https://layerbase.com/convert)

[Conversion guide](https://layerbase.com/docs/converting-engines)