One-time migration — DBConvert
Transfer selected tables and data, review generated type mappings, and recreate supported indexes, views, and foreign keys. Stored procedures, functions, and triggers remain a separate rewrite task.
MariaDB Migration Tools
Migrate MariaDB schema and data to or from SQL Server, Oracle, PostgreSQL, SQLite, Access, and more. Use DBConvert for a one-time migration or DBSync to keep both databases aligned during a staged cutover.
Choose the right MariaDB tool
Start with what must happen after the initial data transfer.
Recurring synchronization — DBSync
Run the initial load, then synchronize inserts, updates, and deletes one way or bidirectionally. Use scheduled or trigger-based sync when both databases must remain aligned during cutover or afterwards.
Several database platforms — DBConvert Studio
Use one application for migration and synchronization across multiple database platforms instead of purchasing a separate tool for each pair.
Download a MariaDB pair tool
MariaDB uses the MySQL-family connection, so the installer name contains mysql. Choose DBConvert or DBSync for the other database in your pair.
One pair license covers every direction
Use either database family as the source or destination. A separate direction-specific license is not required.
| Source | To MySQL / MariaDB | To PostgreSQL |
|---|---|---|
| MySQL / MariaDB | ||
| PostgreSQL |
Price and licensing
- $179 one-time license for each DBConvert or DBSync pair tool.
- DBConvert migration and DBSync synchronization are licensed separately.
- DBConvert Studio uses separate multi-platform pricing.
Trial and runtime
- Free, time-unlimited trial with record and feature limits.
- Windows desktop application.
- Connects to local, remote, or managed MariaDB servers.
How a MariaDB migration works
-
1
Connect both databases
Select MariaDB through the MySQL-family connection, then configure the other database as source or destination.
-
2
Review the target structure
Choose tables and fields, then review generated data types, indexes, keys, and table mappings.
-
3
Run and validate
Transfer the data, inspect the results, and validate application behavior before the production cutover.
MariaDB Cloud, formerly SkySQL
Use the same MySQL-family pair tools; there is no separate SkySQL connector or license.
Connection details
- Copy the host, port, database name, username, and password from MariaDB Cloud.
- Configure the MariaDB connection in DBConvert or DBSync as either source or destination.
Network and TLS
- Allow the Windows machine running DBConvert to reach the cloud service.
- Apply the SSL/TLS settings and certificates required by the service before testing the connection.
Native export versus cross-engine migration
Native exports remain useful, but they do not replace target-specific schema conversion.
mariadb-dump
Produces MariaDB/MySQL-flavored SQL, including engine-specific identifiers and table options. It is suited to backup and compatible-server moves, not direct loading into another SQL dialect.
CSV export
SELECT ... INTO OUTFILE moves rows but drops data types, primary keys, indexes, and foreign keys. You rebuild the schema by hand on the target first.
Federated access
A live remote connection can expose data across servers, but it still requires connectivity, target schema design, and validation of engine-specific behavior.
DBConvert generates a target structure for review, transfers the selected data, and recreates supported indexes and keys. Validate mappings and application behavior before cutover.
MariaDB Migration Directions
Start with the pair that matches the other database in the migration.
MariaDB ↔ SQL Server
Use the SQL Server/MySQL-family pair for transfers between MariaDB and SQL Server. Review the generated mappings before the run:
- Identifier quoting and target table definitions are generated for SQL Server.
TINYINT(1), text, date/time, and identity mappings remain adjustable per field.- Supported indexes and foreign keys are recreated after the table structure is reviewed.
Separate rewrite: stored procedures, functions, and triggers are not auto-translated to T-SQL.
MariaDB ↔ Oracle
Use the Oracle/MySQL-family pair for transfers between MariaDB and Oracle. Treat schema conversion and application SQL as separate review tracks:
- Review numeric, character, date/time, and large-object mappings against the target schema.
- Supported indexes and primary/foreign keys are recreated with the transferred tables.
- MariaDB Oracle mode can support selected Oracle syntax, but it is version-dependent and does not replace application compatibility testing.
Separate rewrite: PL/SQL packages, procedures, and triggers are not transferred automatically.
Other MariaDB directions
MariaDB ↔ PostgreSQL
Migrate MariaDB to PostgreSQL, or pull PostgreSQL back in - cross-engine type mapping handled.
MariaDB ↔ Access
Move Microsoft Access tables into MariaDB, or pull MariaDB data into an Access file.
MariaDB ↔ SQLite
Convert MariaDB to SQLite for an embedded copy, or load SQLite back into MariaDB.
MariaDB ↔ dBase / FoxPro
Move legacy dBase/FoxPro (DBF) tables into MariaDB, or export MariaDB out to DBF.
Any pair, one tool
DB2, Firebird, and Excel pair tools are also available through the MySQL-family tools page. Use DBConvert Studio when one project spans several database platforms instead of a single licensed pair.
What's different from MySQL
MariaDB has a few features MySQL doesn't. They change how the schema converts:
JSON columns
MariaDB stores JSON as a LONGTEXT alias with JSON validation rather than MySQL's binary JSON format. Review the generated target type and application access pattern before transfer.
Sequence objects
Do not assume MariaDB sequence objects will be converted with table data. Inventory them separately and recreate the required behavior on the target.
Oracle mode
SQL_MODE='ORACLE' changes accepted SQL and stored-routine syntax. It does not make Oracle application SQL or PL/SQL automatically portable.
Storage engines & connection
DBConvert connects through the MySQL-family connection. Review storage-engine-specific table options because the target database will use its own storage model.
Need log-based, real-time CDC?
DBConvert Streams is a separate product for continuous, log-based change data capture. DBConvert and DBSync covered on this page focus on migration, scheduled sync, and trigger-based sync.