Supported platforms and databases v55

Database versions

You can use the following database product versions with Migration Toolkit:

  • PostgreSQL versions 12, 13, 14, 15, and 16
  • EDB Postgres Advanced Server versions 12, 13, 14, 15, and 16
  • Oracle 11g
  • Oracle 12c
  • Oracle 18c
  • Oracle 19c
  • SQL Server 2014
  • SQL Server 2016
  • SQL Server 2017
  • SQL Server 2019
  • MySQL 5.5
  • MySQL 5.7
  • MySQL 8.0
  • (Sybase) SAP Adaptive Server Enterprise 15.7
  • (Sybase) SAP Adaptive Server Enterprise 16.0

All the PostgreSQL and EDB Postgres Advanced Server versions available as BigAnimal single-node, primary/standby high-availability, and distributed high-availability cluster types are also supported for use with Migration Toolkit. See the BigAnimal (EDB’s managed database cloud service) documentation for more information about BigAnimal’s supported cluster types. See the database version policy documentation for the versions of PostgreSQL and EDB Postgres Advanced Server available in BigAnimal.

The superuser role isn't available in BigAnimal EDB Postgres Advanced Server distributed high-availability cluster databases. As a result, the following Migration Toolkit capabilities that require superuser access aren't supported when targeting BigAnimal distributed high-availability clusters:

  • The -copyViaDBLinkOra option that enables data migration using the db_link_ora extension
  • The Oracle-compatible SQL command CREATE DATABASE LINK

Contact your EnterpriseDB Account Manager or if you require support for other database products.


The Migration Toolkit isn't tested with and doesn't officially support use with Oracle Real Application Clusters (RAC) and Exadata. However, Migration Toolkit might work when it's connected to a single persistent node. For more information, contact your EDB representative.

Supported operating systems versions

Migration Toolkit supports installations on Linux, Windows, and MacOS platforms. See Product Compatibility for details.


The ojdbc7.jar can cause large data migrations to be incomplete due to a limit on records over Integer.MAX_VALUE (2147483647) while fetching from the ResultSet. To avoid this issue, we recommend upgrading to ojdbc8.jar.