Convert a MariaDB schema to MySQL

Paste the CREATE TABLE statements from MariaDB and ERD Designer draws them as a diagram. Change the diagram's target database to MySQL and every column's datatype is converted. You review each change before it is applied, then generate the MySQL script.

What changes in the sample

Converted to MySQL 8.4, these columns of the sample above change type. Everything else keeps its type; names, keys, nullability and lists of allowed values are left as they are.

What it tells you

Where a conversion loses something, ERD Designer says so rather than picking for you. These are the messages for the sample:

• customers.public_id: MySQL has no function this engine writes that generates a UUID — default UUID() removed; generate the values in your application.
• customers.last_ip: MySQL has no network-address type — "INET6" became VARCHAR(45), holding the address as text; nothing checks that a value is a valid address.

The MySQL script

This is what ERD Designer generates for the sample, for MySQL 8.4. Our test suite applies this conversion to a real MySQL server and then reads the database back to confirm it matches the diagram exactly.

-- Create table customers
CREATE TABLE `customers` (
  `customer_id` INT NOT NULL AUTO_INCREMENT,
  `public_id` CHAR(36) NOT NULL,
  `email` VARCHAR(255) NOT NULL,
  `full_name` VARCHAR(120) NOT NULL,
  `notes` LONGTEXT NULL,
  `is_active` TINYINT(1) NOT NULL DEFAULT 1,
  `last_ip` VARCHAR(45) NULL,
  `created_at` DATETIME(3) NOT NULL DEFAULT CURRENT_TIMESTAMP(3),
  PRIMARY KEY (`customer_id`)
) ENGINE=InnoDB;

-- Create table orders
CREATE TABLE `orders` (
  `order_id` BIGINT NOT NULL AUTO_INCREMENT,
  `customer_id` INT NOT NULL,
  `status` ENUM('new', 'paid', 'shipped') NOT NULL DEFAULT 'new',
  `total` DECIMAL(12,2) NOT NULL,
  `placed_at` DATETIME NOT NULL,
  `receipt_pdf` LONGBLOB NULL,
  PRIMARY KEY (`order_id`)
) ENGINE=InnoDB;

-- Add unique constraint on customers (email)
ALTER TABLE `customers` ADD CONSTRAINT `customers_email_uq` UNIQUE (`email`);

-- Create index on orders (placed_at)
CREATE INDEX `orders_placed_ix` ON `orders` (`placed_at`);

-- Add foreign key orders (customer_id) → customers (customer_id)
ALTER TABLE `orders` ADD CONSTRAINT `orders_FK1` FOREIGN KEY (`customer_id`) REFERENCES `customers` (`customer_id`);

How to convert your own schema

1. Paste your MariaDB script above and press Open in ERD Designer. The diagram opens laid out and ready to edit.
2. Click the diagram's name in the toolbar to open its properties, choose MySQL under Target Database / Version, and press Apply Changes.
3. If MySQL offers more than one way to store a kind of column, choose one and press Continue.
4. Read the list of retyped columns and any warnings, then press Apply Conversion. Save the diagram to keep it.
5. Press Generate DDL (the database icon) to copy or download the MySQL script — or apply it to a database on your own network with the ERD Designer Agent.

What it reads, and what it does not

• It reads CREATE TABLE, ALTER TABLE … ADD CONSTRAINT and CREATE INDEX: tables, columns, keys, foreign keys, unique constraints, check lists and indexes. Anything else in the script is skipped and listed.
• It converts the schema, never the data: no rows are read, moved or changed.
• It does not convert views, stored procedures, functions, triggers or packages.

Which plan you need

Pasting a script and working with it as a diagram is free on the Basic plan, with no card. Converting a diagram to another database is part of the Pro and Advanced plans, which also generate its script and can apply it through the Agent.

Other conversions

• MariaDB to PostgreSQL
• MariaDB to Oracle
• MariaDB to SQL Server
• MariaDB to SQLite
• MariaDB to Amazon Redshift
• MariaDB to Google BigQuery
• MariaDB to Snowflake
• PostgreSQL to MySQL
• Oracle to MySQL
• SQL Server to MySQL
• SQLite to MySQL
• Amazon Redshift to MySQL
• Google BigQuery to MySQL
• Snowflake to MySQL

Questions? Write to support@erddesigner.com. · ERD Designer · Terms · Privacy