Skip to content
All resources
CloudNovember 10, 2026·6 min read

Do You Still Need an On-Site Server?

Windows Server 2016 loses support in January. Before you buy a replacement, work out whether you still need one at all, and be honest about both answers.

By Cohesive Security

There is a box in a cupboard, or under a desk, or in a small room with a noisy fan. It has been there for years, it does something important that nobody can quite articulate, and the only time anyone thinks about it is when it stops.

You are about to have to think about it. Microsoft’s extended support for Windows Server 2016 ends on January 12, 2027, which for a lot of small businesses is the machine in that cupboard. After that date, newly discovered flaws in it stay open permanently.

The usual reflex is to price a replacement server. Before you do, it is worth asking whether you need one, because for a meaningful share of businesses the honest answer is no, and for another meaningful share the honest answer is yes. Anyone who tells you there is only one right answer is selling something.

Key takeaways:

  • The forcing date is January 12, 2027. Plan around it now, because a rushed migration in December is how data gets lost.
  • Start with an inventory of what the server actually does. Most of them are running two or three things, and one of those is the reason you still have it.
  • File shares and email have mostly stopped justifying a server. Line-of-business applications and large-file workflows often still do.
  • Moving to cloud does not remove the backup problem. It relocates it.

First, find out what it actually does

You cannot make this decision from the outside. Before pricing anything, write down what is genuinely running on that machine.

In most small businesses the list is short and looks something like this: a file share, possibly a domain controller handling logins, a line-of-business application with its database, print services, and something somebody set up in 2019 that nobody has dared touch since.

Then, for each one, two questions. Who uses it, and what happens if it is gone on Monday? You will usually find one item on the list is the real reason the server exists, and everything else is habit.

When moving off makes obvious sense

File shares. This is the one that has genuinely changed. If the server exists mainly so people have a shared drive, that job is now done well by SharePoint or OneDrive, which you may already be paying for. Check what your Microsoft 365 licensing already includes before you buy anything.

Logins and identity. If the server is a domain controller keeping track of who can sign in to what, and your applications are mostly cloud now, that role can usually move to cloud identity instead. This is often the single change that lets the box go away entirely.

Remote access. If the server exists so people can reach the office from home, that need is better met other ways now, and the remote access route into a server is one of the more commonly attacked doors on a small network.

Your team is already distributed. If half the company works somewhere else half the time, a machine that only performs well inside one building is fighting your working pattern.

When keeping one is still the right call

This is the half that gets left out of most articles on this topic, usually because the person writing sells cloud.

A line-of-business application that has no cloud version. Plenty of specialist software (practice management, machine control, engineering, older accounting packages) still expects a local server, and forcing it into the cloud can mean paying more for something slower. If the vendor has no cloud option, that decides it.

Large files, constantly. CAD, video, imaging, large design files. Working on a fifty-gigabyte file across an internet connection is a materially worse experience than working on it across the room. Some workflows are genuinely faster local, and pretending otherwise leads to a team that hates the new setup.

Your internet is the weak link. Moving everything to cloud makes your connection a single point of failure. If your building has one unreliable line and no realistic second option, understand that you are trading a risk you control for one you do not.

Equipment that expects it. Manufacturing, labs, and medical practices often have machines that talk to a local server by design and will not be re-engineered. That is its own conversation about keeping that equipment separated rather than about moving it.

The answer most businesses actually land on

Not all-or-nothing. In practice the common outcome is: the file share and identity move to cloud, and one much smaller server stays for the application that needs it.

That is a good outcome. The box gets smaller and cheaper, the things most exposed to the internet stop living on it, and the remaining machine has one job, which makes it far easier to secure and to replace next time.

If you do keep a server, replace the operating system rather than nursing it. A supported version buys you years of patches, and running an unsupported server on a network is exactly the finding that fails a client security questionnaire or an insurance renewal.

The costs both sides forget

Cloud is a subscription, so the sticker price looks smaller than a capital purchase. Compare properly: per-user licensing over five years, any storage above what is included, and the one-off cost of moving.

Keeping a server is a capital purchase, so it looks like one number. Compare properly there too: the hardware, the operating system licensing, the backup for it, the electricity, and the fact that in five to seven years you will do this again.

The cost nobody puts in either column is the migration itself. Moving file shares means permissions get rebuilt, and permissions are where these projects go wrong: everyone can see everything, or the wrong person can see payroll. Budget attention for that, not just money.

And whichever way you go, this does not solve backup. A cloud file store replicates your data, which is not the same as being able to put a folder back the way it looked three weeks ago. We covered why that distinction matters, and it applies just as much after a migration as before. Backup stays a separate line item, which is what our backup and recovery service is for.

How to approach the next two months

If that server is running Windows Server 2016, you have a deadline and you should use it rather than let it use you.

Inventory what the machine does. Decide, per item, whether it moves or stays. Get quotes for both paths so you are comparing real numbers. Then schedule the work for a quiet week, not the week before the deadline, and make sure you have a tested backup before anybody starts.

This is the kind of decision worth an outside opinion, partly because it is expensive to get wrong and partly because most of the advice available is attached to someone’s product. We will tell you when keeping a server is the better call, because sometimes it is. That is part of a free assessment, and the migration itself is what our cloud and infrastructure work covers. Or email hello@cohesivesecurity.com with what your server currently runs and we will tell you which parts could go.

#cloud#Windows Server#infrastructure#migration#backup

Enjoyed this article?

Get more like it by email. Short, practical security tips for business owners. No jargon, no spam, unsubscribe anytime.

We only use your email to send the tips. Nothing else, and never shared.

Want help putting this into practice?

Our team can assess your environment and handle the heavy lifting. Start with a free, no-pressure conversation.