pgloader vs YugabyteDB Voyager

pgloader migrates database and flat-file data into PostgreSQL using schema translation, casting rules, and parallel loading. Listed sources are MySQL, MariaDB, MS SQL Server, SQLite, CSV, fixed-width files, and DBF; Oracle support is not built yet. Its pipeline fetches the source catalog, prepares the PostgreSQL target, runs parallel COPY, creates indexes in parallel, and completes the schema. MySQL handling includes enum translation, converting TINYINT(1) to boolean, zero-date handling, and looking up credentials in .my.cnf. The MS SQL Server path includes Azure AD authentication, sequence migration, and multi-column foreign keys. For file imports, rejected rows can be separated after a failed COPY transaction while accepted rows continue loading. Custom casting rules go in a .load file. Version 3 in Common Lisp is the stable packaged release; version 4 is a pre-release JAR requiring Java 21 or later. The free Community tier has best-effort GitHub support. Paid support starts at €100/mo, with higher tiers offering priority handling, SLA-triaged patches, roadmap input, or issue-based support. It is self-hosted on Linux.

YugabyteDB Voyager has no write-up on Specifiction yet; its figures are above.