Notes7 min read

Windows Server 2016 and SQL Server in a deal: the fee is known, the move is not

SQL Server 2016 left extended support in July 2026, Windows Server 2016 follows in January 2027 and SQL Server 2017 in October 2027. In smaller companies they often carry the accounting, the ERP and the internal systems. Microsoft sells security updates by the year, but the move to a supported version is the real project, and around a sale it is the part that gets priced.

Within fifteen months, three pieces of the Microsoft server stack leave extended support. SQL Server 2016 left it in July 2026, Windows Server 2016 follows in January 2027 and SQL Server 2017 in October 2027. In many small and mid-sized companies they carry the accounting package, the ERP and the internal tools on a server in a closet or a rented rack. Microsoft sells paid Extended Security Updates for some of them, by the year. That fee is a known number. The move to a supported version is the real project, and around a sale it is the part that gets priced.

This note is for owners preparing a sale, buyers reading a target and their advisors. How to upgrade each server is an engineering question; here we look at what the dates do to a deal.

The dates

DateWhat endsPaid updates after it
14 July 2026Extended support for SQL Server 2016.Extended Security Updates for up to three years, until July 2029.
12 January 2027Extended support for Windows Server 2016.Extended Security Updates for up to three years, sold as Year 1, 2 and 3, the last ending 8 January 2030.
12 October 2027Extended support for SQL Server 2017.Microsoft's SQL Server ESU pages cover 2014 and 2016 only. Nothing is stated yet for 2017.

The dates come from Microsoft's lifecycle pages for Windows Server 2016, SQL Server 2016 and SQL Server 2017, and the ESU years from the Extended Security Updates FAQ. We keep them, with other dates that matter to owners, on our page of technology deadlines for owners. To see which of them apply to your own software, drop your project files into our stack check; nothing leaves your browser.

What the yearly fee buys, and what it does not

Microsoft calls ESU a last resort and a temporary bridge. Its terms decide whether the fee is even available to a given company.

  • Only security fixes. Windows Server gets updates rated Critical and Important. SQL Server gets only Critical ones, released if and when a flaw is found. No bug fixes, no new features, and no general technical support.
  • Only some editions. For Windows Server 2016, ESU covers Standard and Datacenter. For SQL Server 2016, Enterprise and Standard; Express and Web editions cannot be covered. Small business software often runs on SQL Server Express, where the fee is not an option at all.
  • Only some licenses. Outside Azure, a Windows server qualifies with active Software Assurance, subscription licenses or a hosting provider's license-included service. A license that came preinstalled with the hardware and was never covered by Software Assurance is not on that list. SQL Server without Software Assurance can still get ESU by connecting to Azure Arc and paying as it goes.
  • Two ways to buy. Through commercial licensing, ESU licenses cover one year each, per core, and Year 2 can only be bought after Year 1. Through Azure Arc, the server is connected to Azure and billed monthly; for Windows Server 2016 billing starts on 13 January 2027. Late sign-ups are billed back.
  • Not free in Azure this time. Older versions got ESU at no extra charge on Azure virtual machines. Windows Server 2016 ESU is a paid offering in Azure, and moving SQL Server 2016 to an Azure VM no longer brings free ESU.

On cost, Microsoft's own SQL Server end of support guide puts ESU at approximately 75% of the on-premises license cost each year. Windows Server ESU is priced per core against the license of the product. It buys time, not a solution.

Why it reaches a deal

Three things carry an old server into a deal. First, what runs on it. The general ledger, invoicing, inventory and the owner's weekly reports often live in one database on one server, and they hold the numbers the buyer is paying for. An unpatched server holding them is a finding about the business, not about IT.

Second, the move is rarely only Microsoft's part. The size of the work is decided by the application on top: whether its vendor still exists, whether it supports a newer Windows Server and SQL Server, whether the company paid for the version that does, and how many custom reports, stored procedures, imports and integrations were built around it over the years. A current release of the ERP can mean weeks of planned work; a version its vendor stopped selling can mean a new system. A wider look at old platforms in a target is in An aging platform inside an acquisition target.

Third, timing. A deal signed in late 2026 or in 2027 crosses one of these dates before the buyer's first year is out. Work that has to be done anyway is better priced before closing than found after it.

What a reviewer looks at

A reviewer usually asks a short list of questions, most of them answered from an inventory:

  • The list of servers: every Windows Server and SQL Server instance, with version, edition, patch level and what runs on it. For SQL Server 2016, whether it sits on Service Pack 3, the last one, which ESU requires.
  • The licenses: how the servers are licensed, whether Software Assurance or subscriptions are active, and who holds the agreement. In a carve-out, the licenses and any ESU contract often belong to the parent. That question is covered in Carve-outs and shared systems in due diligence.
  • The application vendors: the support matrix of each key application for newer Windows Server and SQL Server versions, and the company's current maintenance contract with each vendor.
  • The custom layer: reports, scheduled jobs and integrations tied to the old versions, often written by people long gone.
  • Exposure: whether the old servers are reachable from the internet, how remote access works, and whether backups are restored and tested.
  • The plan: ESU bought or budgeted, an upgrade scoped with a date, or nothing yet.

How it turns into deal terms

ESU is a recurring cost with a known end: it belongs in the operating cost the buyer models, and it stops at three years whatever happens. The move is a one-time project of uncertain size, and that uncertainty is what the parties negotiate over.

A hypothetical example: a distribution company runs its ERP on Windows Server 2016 and SQL Server 2016 Standard. ESU is bought, so security fixes continue. But the ERP vendor supports newer SQL Server versions only in a release the company has not licensed, and twelve custom reports depend on the current schema. The fee is a line in the model; the new ERP release and the report rework are the finding.

From there the familiar mechanisms apply: the cost of the move comes off the price, part of the payment is held back until it is done, the seller completes it before closing, or it is disclosed with a plan the buyer accepts. The choice is for the parties and their lawyers. The reviewer's job is to say what is out of support and when, what decides the size of the move, a range of time and cost with its assumptions, and the risk in the meantime. How serious the finding is depends less on the version number than on exposure, on what the server holds and on whether a plan exists.

What a seller can do now

  1. Write down the servers. Version, edition, patch level, license and what runs on each.
  2. Ask each application vendor in writing which Windows Server and SQL Server versions they support, and what it costs to get there.
  3. Decide on ESU early. If the move will not finish before a date, buy coverage on time; joining late means paying back to the start of the term.
  4. Scope the move. A short assessment turns "our server is old" into a scope, a time frame and a range of cost. Keep it separate from whoever will do the work, so the estimate reads as independent.
  5. Put it in the data room. The inventory, the vendor answers, the ESU status and the plan answer the buyer's questions before they are asked.

This is the kind of work our exit readiness program runs month by month.

What a buyer can do

Ask for the server inventory and the license position early, so the cost of ESU and of the move is in the model before the price is. Check the application vendors' support, not only Microsoft's dates. If the integration plan moves the target onto the buyer's infrastructure or licenses, decide who carries ESU through the transition. A red-flag memo early in the process puts it on the table while it can still be priced.

A short checklist

  • Every Windows Server and SQL Server instance, with version, edition and patch level.
  • Which business systems run on each, and who supports them.
  • The license basis of each server, and whether it qualifies for ESU.
  • Application vendor support for newer versions, in writing.
  • Custom reports, jobs and integrations tied to the old versions.
  • ESU bought or budgeted, and until when.
  • A plan for the move with a date, a budget and named people.

Questions

Does our accounting system stop working when Windows Server 2016 loses support?

No. It runs the day after 12 January 2027 as it did the day before. What stops are Microsoft's free security fixes. Any flaw found later stays open unless the company pays for Extended Security Updates, and those run for three years at most, until January 2030.

Can every company buy Extended Security Updates?

No. For Windows Server 2016, Microsoft covers Standard and Datacenter editions with active Software Assurance, subscription licenses or a hosting provider's license-included service. For SQL Server 2016, Enterprise and Standard editions only; Express and Web cannot be covered. A license bought with the hardware and never covered by Software Assurance is not on Microsoft's list.

Is ESU free if we move the servers to Azure?

Not this time. Microsoft states that Windows Server 2016 ESU is a paid offering in Azure, and that moving SQL Server 2016 to an Azure virtual machine no longer brings free ESU. Older versions had that benefit. The fee can be billed monthly through Azure Arc, but it is still a fee.

Is an old Microsoft server a reason to lower the price?

Rarely on its own. The yearly fee is a known operating cost. It becomes a deal point when the move is large and unplanned: the application vendor does not support newer versions, much custom work sits on the old database, or the server is exposed and holds the financial records the buyer relies on.

What should a seller do if the move cannot be finished before the sale?

Buy ESU on time, since joining late means paying back to the start of the term. Then document the move: the inventory, the vendor's written answer on supported versions, a scope with a range of time and cost, and who will do it. A planned finding weakens the seller far less than one the buyer finds.

Written by
Yevhen Borovoi
FounderYevhen Borovoi

Founder of PERETZ, DeZZign, The Structure and NEX, partner at SCHOEFFEL. An engineer by training who reads a business as one system: strategy, product, technology, processes and economics.

Next step

Preparing a sale or looking at a target?

We reply within one business day. NDA before any documents change hands.