Database Conversion Tools

Supported databases

Access and Access 365, DB2, the dBase family (dBase, xBase, FoxBase, FoxPro, Visual FoxPro, HiPer Six, Clipper), MySQL and its forks (MariaDB, Percona), Oracle, SQLite, PostgreSQL, Redshift, SQL Server and Azure SQL — as well as MongoDB and Redis.

Kinds of job

• Migrate — move a whole database to a different engine, keeping tables, keys and indexes.
• Copy — duplicate selected tables, or one table, into another database with the same or a different structure.
• Sync — keep a source and a target in step, applying inserts, updates and deletes.
• Merge — combine rows from several tables or databases into a single target table.
• Export and import — move a table or a query result out to a file, or load a file into a table.

Same engine or different engine

Copying between two databases of the same engine is mostly a matter of pointing at both sides and pressing go. Crossing engines needs a bit more care: numeric widths, date formats and boolean representations differ, so the tools let you review and adjust the column mapping before the job runs, and report what they changed.

Large objects and awkward columns

BLOB and CLOB columns hold documents, images, audio and long text. They can be exported from the database to individual files on disk — or loaded from a folder of files back into a column — which makes them practical to back up, inspect and move between platforms.

Automating database transfers

Any job can be saved and run again. Run it on a schedule for nightly replication or a periodic export, or call the command-line mode from your own script or job scheduler. Because the tool runs locally, it works the same on a laptop, a build server or a machine with no internet access.

Browse by database

• Access Conversion Tools
• DB2 Conversion Tools
• DBF Conversion Tools
• dBase Conversion Tools
• xBase Conversion Tools
• FoxBase Conversion Tools
• FoxPro Conversion Tools
• Visual FoxPro Conversion Tools
• HiperSix Conversion Tools
• Clipper Conversion Tools
• MySQL Conversion Tools
• MariaDB Conversion Tools
• Percona Conversion Tools
• Oracle Conversion Tools
• SQLite Conversion Tools
• PostgreSQL Conversion Tools
• RedShift Conversion Tools
• SQL Server Conversion Tools
• Azure Conversion Tools
• MongoDB Conversion Tools
• Redis Conversion Tools

Frequently asked questions

Which databases are supported?

Access, Access 365, DB2, dBase, xBase, FoxBase, FoxPro, Visual FoxPro, HiPer Six, Clipper, MySQL, MariaDB, Percona, Oracle, SQLite, PostgreSQL, Redshift, SQL Server and Azure SQL, plus MongoDB and Redis.

Can I copy data between two different database engines?

Yes. Cross-engine work is the main use case: pick a source table or query in one engine and a target table in another, then map the columns. Data types are converted automatically where a sensible equivalent exists.

What is the difference between migrate, copy, sync and merge?

Migrate moves a whole database to a new engine. Copy duplicates selected tables. Sync keeps two databases in step by applying inserts, updates and deletes. Merge combines rows from several sources into one target table.

Can the tools handle tables with millions of rows?

Yes. Rows are transferred in batches rather than all at once, so large tables move without exhausting memory on either side.

How are BLOB and CLOB columns handled?

Large binary and text objects can be exported from a column to individual files, or loaded from files back into a column, with the file naming scheme under your control.

Can a transfer run unattended?

Yes. Save the job and schedule it — nightly replication, periodic exports and one-off migrations all use the same job definition, and the command-line mode can be called from your own scripts.