Azure Database Migration Tools

Move schema and data to or from Azure SQL Database, SQL Managed Instance, Azure Database for MySQL, and Azure Database for PostgreSQL.

Start with the Azure target

The service determines the connector family, connection path, and objects that need separate migration work.

SQL Server

Azure SQL family

Uses the SQL Server connection family.

Azure SQL DatabaseSQL Managed Instance
Target scopeIndividual managed databaseManaged SQL Server instance
ConnectionLogical server and databaseManaged Instance endpoint and database
DBConvertSelected schema and dataSelected schema and data
Separate workServer logins, SQL Agent jobs, infrastructureLogins, credentials, jobs, operators, instance objects
View SQL Server pair tools

Azure Flexible Server

Choose the engine running on the Azure server. Connection and validation requirements are covered below.

MySQL

MySQL

MySQL-family pair tools
PostgreSQL

PostgreSQL

PostgreSQL-family pair tools

Choose the pair for the Azure destination

Every pair works in either direction. DBConvert handles migration; DBSync is the separately licensed synchronization product.

Paths involving Azure SQL

Use these when Azure SQL Database or Managed Instance is one side of a cross-engine project.

Oracle ↔ Azure SQL

DBConvertDBSync

MySQL ↔ Azure SQL

DBConvertDBSync

PostgreSQL ↔ Azure SQL

DBConvertDBSync

Paths involving Flexible Server

Use these for Azure Database for MySQL or PostgreSQL.

Oracle ↔ Azure Database for MySQL

DBConvertDBSync

Oracle ↔ Azure Database for PostgreSQL

DBConvertDBSync

MySQL ↔ Azure Database for PostgreSQL

DBConvertDBSync

DBConvert

Use it for a one-time schema-and-data migration, repeated test loads, or an export from Azure.

DBSync

Use it for scheduled row comparison. Trigger-based and bidirectional modes depend on the selected engine and Azure privileges; verify the intended mode with the trial.

$179 one-time license per DBConvert or DBSync pair tool. The products are licensed separately; the free Windows trial is time-unlimited with record and feature limits.

License termsTrial limitsSeveral pairs? Studio

Connect to the selected Azure service

DBConvert uses the database endpoint; Azure networking and service configuration must already allow the Windows client to connect.

Azure SQL Database

  • Use the logical server FQDN and target database.
  • Allow access through firewall rules or a private endpoint.
  • Review unsupported server-level objects separately.
Azure SQL connection guide

SQL Managed Instance

  • Use the Managed Instance endpoint and database port.
  • Provide a VNet, VPN, private endpoint, or another reachable network path.
  • Inventory instance-level objects outside DBConvert.
Managed Instance considerations

MySQL or PostgreSQL Flexible Server

  • Use the server FQDN, database name, and database credentials.
  • Apply firewall, private networking, and TLS requirements.
  • Validate extensions, collations, and server parameters.
MySQL guidePostgreSQL guide

Before the full run

  • Test representative tables and review generated target types and keys.
  • Verify stored procedures, functions, triggers, and application SQL separately.
  • Inventory jobs, logins, extensions, and service-level configuration outside the data-transfer job.