Deadline: 12 January 2027

Windows Server 2016 end of support: what to do now

Microsoft ends security updates for Windows Server 2016 on 12 January 2027. After that date your servers become more exposed every month. We help you choose the right path and migrate in time – without downtime.

End of support
12 Jan 2027
Microsoft recommends
Windows Server 2025
Bridge
ESU for up to 3 years
First step
Server inventory

How we work

  1. Inventory

    We find every Windows Server 2016 server, its roles and applications.

  2. Choosing a path

    For each server: Windows Server 2025, Azure, Microsoft 365, or ESU as a bridge.

  3. Plan and budget

    Sequence, cost and timeline up to 12 Jan 2027, with time left for testing.

  4. Delivery

    Migration at agreed times, without downtime, followed by ongoing management.

What you get

A server list

Every Windows Server 2016 server, its roles and risks.

A path for each server

A reasoned recommendation: upgrade, move or replace.

A cost and timeline plan

What happens when and at what cost – before support ends.

A completed migration

No unsupported servers left, and the environment documented.

Indicative timeline

PhaseDuration
Readiness assessment1–2 weeks
Decision and planAbout 1 week
Migration2–8 weeks, depending on the number of servers
Buffer before 12 Jan 2027The earlier you start, the more time is left for testing

Durations are indicative – you get an exact plan and dates in the proposal, after we have assessed your environment.

What we need from you

To keep things moving, please have ready:

  • a server list (if you have one) and admin access;
  • your application vendors’ contacts – do their apps support a newer Windows Server or the cloud?
  • details of your licences (e.g. Software Assurance, CALs);
  • a decision-maker and budget expectations;
  • agreed times for the work.

A typical project: three servers, three paths

Situation

The company ran three Windows Server 2016 servers: a domain controller, a file server and a server hosting its production accounting software.

What we do

We moved users to Entra ID and files to SharePoint, and upgraded the production software server to Windows Server 2025 because the vendor didn’t support the cloud.

Result

No unsupported server remained before the deadline, and two of the three servers no longer need looking after.

A composite example based on our most common projects.

Frequently asked questions

What happens after 12 January 2027?

Servers keep running, but get no more security updates or Microsoft support – the risk grows every month.

Can we buy extra security updates?

Yes, Microsoft offers Extended Security Updates (ESU) for up to three years. It’s a temporary bridge while you migrate.

How long does a migration take?

It depends on the number of servers and applications – which is why it pays to start with an assessment now.

Can we simply upgrade the existing server?

Sometimes – Windows Server 2025 supports an in-place upgrade. But older hardware often no longer meets the requirements, so the assessment checks hardware and application compatibility.

Get a readiness assessment

Number of users
More details (optional) – for a more accurate proposal
Current e-mail systems · select all that apply
Where are your files? · select all that apply
User management · select all that apply
You’ll get a written proposal by the next business day.
  • Microsoft partner
  • Lenovo Gold Partner
  • Scoris Business Excellence Award 2026
  • 433+ companies served
  • Since 2005
CallGet a proposal

Choose which cookies you allow. You can change your choice at any time.

Strictly necessary

Needed for the site to work securely and remember your choices (e.g. cookie settings or text typed into a form). They cannot be switched off and need no consent.

Always on
Cookies (3)
  • ithink-consent · IThink (localStorage)
    Stores your cookie choice and an anonymous consent ID. Expires: 12 months.
  • ithink-form:* · IThink (sessionStorage)
    Keeps the text you type into a form so you don’t lose it while filling in a request. Expires: Until the browser tab is closed or the form is sent.
  • __cf_bm, cf_clearance · Cloudflare
    Protection against bots and attacks (set only when needed). Expires: 30 minutes.

Analytics

Help us understand how visitors use the site (Google Analytics 4) so we can improve it. Data is aggregated and IP addresses are not stored.

Cookies (3)
  • ithink-utm, ithink-landing · IThink (sessionStorage)
    Adds the campaign source and first page visited to your request. Expires: Until the browser tab is closed.
  • _ga · Google Analytics 4
    Distinguishes visitors for visit statistics. Expires: 2 years.
  • _ga_8EFLVCZYDP · Google Analytics 4
    Keeps the state of your visit (session). Expires: 2 years.

Marketing

Let us measure the effectiveness of our Google Ads advertising and show you more relevant ads.

Cookies (2)
  • _gcl_au · Google Ads
    Measures whether an ad led to a visit and a request. Expires: 90 days.
  • IDE, test_cookie · Google (doubleclick.net)
    Ad delivery and measurement on Google networks. Expires: Up to 13 months (test_cookie – 15 minutes).

Cookie policy · Privacy policy

Privacy policy

Loading…