Priority access when your migration or production system depends on pgloader
pgloader stays free and open source — that never changes. What this funds is the difference between a best-effort GitHub issue and an answer on a schedule you can plan around.
“Pgloader greatly reduced the time required to accomplish this complex migration.” — Alexander Groth, FusionBox, migrating a government agency off SQL Server
A production migration carries real risk regardless of the tooling
Delays, incompatibilities, edge cases that only show up against your actual data — without a path to priority handling, blockers delay CI/CD and release cycles, compatibility issues accumulate, and migration timelines slip. None of that is specific to pgloader; it's what happens whenever a critical dependency runs unfunded.
Moving terabytes with consistency, not just a successful dry run.
Usually the most expensive line item — and the one a stalled tool blocks hardest.
Maintaining uptime during switchover, on a schedule you chose.
One shared model across every project on oss.theartofpostgresql.com — pgloader, pgcopydb, pg_auto_failover, and pgextwlist, maintained in one place so it never drifts out of sync per project.
€0
For evaluating, or non-critical use.
Best-effort, through GitHub, like everyone else.
€100/mo
Your issues stop getting lost in the queue.
Priority queue, answered within a few days.
Get this tier →Recommended
€800/mo
When a production system depends on the tool.
Patches triaged under an SLA, land in the next release.
Get this tier →€2,000/mo
When your roadmap depends on its roadmap.
Roadmap input, and development bandwidth reserved for you.
Get this tier →€10,000/release
Time-critical dependencies, one release at a time.
Prioritized PRs and features, credited in the release notes. One sponsor per release.
Get this tier →€3,000/issue
One urgent blocker, handled outright.
Guaranteed resolution in the next release, no subscription required.
Get this tier →Same tiers as every project on oss.theartofpostgresql.com — one checkout, kept current in one place, whichever page you get here from.
Not case studies — direct quotes, attributed
“Thanks to pgloader we were able to migrate our main database from MySQL to Postgres, which involved moving hundreds of tables used by our complex Django project. Dimitri was very helpful. He implemented a new feature for us quickly and smoothly.”
Andrea Crotti, Iwoca
“Fusionbox used pgloader on a project for a large government agency. We needed to migrate a large set of data from an existing SQL Server cluster to a new PostgreSQL solution. Pgloader greatly reduced the time required to accomplish this complex migration.”
Alexander Groth, FusionBox
“Thank you for pgloader, it made our migration from MySQL to PostgreSQL really easy (~1Tb). It was almost too easy — I just ran the one-liner and waited for 48 hours. Nothing to change in the app, thanks to Hibernate.”
CommaFeed, via Twitter
Redpill Linpro sponsored MS SQL Server support in pgloader outright after asking what the most efficient way to migrate a customer off Microsoft SQL Server would be — the answer became a feature, now free for everyone. That's also how Azure AD authentication and multi-column foreign keys got funded — the Sponsor and Release Sponsor tiers above are the same mechanism, open to anyone.
The self-serve alternative to prioritized support
If you'd rather learn to run the migration end-to-end than pay for priority handling, there's a course for it: 16 modules, of which six are the method itself and five are specific to your source engine. The two engine lanes are siblings rather than steps — you buy the one you need, at the same price, or both. It teaches the same Continuous Migration method this tool was built for, hands-on against a real dataset, with pgloader doing the data step.
11 modules · first 4 free · $79
Why and whether to migrate, the migration budget, Continuous Migration architecture, automated failover with pg_auto_failover, nightly re-migration and the D-Day cutover, managed cloud PostgreSQL — then migrating data with pgloader, casting rules and schema mapping, the MySQL-quirks FAQ as graded exercises, porting stored procedures, triggers and views, and a hands-on build of your own migration.
See the full curriculum11 modules · same six common ones · $79
The same method, T-SQL-specific: pgloader from MS SQL Server, casting rules and schema mapping for MS SQL types, T-SQL to PL/pgSQL (triggers, TRY/CATCH, MERGE, cursors, OUTPUT), Babel Fish evaluated against a full migration, and a hands-on build that runs both paths on one schema so you can justify the call.
See pricingBoth lanes together, plus Oracle when it ships, is $129. There's a $49 price for lower-income regions and a $229 supporter price, all on the same checkout.
Professional services, beyond pgloader support tiers
As set out in the Migrating to PostgreSQL course, a database migration to PostgreSQL sets up in four steps: data migration, code migration (SQL, stored procedures, application architecture), service migration (the maintenance window), and opportunity cost. We can help at any step above, thanks to our network of Postgres professionals — hundreds of migrations handled, across many situations, constraints, and platforms. Whether you're migrating from MySQL or Oracle, MS SQL Server or RDS/Aurora, we can make it easier and ensure a successful result.
Copyright 2017-2026 © Dimitri Fontaine. All rights reserved.
Postgres, PostgreSQL and the Slonik Logo are trademarks or registered trademarks of the PostgreSQL Community Association of Canada. pgloader is an independent, unaffiliated project.