# 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

## Four paths

- **Upgrade to Windows Server 2025**: When the server must stay in your office or data centre. – https://ithink.lt/en/it-support-services/infrastructure-management/
- **Move to Azure**: Servers in the cloud, no hardware refresh. – https://ithink.lt/en/cloud-migration/azure/
- **Replace with Microsoft 365**: Files, e-mail and users – no server needed. – https://ithink.lt/en/cloud-migration/microsoft-365/
- **ESU as a bridge**: Paid security updates for up to 3 years while you finish migrating.

## 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

| Phase | Duration |
|---|---|
| Readiness assessment | 1–2 weeks |
| Decision and plan | About 1 week |
| Migration | 2–8 weeks, depending on the number of servers |
| Buffer before 12 Jan 2027 | The 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.

**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.

---
Source: https://ithink.lt/en/cloud-migration/windows-server-2016/ · Updated 2026-09-28
