Azure Storage Mover vs pgloader

Azure Storage Mover moves files and folders from on-premises systems and cloud sources into Azure Storage. It can transfer to Azure Blob Storage or Azure Files from sources using SMB 2.x/3.x, NFS 3/4 or S3. Choose a one-time migration, recurring transfers, or a metadata-only run that creates folder structures and permissions without transferring file contents. Transfers can retain file structure, permissions, attributes and metadata. An Azure-hosted resource coordinates jobs, authentication and progress; agents scan and transfer data from on-premises systems or cloud virtual machines. For AWS S3-to-Azure moves, Azure Arc connectors provide source access and allow server-to-server copying without an agent. Transfers use HTTPS, and Private Link to storage accounts is optional. Storage Mover is free for on-premises-to-Azure and AWS-to-Azure scenarios, though standard storage, transaction and networking charges apply. Resources can be created in six listed regions, while data can be ingested into all Azure public regions. Microsoft reports no per-job file or directory limit and testing up to 500 million objects in on-premises scenarios.

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.