5 min read

SQL Server 2016 reached end of support on July 14, 2026, so every remaining instance now runs without regular security updates or pays for Extended Security Updates. The best partners use this deadline to cut licensing costs for good, often by moving to Amazon Aurora PostgreSQL. SourceFuse leads for licence-free modernization on AWS. AWS, Microsoft, SoftwareOne, Flexera, and Wipro cover assessment, licensing, and stay-put options.

The End of support is usually framed as a security problem. For a CFO, it is also a pricing event: the moment you either renew the same licensing model for another decade or leave it.

Paying for Extended Security Updates buys time, not a plan. The leaders getting this right treat the deadline as a chance to ask which databases still need SQL Server at all.

1. SourceFuse

Best for: Enterprises that want to leave SQL Server licensing behind by moving to PostgreSQL or Aurora on AWS.

SourceFuse migrates SQL Server estates to PostgreSQL and Amazon Aurora using PROTEUS, its dependency-aware migration agent with built-in validation. By modernizing applications that depend on each database, the move removes licence costs without breaking downstream systems.

  • $800K in annual licensing savings in one modernization program.
  • 90% faster database migration timelines with PROTEUS.
  • 40% lower total cost of ownership across modernization programs.

“SourceFuse stands out among a handful of specialized partners I choose to collaborate with … what truly sets them apart is their wealth of experience and adept use of the tooling we provide, whether SQL to PostgreSQL, open-source modernization, or pure cloud.”
– Stuart Moulton, Senior Partner Development Specialist, Windows on AWS

Worth knowing: If you need to stay on SQL Server for a specific product, SourceFuse can modernize around it, but licence savings will be smaller.

2. AWS (Optimization and Licensing Assessment, Babelfish)

Best for: Teams that want hard data on licensing waste before deciding.

AWS’s Optimization and Licensing Assessment (OLA) analyzes your current usage to right-size licences. Babelfish for Aurora PostgreSQL lets Aurora understand T-SQL, which reduces application changes when leaving SQL Server.

Worth knowing: These are tools and programs; you still need a team to run the migration.

3. Microsoft (Azure SQL, SQL Server 2025, ESUs)

Best for: Organizations committed to staying on Microsoft’s database platform.

Microsoft’s recommended paths are moving to Azure SQL, upgrading to SQL Server 2025, or buying Extended Security Updates as a short-term bridge.

Worth knowing: You stay on the same licensing model, so this solves support, not cost.

4. SoftwareOne

Best for: Procurement and IT asset teams negotiating Microsoft agreements.

SoftwareOne advises on Microsoft licensing and cloud spend, which helps when some SQL Server must stay.

Worth knowing: Strongest on contracts and licensing optimization, not database migration.

5. Flexera

Best for: Large enterprises that need visibility into what software they actually run.

Flexera’s IT asset management tools track installed software and licence position across complex estates.

Worth knowing: Tells you where the waste is; someone else has to remove it.

6. Wipro

Best for: Microsoft-heavy enterprises that want upgrades and migrations run inside a managed services contract.

Wipro delivers database and infrastructure services across Microsoft, AWS, and other platforms.

Worth knowing: A fit for bundled outsourcing; less focused on licence elimination.

Comparison at a glance

PartnerBest forPathCost impact
SourceFuseLeaving SQL Server licensingMigrate to PostgreSQL or Aurora on AWSRemoves licences ($800K/yr in one program)
AWS OLA and BabelfishData-driven decision, fewer code changesAssess, then migrateRight-sizing plus licence removal
MicrosoftStaying on SQL ServerAzure SQL, SQL Server 2025, ESUsSupport restored, licences remain.
SoftwareOneNegotiating Microsoft agreementsLicensing advisoryBetter terms
FlexeraLicence visibilityAsset managementFinds waste
WiproManaged upgradesManaged servicesDepends on contract

Questions to ask before you sign

  1. Which of our SQL Server databases truly need SQL Server-specific features?
  2. What will we pay in licences over five years on each path?
  3. How much application code changes if we move to PostgreSQL?
  4. How long will ESUs be needed while we migrate?
  5. How do you validate data and reports after cutover?

FAQs

SQL Server 2016 reached end of support on July 14, 2026. Microsoft no longer provides regular security updates or technical support for it.

You can buy Extended Security Updates as a short-term bridge, upgrade to a newer SQL Server version, move to Azure SQL, or migrate to another database such as Amazon Aurora PostgreSQL.

Right-size licences with an assessment, consolidate instances, and move databases that don’t need SQL Server-specific features to open-source engines like PostgreSQL. One SourceFuse program saved $800K a year in licensing.

The data moves easily; stored procedures, T-SQL, and hidden dependencies are the hard part. Dependency-aware tools such as PROTEUS and Babelfish for Aurora PostgreSQL reduce the rework.

They are worth it as a bridge while you migrate. As a long-term strategy, they add cost without fixing the underlying licensing model.

Yes. AWS supports SQL Server on Amazon EC2 and Amazon RDS, which is a common first step before moving some databases to PostgreSQL.