AWS Schema Conversion Tool vs pgloader

AWS Schema Conversion Tool (AWS SCT) converts database schemas between engines, including relational OLTP, data warehouse, and NoSQL schemas. If it cannot automate a conversion, it gives guidance for creating an equivalent schema in the target database. A project wizard estimates migration complexity for supported destinations and generates a report for comparing target options. For warehouse migrations to Amazon Redshift, it can manage data extraction agents; it can also create, run, and monitor AWS DMS endpoints and tasks. AWS SCT converts SQL embedded in C++, C#, Java, and other application code for users to review, edit, and save. Supported workload conversions include SSIS packages, Teradata workloads, and Apache Oozie workflows to specified AWS services. It is both a standalone, project-based application and a command-line tool. Planned converted schemas stay local until applied to the target. AWS SCT is free and supports 64-bit Microsoft Windows, Fedora Linux, and Ubuntu Linux. It also supports FIPS standards for connections to Amazon S3 or another AWS resource and is compliant with FedRAMP.

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.