Vitess Migration Tool

Move schema and data between Vitess and PostgreSQL, SQL Server, Oracle, MySQL, or MariaDB. DBConvert connects to the cluster through VTGate's MySQL protocol endpoint.

Choose the other database

Vitess uses the MySQL side of the selected database-pair tool.

Vitess ↔ PostgreSQL

DBConvert DBSync

Vitess ↔ SQL Server

DBConvert DBSync

Vitess ↔ Oracle

DBConvert DBSync

DBConvert or DBSync?

One-time migration — DBConvert

Select tables and fields, review the generated target structure, transfer the data through VTGate, and validate routing and application behavior before cutover.

Repeated comparison — DBSync

Evaluate standard non-trigger synchronization when the Vitess cluster and another database must be compared again after the initial load.

Validate before purchase: trigger creation and cross-shard writes depend on the Vitess topology, VTGate configuration, VSchema, and user privileges. Do not assume trigger-based or bidirectional DBSync will work through every VTGate deployment.

More Vitess directions

These pair tools also connect through their MySQL-family side.

View all MySQL-family tools

Vitess ↔ Access

Move Access tables into Vitess or export selected Vitess data to an Access database.

DBConvert DBSync

Vitess ↔ SQLite

Load a SQLite database into Vitess or create a local SQLite copy from Vitess data.

DBConvert DBSync

Vitess ↔ dBase / FoxPro

Move legacy DBF tables into Vitess or export selected Vitess data to DBF files.

DBConvert DBSync

Working with DB2, Firebird, Excel, or several database platforms in one project? Use DBConvert Studio instead of managing several pair tools.

Price and licensing

$179 one-time license for each DBConvert or DBSync pair tool.
DBConvert migration and DBSync synchronization are licensed separately.
One pair tool accepts either database family as source or destination.

License terms

Trial and runtime

Free, time-unlimited trial with record and feature limits.
Runs as a Windows desktop application.
Requires a reachable VTGate MySQL endpoint and credentials for the target keyspace.

Trial limitations

Prepare Vitess before the transfer

DBConvert moves relational schema and data; it does not design the Vitess topology.

VSchema and shard routing

Create the keyspace and define its VSchema, primary vindex, and sharding strategy before loading production data.
For sharded keyspaces, review primary keys and replace MySQL-style auto-increment assumptions with Vitess sequences where required.
Validate cross-shard transactions, views, stored routines, and application queries against the deployed Vitess version.

Vitess MySQL compatibility

VTGate connection checklist

1.Use a VTGate MySQL hostname and port, not a direct tablet or topology-service endpoint.
2.Select the prepared keyspace as the database and grant the account the required read or write privileges.
3.Apply the TLS and client-certificate settings configured on VTGate.
4.Run a representative subset and verify row routing across shards before the full transfer.

VTGate MySQL connection guide

Need native Vitess CDC?

Use Vitess VStream/VReplication for shard-aware change notifications and online Vitess workflows. DBConvert Streams does not currently provide a Vitess VStream source connector.

Vitess VReplication documentation