Percona Server Migration Tools

Use MySQL-family pair tools for Percona Server for MySQL, or PostgreSQL-family pair tools for Percona Distribution for PostgreSQL. Migrate once with DBConvert or keep a database pair aligned with DBSync.

Choose the Percona distribution and pair

The distribution selects the connection family; the other database selects the installer.

MySQL

Percona Server for MySQL

The installer name contains mysql because Percona Server uses the MySQL-family connection.

SQL Server ↔ Percona Server
Oracle ↔ Percona Server
PostgreSQL ↔ Percona Server
PostgreSQL

Percona Distribution for PostgreSQL

The installer name contains postgresql because this distribution uses the PostgreSQL-family connection.

MySQL ↔ Percona PostgreSQL
SQL Server ↔ Percona PostgreSQL
Oracle ↔ Percona PostgreSQL

Choose the product for the workflow

The pair determines compatibility; the product determines what happens after the first transfer.

DBConvert

One-time migration with target structure generation, adjustable type mappings, and transfer of selected tables and data.

DBSync

Initial migration plus one-way or bidirectional synchronization for databases that must remain aligned during cutover or afterwards.

DBConvert Studio

Migration and synchronization across several database platforms without purchasing a separate pair tool for every combination.

About Studio

Price and licensing

  • $179 one-time license for each DBConvert or DBSync pair tool.
  • Migration and synchronization are licensed separately.
  • Each pair tool works in either direction and between two servers from the same engine family.
License terms

Trial and runtime

  • Free, time-unlimited trial with record and feature limits.
  • Windows desktop application.
  • Connects to local, remote, and managed Percona servers.
Trial limitations

Migration scope

Separate database transfer from Percona infrastructure work.

Percona Server for MySQLPercona Distribution for PostgreSQL
ProtocolMySQLPostgreSQL
Connect toWritable SQL endpointPostgreSQL server endpoint
ValidateVersion, charset, collation, SQL behaviorExtensions, types, collation, server parameters
Outside DBConvertCluster topology, replication, failoverHA topology, backup, extension deployment

Handled in the migration workflow

  • Selected tables, fields, and rows
  • Generated target data types and table mappings
  • Supported indexes, views, primary keys, and foreign keys
  • Saved sessions for repeated test runs

Plan as separate work

  • Stored procedures, functions, and triggers
  • Application SQL and database-specific behavior
  • Percona high-availability and cluster configuration
  • Backup, monitoring, and production cutover validation