Migrating SQL Server Workloads to PostgreSQL
Proposed session for SQLBits 2026TL; DR
As cloud adoption and cost pressures grow, many teams are considering moving from SQL Server to PostgreSQL. This session covers when it makes sense to migrate, key differences between platforms, and the main steps: assessing compatibility, translating T-SQL to PL/pgSQL, and tuning for production so you can plan and execute a successful migration.
Session Details
As cloud adoption and cost optimization reshape data strategies, many organizations are considering a move from SQL Server to PostgreSQL — a powerful, open-source alternative. But migrating workloads isn’t just about exporting data and rewriting queries; it requires careful planning, tooling, and a deep understanding of the differences between platforms. While SQL Server offers rich features, seamless Microsoft integration, and mature tooling, its licensing costs and proprietary limitations can be significant. PostgreSQL, on the other hand, is free, extensible, and highly portable — but comes with a steeper learning curve and fewer built-in enterprise tools. In this session, we’ll walk through the key steps for a successful migration — from assessing compatibility and translating T-SQL to PL/pgSQL, to handling performance tuning and production readiness. You’ll walk away with a clear view of when, why, and how to migrate your SQL Server workloads to PostgreSQL.
3 things you'll get out of this session
*Clarity on when it makes business and technical sense to migrate from SQL Server to PostgreSQL
*A practical roadmap for migration: assessment, code translation, tooling, and performance tuning
*Awareness of key pitfalls, behavioral differences, and best practices for production-ready PostgreSQL deployments