Last year, everybody was focused on Windows 10. That made sense. It was sitting on every desk in the building and the deadline was impossible to ignore. But while everyone was busy swapping out laptops, a quieter set of deadlines has been working its way through the equipment in the server closet, and these are a lot harder to fix in a weekend.
Windows Server 2016 loses support on January 12, 2027.
If that sounds comfortably far off, it isn't. A server migration is not a laptop refresh. You have applications with dependencies nobody documented, a line of business system whose vendor may or may not support the newer OS yet, and a cutover window that has to happen when the business isn't running. Five or six months is a reasonable timeline for this. Five or six weeks is a bad one.
Most of the businesses we walk into are not dealing with a single aging server. They're dealing with a stack of them, and the Microsoft lifecycle has been quietly clearing the shelf:
Windows Server 2012 and 2012 R2, for what it's worth, went dark back in October 2023, and we still find them running in production. If you have a domain controller, a file server, and a line of business app server that all went in around the same time, there's a decent chance more than one of these applies to you.
Nothing. That's the trap.
The server boots up like it always does. Nobody notices anything. What you've actually lost is the flow of security updates, and the gap builds quietly until somebody publishes an exploit for a hole that will never be patched. Unsupported servers don't fail on the deadline. They fail eight months later, at two in the morning, in a way that costs considerably more to sort out.
The other half of it is paperwork, and this is the part that catches people off guard. The question "do you run any unsupported or end of life operating systems?" now shows up on:
You can be running along perfectly well and still fail a review because of one box in the corner nobody has looked at in years.
Every server on your list lands in one of these buckets. The work is deciding which one.
Upgrade the OS, and probably the hardware with it.
If the machine went in around 2016 or 2017, it is out of warranty and near the end of its useful life anyway. Replacing the hardware and moving to Windows Server 2022 or 2025 is the straightforward path, and it's usually the right call for domain controllers and file servers you genuinely need on site.
Move the workload to the cloud.
File shares move to SharePoint or OneDrive, mail moves to Microsoft 365 (if you're still on Exchange, this is almost certainly where you're headed), and application servers can go to Azure. This trades a capital purchase for a monthly bill, which some owners like and some don't. It also means you're not doing this same exercise again in 2032.
Buy Extended Security Updates as a bridge.
Microsoft sells ESU for SQL Server 2016 through volume licensing, covering critical patches for up to three years past the end date. It's a real option, but treat it as what it is: rented time while you do the actual migration. It is not a plan on its own, and the price climbs each year you extend.
Retire the application entirely.
Sometimes the only reason a 2016 server still exists is one piece of software that three people use twice a year. Worth asking that question before you spend money moving it somewhere new.
Before you call anyone, including us, it helps to know the shape of the problem. A few things you can check yourself:
Nobody publishes real numbers on this, so here's a rough shape based on what we see with businesses in the ten to seventy-five employee range.
A single replacement server, properly specced with redundant storage, plus Windows Server licensing and client access licenses, plus the labor to migrate roles and data across, generally lands somewhere in the five figures once you account for everything. Two or three servers and you're planning a real capital expense. Moving the same workloads to Microsoft 365 and Azure instead usually means little or no hardware, a higher monthly bill, and a project cost that depends almost entirely on how messy the data is.
The variable that moves the number most isn't the hardware. It's the applications. A file server migration is predictable. An ERP or a shop floor system with a database behind it and a vendor who wants to be involved is where timelines stretch and budgets move. That's the first thing to scope, not the last.
The one cost people forget to compare against is doing nothing: a higher insurance premium, a failed vendor security review, or an incident on an unpatched box. Those aren't hypothetical line items anymore.
Two reasons. The first is budget. If you're setting next year's numbers this fall, server replacement is a line item you want in there deliberately rather than as an emergency in the middle of the year.
The second is lead time. Hardware takes weeks. Coordinating with application vendors takes longer. And the migration itself should happen in stages, one workload at a time, with a rollback plan, during evenings and weekends. The businesses that started early on the Windows 10 side had a calm project. The ones that waited had a scramble the month before and paid for it in overtime and rushed decisions.
You've got about five months. That's enough to do this properly if you start now, and not much more than that.
If you're not sure what's in your server closet or what it's costing you to keep it there, that's the first conversation. We'll do a straightforward inventory: what you're running, what's already out of support, what each option would cost, and a sequence that doesn't take the business offline. No pressure to buy hardware on the spot.
We're based in Murray and we work with businesses across Salt Lake County and the Wasatch Front. If your servers are getting up there in years, let's take a look while there's still time to plan rather than react.
We inventory what you are running, flag what is already out of support, price each option, and sequence a migration that keeps the business online. Start with a free, no-pressure assessment.
Get a Free IT Assessment