DBConvert Studio

Convert and sync across all your databases: servers, cloud and files.

Version
5.8.0
Release Date
Nov. 8, 2026
Size
183.0 MB
Platform
Windows 10 or later
Download DBConvert Studio Order from US$ 699

Rather not run it yourself?

Let us do the migration →

Servers

SQL Server
MySQL / MariaDB
PostgreSQL
Oracle
DB2
Firebird / InterBase

Cloud

Azure SQLvia SQL Server
Amazon RDS / Auroravia SQL Server / MySQL / PostgreSQL
Google Cloud SQLvia MySQL / PostgreSQL
Azure Database for MySQL / PostgreSQLvia MySQL / PostgreSQL
Supabasevia PostgreSQL
Neonvia PostgreSQL

Files

SQLite
Access
FoxPro
Excel

Good to know

  • Convert can also write a MySQL or PostgreSQL dump file.
  • Excel works with Convert only, not Sync: as a source, or as a new workbook.
  • DB2 pairs with SQL Server, MySQL and PostgreSQL.

Watch a SQL Server to PostgreSQL migration

One take in real time: the source, the destination, the plan, the run, and every row checked against the source.

Watch on YouTube (1:29)

How it works

1

Setup

  • Pick Convert or Sync.
  • Choose the source and the destination. A new connection starts with a card for each database type.
  • A connection is saved once and reused by every job.
Setup in DBConvert Studio: choosing the destination database type
2

Tables & mapping

  • Pick the tables.
  • Open one: each column shows the destination type it becomes. Change a type or a name in place.
  • The line at the bottom names anything that would fail.
Tables and mapping: the table list and one table's columns with their destination types
3

Execution

  • Review what the run will do and start it.
  • Read the log as it goes.
  • The job stays in the list to run again or put on a schedule.
A finished conversion: the summary and the operation log

Verify the copy New

A run can finish without errors and still leave changed data: some servers store a value they cannot hold in another form. Verify checks the destination after the run, on three levels:

  • Schema - every table and column is there, with the planned type.
  • Totals - row counts, sums, earliest and latest dates and text length match on both sides.
  • Rows - every row matches the one that was copied. The window shows which rows and columns differ.

Tick Verify after the run on Execution.

How Verify works
Watch on YouTube (1:24)

Much faster on large databases

Conversion and synchronization now take a fraction of the time.

  • Large tables are split across Worker threads, set on Execution.
  • Indexes are built after the data is loaded.
Speeding up large transfers

Time for a table of 10 million rows

Convert

Direction Time
MySQL to PostgreSQL 15 s
PostgreSQL to SQL Server 22 s
SQL Server to PostgreSQL 22.5 s
Oracle to MySQL 32 s
MySQL to Oracle 35 s
Firebird to SQL Server 37 s

Sync, nothing changed

Direction Time
PostgreSQL to MySQL 23 s
MySQL to PostgreSQL 26 s

Measured on our test stand, single runs. Convert at 16 worker threads; MySQL to PostgreSQL and Firebird to SQL Server at 4.

Run it again

  • Saved jobs - a job saves itself as you work. Jobs in the left rail lists them; open one and run it again.
  • Schedule… on Execution - daily, weekly or monthly. It runs with the app closed, as long as you are logged in to Windows.
  • Command line - --run-job with the saved job's name, for your own scripts.
Command line
The Schedule dialog: how often the job runs and when it starts

Try it on your own databases

Download

Rather not run it yourself? Let us do the migration →