DBConvert, DBSync, and DBConvert Studio all migrate data between database platforms in either direction the pair supports - for example SQL Server and PostgreSQL, MySQL and Oracle, or Access and MySQL. Targets can be on-premises, remote, PostgreSQL-compatible, or other managed cloud services that accept standard connections.
What separates the three products is what happens after that first migration.
- What the products share
- DBConvert - one-time migration
- DBSync - recurring synchronization
- DBConvert Studio - both, across platforms
- Real-time replication (CDC)
- Recommendation
- Frequently asked questions
What the products share
Any DBConvert or DBSync pair tool, and DBConvert Studio, move structure and data between the source and target using the same overall workflow.
Common migration workflow
- Connect to the source database.
- Connect to the destination database - on-premises, remote, or a managed cloud service.
- Select the required tables and columns, indexes, and foreign keys.
- Review the automatically generated target structure and data type mappings.
- Apply table mapping and filtering options if required.
- Run the migration and monitor the progress.
- Save the session for reuse, scheduled execution, or command-line runs.
What gets transferred
Migration moves your schema and data: tables, columns, indexes, views, and foreign keys, with automatic data type mapping between the source and target.
Not transferred: stored procedures, functions, and triggers are not migrated and must be recreated manually if required.
DBConvert - one-time migration
DBConvert is focused on one-time migrations between two database platforms, for example SQL Server and PostgreSQL. It is the simpler, lower-cost choice when you only need to move one pair.
Limitation: DBConvert performs migration only. For recurring synchronization on the same pair, a separate DBSync license is required.
DBSync - recurring synchronization
DBSync keeps two databases aligned over time, replicating only the changes since the last run. See how database synchronization works for the sync types.
It adds one-way and bidirectional synchronization with Insert, Update, and Delete sync types, on top of the shared migration workflow.
Limitation: each DBSync license covers a single database pair.
DBConvert Studio - both, across platforms
DBConvert Studio combines migration and synchronization in one application and supports multiple database platforms.
What it adds over a single pair tool:
- No separate purchase for each database pair
- Reusable jobs across different source and target combinations
- Data distribution, where one source can be transferred to several destinations
Limitation: higher cost than a single pair tool if all you need is one migration.
Real-time replication (CDC)
DBSync's synchronization is scheduled and trigger-based. If you instead need continuous, low-latency replication that reads the database transaction log - log-based change data capture (CDC) - that is a separate product, DBConvert Streams.
Recommendation
- One-time SQL Server to PostgreSQL migration (or any single pair): DBConvert.
- Recurring synchronization on one pair: DBSync.
- Both, or work across multiple database platforms: DBConvert Studio.
Still unsure? Tell us whether you need a one-time migration, recurring synchronization, or both, and we will recommend the most suitable license.
Frequently asked questions
Can DBConvert run a recurring or scheduled migration?
DBConvert can re-run a saved migration on a schedule or from the command line, but each run transfers data as a migration. For change-based synchronization that moves only inserted, updated, and deleted rows since the last run, use DBSync.
How is licensing structured?
DBConvert and DBSync are licensed per database pair; DBConvert Studio is licensed once for many platforms. See License types & upgrade policy for tiers, user counts, and pricing.