The short answer
Choose Babelfish when an application's T-SQL cannot realistically be rewritten and you are content to run on Aurora PostgreSQL; choose a native conversion when you want ordinary PostgreSQL that runs anywhere. The answer can differ between databases in the same estate, and it should be decided per application after an assessment. The wider choice, including upgrading, is on SQL Server end of support options.
Running PostgreSQL in production? OSSeva patches and supports it, end-of-life versions included.
PostgreSQL extended support: what is coveredHow do Babelfish and a native conversion compare?
| Question | Babelfish | Native PostgreSQL |
|---|---|---|
| What changes in the application? | Little: it keeps speaking T-SQL over the SQL Server protocol | The SQL, procedures and often the driver change |
| Where can it run? | Managed Babelfish is an Aurora PostgreSQL feature; elsewhere you build and run the open-source version yourself | Any PostgreSQL: your servers, VMs, Kubernetes or any cloud |
| What does not carry over? | CLR routines, availability groups and the BACKUP statement are unsupported; SQL Agent jobs and SSIS need new homes | All T-SQL must be rewritten; SQL Agent jobs, linked servers, SSIS and CLR need new homes too |
| Rollback | Easier to plan, because the application still speaks T-SQL | Needs the previous application build as well as the data |
| Skills needed to run it | T-SQL and PostgreSQL operations | PostgreSQL only |
The Babelfish limits above are those documented by AWS and the Babelfish project, as set out in our SQL Server to Aurora PostgreSQL guide; check the current lists for your target before you decide. Babelfish Compass reports which of your objects are affected.
How do you decide for each application?
Ask six questions in order, and let the first hard blocker decide.
- Who owns the code? For vendor software, follow what the vendor supports.
- What does Compass report? A dependency Babelfish does not support rules it out for that database until the dependency is removed.
- How much T-SQL is there? A small amount favours conversion; a large body with no team to rewrite it favours Babelfish.
- Where might it run later? If running PostgreSQL outside Aurora is realistic, converting now avoids a second migration.
- What drives the date? An end date can justify Babelfish first and conversion later. The SQL Server 2016 end of life, SQL Server 2017 end of life and SQL Server 2019 end of life posts give the dates.
- Who will run it? Babelfish needs people who know both T-SQL and PostgreSQL operations.
Where OSSeva fits
If the plan is Babelfish on Aurora, AWS is the right partner: OSSeva supports community PostgreSQL, not Babelfish's modified build, and it does not support SQL Server. For a native conversion, SQL Server to PostgreSQL with OSSeva assesses each application, converts the schema and T-SQL, runs old and new side by side and supports the PostgreSQL cluster from cutover, priced per cluster. Back to SQL Server end of support options for every route.
Frequently asked questions
Should I use Babelfish or convert to native PostgreSQL?
Use Babelfish where the T-SQL cannot be rewritten and Aurora is acceptable. Convert where you want portable PostgreSQL. Decide per application.
Does Babelfish support all T-SQL?
No. Documented gaps include CLR routines, availability groups and the BACKUP statement. Run Babelfish Compass on your schema first.
Can I run Babelfish outside Aurora?
The open-source project can be built and run yourself on its patched PostgreSQL. The managed feature is Aurora only.
Does OSSeva support Babelfish?
No. OSSeva supports community PostgreSQL, so it fits a native conversion, not a Babelfish deployment.
Tags
Related articles
SQL Server to PostgreSQL Migration: Tools, T-SQL Differences and Data Types
October 7, 2026MigrationHow to Evaluate a SQL Server to PostgreSQL Migration Partner
November 17, 2026MigrationSQL Server to PostgreSQL Migration Using pgloader
October 8, 2026MigrationSQL Server to Aurora PostgreSQL Migration: Babelfish vs Full Conversion
October 8, 2026MigrationPostgreSQL vs MySQL: Syntax Differences, Licensing, Replication and Which to Choose
October 7, 2026MigrationOracle Third-Party Database Support vs Leaving Oracle
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?