Windows Server 2016 Migration

When does Windows Server 2016 support end?

Extended support for Windows Server 2016 ends on 12 January 2027. The Microsoft Lifecycle page gives this date for the Datacenter, Standard, Essentials and MultiPoint Premium editions alike; mainstream support already ended in January 2022. After that date, Microsoft will release no further security updates for this version.

An unpatched server does not fall over on day one. The problem is that every vulnerability published in the months that follow stays open on it. There is a compatibility side as well: new application versions, backup agents and security software drop unsupported operating systems from their lists over time. If data covered by KVKK, Türkiye’s Personal Data Protection Law (Law No. 6698), lives on these servers, an out-of-date system is also hard to defend in terms of technical measures.

Can you buy Extended Security Updates (ESU) for Windows Server 2016?

At the time this page was last updated, Microsoft’s Extended Security Updates overview lists an ESU programme only for Windows Server 2012 and 2012 R2; it contains no published ESU terms for Windows Server 2016. For that reason we do not recommend building your migration plan around ESU.

If Microsoft announces an ESU option for this version, we will check the terms on the official page and pass them on to you. Even so, ESU is by definition a temporary bridge, offered as a last resort and with no new features. The real job is still moving the servers to a supported version.

In-place upgrade or migration to a new server?

If the hardware is current and the roles support it, an in-place upgrade is the quick route; if the hardware is old, or the server has built up years of tangled configuration, migrating to a new server gives a cleaner result. According to Microsoft’s upgrade paths page, an in-place upgrade from Windows Server 2016 directly to 2019, 2022 or 2025 is supported using installation media.

The same page spells out the limits of an in-place upgrade: you cannot change the language, you cannot switch between Server Core and Desktop Experience, NIC Teaming must be disabled before upgrading, and every new version needs its own licence. On failover clusters, a cluster OS rolling upgrade can move only one version at a time. Whichever route we take, we start with a full backup.

• In-place upgrade: same hardware, settings kept, downtime roughly the length of a reboot
• Migration to a new server: new hardware or VM, role-by-role move, clean build
• Move to Azure: the virtual machine is moved into Azure under your own subscription

How do you migrate domain controllers, file servers and applications?

Rather than upgrading domain controllers in place, we prefer to add a new DC on the new version, transfer the FSMO roles, confirm that replication is healthy and only then demote the old DC cleanly. DNS, DHCP and Group Policy are checked along the way; we cover the details on the Active Directory and Entra ID page.

For file servers, Microsoft’s Storage Migration Service handles inventory, transfer and an optional cutover. When the destination server takes over the old server’s name and IP address, users’ mapped drives keep working without any changes. For application servers, we first confirm that the vendor supports the new operating system and, where necessary, install the application cleanly on a new server and move the data across.

Watch the licensing on Remote Desktop servers: according to the RDS CAL compatibility table, Windows Server 2016 CALs cannot be used to connect to session hosts running Windows Server 2019 or later. We cover this separately on the RDS and CAL licensing page.

Is migrating from Windows Server 2016 to Azure a good idea?

Azure is a sensible option if your server hardware has reached end of life and the workloads suit the cloud, but not for every workload. For latency-sensitive local applications, heavy file access from branch offices, or offices where a single internet line is the weak point, an on-premises server may still be the better fit.

For an Azure migration, we create and configure the subscription and resources on your behalf; the servers run in your own subscription. We prepare the plan, including network connectivity, backup and cost monitoring, as part of Azure and AWS setup and migration.

How long does a Windows Server 2016 migration take?

It depends on the number of servers and how complex the roles are: a single file server can be moved in a few days, an environment with several DCs and application servers in a few weeks. The longest part of a migration is usually not the technical work but getting sign-off from the application vendor and lining up users for testing.

Consider a three-server setup: one DC, one file server and an ERP system running on SQL Server. In a typical plan the new DC is added first, the file server is moved over a weekend, and the ERP goes last, after vendor approval and a round of testing. As 12 January 2027 approaches, both your calendar and your vendors’ will fill up, so we recommend planning now. We review your current setup free of charge and produce a written migration schedule.

What you receive

• Inventory of Windows Server 2016 servers and roles
• Per-server choice of method (in-place upgrade, migration or Azure) and a timeline
• DCs, file servers and application servers moved to the new version
• Full pre-migration backup and rollback plan
• Safe decommissioning of the old servers
• Updated network, role and licensing documentation

How we work

1. 1

   Inventory

   We list every server running Windows Server 2016, its roles and the applications that depend on it.

2. 2

   Method and timeline

   For each server we choose between in-place upgrade, migration to a new server or Azure, and draw up the schedule.

3. 3

   Preparation

   We take full backups and confirm licensing and application vendor support.

4. 4

   Migration

   We move roles in order and test with users and applications after each step.

5. 5

   Close-out

   We decommission the old servers and connect monitoring and backup to the new ones.

Frequently asked questions