OSSeva Blog
MigrationHow to Evaluate a SQL Server to PostgreSQL Migration Partner
The short answer
A good SQL Server to PostgreSQL migration partner assesses each application before it quotes, rewrites T-SQL rather than hiding it, runs old and new side by side, plans a rollback, and supports PostgreSQL after cutover. A partner that quotes one price and one timeline for the whole estate without looking at it is guessing. If the reason for moving is an end date, start from SQL Server end of support options, because for some applications an upgrade is the better answer and a partner should say so.
Running PostgreSQL in production? OSSeva patches and supports it, end-of-life versions included.
PostgreSQL extended support: what is coveredWhat should an assessment cover?
It should cover every database, every T-SQL object and every client that connects, and end with a recommendation per application. Ask for the output in writing. The four outcomes are: stay on SQL Server and upgrade, convert to native PostgreSQL, try Babelfish, or leave the application alone. A partner who only ever recommends one of them is selling, not assessing. The Babelfish or native PostgreSQL decision is made per application, not per estate.
Questions to ask a migration partner
| Question | A good answer | A warning sign |
|---|---|---|
| How do you assess? | An inventory of databases, T-SQL objects and connecting clients, with a path per application | A flat quote before anyone sees the schema |
| How is the schema and data moved? | Named tooling, for example pgloader for schema and data, with rehearsed loads and row-count validation | "Automated conversion" with no mention of what is not converted |
| What happens to stored procedures, functions and triggers? | Rewritten in PL/pgSQL and reviewed; the migration guide lists the T-SQL differences | Silence about T-SQL, or a promise that it all converts |
| What about SQL Agent jobs, linked servers, SSIS and CLR? | Listed as separate work items with owners | Treated as out of scope until late in the project |
| How do you prove the new system is right? | A parallel run where applications and reports are checked against both systems | A single big-bang weekend with no comparison |
| What is the rollback plan? | A written plan and an agreed decision date, with SQL Server kept read-only until then | "We have never needed one" |
| Who supports PostgreSQL after cutover? | The same team or a named provider, with stated response times and patching | The project ends at go-live |
How should a partner quote the work?
The quote should follow what you can count, not a standard duration. The drivers are the number and size of schemas, the volume of T-SQL, the number of applications, SSIS packages and reports that connect, and the downtime window you can accept. Be wary of any fixed number of weeks quoted before an assessment. Ask what changes the price and what the partner would do if the assessment moved the scope.
What should support after cutover include?
It should name the PostgreSQL versions covered, the response times and the patch timing in the contract. OSSeva's published patch SLA is Critical within 48 hours and High within 7 days, with 24/7 reactive support on Assure and a 15-minute P1 response on Operate. Whoever you pick, compare the same three things in writing: versions, response times, patch timing.
Where OSSeva fits
OSSeva does not support or patch SQL Server. It sells SQL Server to PostgreSQL migration: assessment, conversion with pgloader and PL/pgSQL, a parallel run, cutover with a rollback plan, and PostgreSQL support from the day you cut over, priced per cluster. Where an upgrade is the better answer for an application, the written assessment says so. Use the table above on every vendor you talk to, OSSeva included, and see SQL Server end of support options for the full set of routes.
Frequently asked questions
How do I choose a SQL Server to PostgreSQL migration partner?
Ask for a per-application assessment, named tooling for schema and data, a plan for T-SQL objects, a parallel run, a written rollback plan and a support contract for PostgreSQL after cutover. The table above lists the questions and the warning signs.
How long does a SQL Server to PostgreSQL migration take?
It depends on the number and size of schemas, the amount of T-SQL, the clients that connect and your downtime window, so no honest figure exists before an assessment.
Can a partner migrate everything automatically?
Tools move schema and data, but stored procedures, SQL Agent jobs, linked servers, SSIS packages and CLR code need manual work or a decision to leave them.
Should every SQL Server database move to PostgreSQL?
No. A vendor-certified application that only runs on SQL Server should stay, and an upgrade or Extended Security Updates is the route for it.
Tags
Related articles
Babelfish or Native PostgreSQL? Choosing per Application
November 17, 2026MigrationSQL Server to PostgreSQL Migration Using pgloader
October 8, 2026MigrationSQL Server to PostgreSQL Migration: Tools, T-SQL Differences and Data Types
October 7, 2026MigrationPostgreSQL vs MySQL: Syntax Differences, Licensing, Replication and Which to Choose
October 7, 2026MigrationOracle Third-Party Database Support vs Leaving Oracle
October 8, 2026MigrationOracle to PostgreSQL Migration Using Ora2Pg: Step by Step
October 8, 2026Get a quote
Ready to get your open source under control?
Tell us what you run. An OSSeva engineer replies within 1 business day with CVE coverage and a price for your stack.
Prefer to talk or read more first?