Windows Server 2016 to 2025 migration is the move most UK businesses should now make in one jump rather than two. Support for the 2016 release ends on 12 January 2027, and the servers it affects will give you no warning: they keep serving files, applications and logins while the security updates that make them safe to run quietly stop arriving. The deadline is fixed; the only real decision left is which route you take off the platform.
This Windows Server 2016 to 2025 migration guide covers the whole journey: why Windows Server 2025 is the right landing zone, the lifecycle dates driving the project, how the realistic routes compare, the hardware and licensing checks that catch teams out, and a cutover-weekend runbook. If you want the compliance and insurance picture first, read our companion Windows Server 2016 end of support risk guide, then come back here for the how.
Table of contents
- Why a Windows Server 2016 to 2025 Migration Beats a Two-Step Upgrade
- Support Deadlines: The Clock Behind the Move
- Windows Server 2016 to 2025 Migration Paths Compared
- Hardware and Licensing Checks Before You Commit
- Planning Your Windows Server 2016 to 2025 Migration
- Route 1: The Direct In-Place Upgrade
- Route 2: Clean Install and Role Migration
- Cutover Weekend: A Step-by-Step Runbook
- Windows Server 2016 to 2025 Migration Costs
- Common Windows Server 2016 to 2025 Migration Mistakes
- Windows Server 2016 to 2025 Migration FAQ
- References
Why a Windows Server 2016 to 2025 Migration Beats a Two-Step Upgrade
When a deadline is close, moving to Windows Server 2019 or 2022 can feel like the smaller, safer step. It is usually the more expensive one. The project work — discovery, application testing, licensing, cutover, decommissioning — costs roughly the same whichever version you land on, but the older targets hand back far less supported life in return. Choose 2019 and you will run the entire exercise again within three years; a Windows Server 2016 to 2025 migration does it once.
The runway problem with 2019 and 2022
Windows Server 2019 leaves extended support on 9 January 2029, and Windows Server 2022 follows on 14 October 2031. A team that finishes a move to 2019 in late 2026 gets roughly 29 months before it is back where it started. A Windows Server 2016 to 2025 migration completed on the same schedule buys about eight years of patches for the same project cost — the arithmetic is not close.
What Windows Server 2025 actually adds
Windows Server 2025 is not just a longer support clock. Hotpatching lets you install many security updates without a reboot, cutting the maintenance windows that make server estates painful to patch. Active Directory gains a larger 32k database page size and better scalability, SMB over QUIC improves secure remote file access, and storage performance on NVMe hardware is significantly higher. Microsoft’s What’s New in Windows Server 2025 page lists the full set.
Support Deadlines: The Clock Behind the Move
Lifecycle dates are the fixed points every plan has to fit around. Four of them matter here.
| Version | Extended support ends | What that means in practice |
|---|---|---|
| Windows Server 2016 | 12 January 2027 | Final free security update ships; the platform is retired |
| Windows Server 2019 | 9 January 2029 | Barely two years of runway left for a new landing zone |
| Windows Server 2022 | 14 October 2031 | A middle option that still repeats the project sooner |
| Windows Server 2025 | 10 October 2034 | Released 1 November 2024; mainstream support to 9 October 2029 |
Reading the runway
From mid-August 2026 the arithmetic is stark: about 5 months of support remain on 2016, 29 on 2019, 62 on 2022 and 98 on 2025. Every month of delay comes off the front of the Windows Server 2016 to 2025 migration window, not the back — procurement, testing and the December change freeze all still have to fit before January 2027.
Windows Server 2016 to 2025 Migration Paths Compared
Every Windows Server 2016 to 2025 migration takes one of three realistic routes off the old platform, and most estates end up using a mix: an in-place upgrade for well-behaved application servers, a clean build for anything identity-related, and a move to the cloud for workloads that no longer justify their own hardware.
| Factor | In-place upgrade | Clean install + role migration | Rehost in Azure |
|---|---|---|---|
| Service interruption | 60–90 minutes per server | Minutes at cutover, work spread over weeks | Depends on bandwidth and replication |
| Carries old problems across | Yes — config drift comes too | No — fresh OS, clean baseline | Only if you lift and shift as-is |
| Needs new hardware | No, if CPU passes the flag check | Usually yes, or reuse via virtualisation | No — hardware problem disappears |
| Best for | Healthy single-role application servers | Domain controllers, file servers, drifted estates | Ageing hardware, variable workloads |
How to choose quickly
Ask two questions of every server in the Windows Server 2016 to 2025 migration scope. Is the operating system healthy, with a vendor-supported application on hardware that passes the 2025 checks? In-place upgrade. Is it a domain controller, a file server, or a box nobody fully understands? Build clean and migrate the role. Servers with failing hardware or spiky workloads belong in the cloud conversation instead — our end-of-support guide compares the Azure route in more detail.
Hardware and Licensing Checks Before You Commit
More Windows Server 2016 to 2025 migration projects stall on a processor flag or a licence count than on any technical step in the migration itself. Run these checks in week one, before any route is chosen.
The CPU-flag trap
Windows Server 2025 requires a 64-bit processor that supports the POPCNT and SSE4.2 instructions, and Setup enforces the requirement. Most CPUs made after about 2010 pass, but the eight-to-ten-year-old hosts typically still running 2016 are exactly where exceptions surface. Check with Microsoft’s Coreinfo utility or the vendor’s specification sheet before promising an in-place upgrade; the full list is on the Windows Server hardware requirements page.
| Requirement | Minimum for Windows Server 2025 | Notes |
|---|---|---|
| Processor | 1.4 GHz 64-bit with POPCNT and SSE4.2 | Hard requirement — Setup blocks without it |
| Memory | 512 MB (2 GB with Desktop Experience) | Plan 16 GB+ for real workloads |
| Storage | 32 GB minimum system disk | In-place upgrades need substantial free space as well |
| TPM 2.0 | Needed for BitLocker and hardening features | Not a hard Setup block, but expected on new builds |
Licensing in 2025 terms
Licensing is where a Windows Server 2016 to 2025 migration budget most often slips. Windows Server licensing remains core-based: a minimum of 8 core licences per processor and 16 per server, with Standard edition covering two virtual machines and Datacenter covering unlimited VMs on a licensed host. Existing 2016 CALs do not carry over — users and devices need 2025 CALs. New in this generation is a pay-as-you-go subscription option through Azure Arc, which also unlocks hotpatching. Budget from Microsoft’s Windows Server pricing page rather than a reseller quote from memory.
Planning Your Windows Server 2016 to 2025 Migration
The planning fortnight of a Windows Server 2016 to 2025 migration decides whether cutover weekend is boring or memorable. Three workstreams run in parallel.
Inventory and dependency map
List every 2016 instance — physical, virtual and hosted — with its roles, applications, data, owners and the systems that depend on it. Estates that have grown by acquisition often hide a server nobody admits to owning; a server management partner can run discovery tooling if internal records are thin. Two findings change the plan materially: domains upgraded from Windows Server 2003 may still replicate SYSVOL with FRS, which must move to DFSR before any 2025 domain controller joins, and hosts also running SQL Server 2016 need their own remediation since its support ended in July 2026.
Application compatibility
For every line-of-business application, get the vendor’s supported-platform statement for Windows Server 2025 in writing, then prove it in a test virtual machine — a snapshot of the production server upgraded in an isolated network is the cheapest rehearsal you will ever run. Applications with no 2025 support statement become the critical path of the whole Windows Server 2016 to 2025 migration, and the earlier you find them the more options you have.
Backup, rollback and the change freeze
Every route in a Windows Server 2016 to 2025 migration assumes you can go backwards. Take full image backups before each cutover, test-restore at least one of them, and write the rollback decision point into the runbook: who calls it, at what time, on what evidence. Then check the calendar — most UK businesses freeze changes in December, so a January 2027 deadline really means finishing by the end of November 2026.
Route 1: The Direct In-Place Upgrade
Windows Server 2025 accepts in-place upgrades from up to four versions back — 2012 R2, 2016, 2019 and 2022 — so a single-hop Windows Server 2016 to 2025 migration is fully supported on hardware that passes the checks above. Microsoft documents the procedure in its in-place upgrade guide.
Prerequisites that decide success
Before running Setup: current firmware and storage drivers, at least 40 GB free on the system volume, third-party antivirus and backup filter drivers removed or updated to 2025-aware versions, Windows Update fully current, and a verified image backup. Skipping the driver step is the single most common cause of a failed upgrade.
The upgrade sequence
Mount the 2025 ISO, run setup.exe, choose to keep files and applications, supply the new licence key and let the server reboot through the upgrade phases. Plan for 60 to 90 minutes of interruption per server, and upgrade one representative server per application tier before committing the rest of the estate.
When not to upgrade in place
Never in-place upgrade a domain controller, a server that fails the CPU-flag check, or a box carrying years of configuration drift, orphaned software and mystery scheduled tasks. An upgrade faithfully preserves problems along with data — a clean build is how you finally shed them.
Route 2: Clean Install and Role Migration
The clean-install route of a Windows Server 2016 to 2025 migration builds new 2025 machines alongside the old estate and moves each role across with its own native tooling, then retires the 2016 boxes once nothing depends on them.
| Role | Migration method | Key caution |
|---|---|---|
| Active Directory | Promote new 2025 DCs, transfer FSMO roles, demote old | Forest functional level must be 2016+; FRS must be gone |
| File services | Storage Migration Service in Windows Admin Center | Cutover adopts the old name and IP — sequence it last |
| DHCP and DNS | Export/import scopes; AD-integrated zones replicate | Update helpers and reservations pointing at old servers |
| Hyper-V guests | Build new 2025 hosts, live-migrate or re-import VMs | Check configuration versions before upgrading them |
| Applications and SQL | Fresh install on 2025, restore data, repoint clients | Vendor support statement first; SQL 2016 needs its own plan |
Domain controllers: build new, never upgrade
Promote fresh Windows Server 2025 domain controllers into the existing domain, let replication settle, transfer the FSMO roles, repoint anything with a hard-coded DNS entry, then demote and remove the 2016 controllers. Microsoft’s domain controller upgrade guidance covers the sequence, and it requires a forest functional level of Windows Server 2016 or higher — which a native 2016 domain already meets.
File servers: Storage Migration Service
The Storage Migration Service inventories the old server, transfers files with permissions and shares intact, then cuts over the server’s identity so the new machine adopts the old name and IP address. Users and mapped drives notice nothing, which makes it the lowest-drama step of the whole Windows Server 2016 to 2025 migration — provided it runs after every other role has left the box.
DHCP, print and everything else
DHCP scopes export and import cleanly with PowerShell, AD-integrated DNS zones replicate to the new controllers automatically, and print queues move with the Print Management console. What remains is the application tail: each one gets a fresh install on 2025, a data restore and a client repoint, in an order set by the dependency map from the planning phase.
Cutover Weekend: A Step-by-Step Runbook
However carefully each server route was chosen, a Windows Server 2016 to 2025 migration ends in one coordinated estate-level sequence.
Two weeks out
Confirm every backup has a tested restore, every application owner has signed off their test result, and licences and CALs are purchased and recorded. Send the user-facing downtime notice, book the engineers, and walk the runbook end to end in a tabletop rehearsal — every step should name an owner, a duration and a rollback trigger.
Cutover night
Freeze changes, take final backups, then work the sequence: infrastructure roles first (domain controllers should already be done), application servers next, the file-server identity cutover last. Verify each service against a written checklist — logins, shares, printing, the line-of-business applications, backup agents — before declaring it complete. If a step blows its time box, roll it back and continue with the rest; a Windows Server 2016 to 2025 migration survives a postponed server, but not an unplanned Monday outage.
The week after
Keep the old servers powered off but intact for an agreed soak period, monitor event logs and helpdesk volume, then decommission: remove stale DNS records, retire monitoring entries, cancel maintenance contracts and wipe the disks. The project is finished when the old estate is gone, not when the new one boots.
Windows Server 2016 to 2025 Migration Costs
Windows Server 2016 to 2025 migration budgets fail in predictable places, and almost never on the licence line alone.
Licence list prices
Microsoft’s list price for Windows Server 2025 Standard is $1,176 for a 16-core licence, and $6,771 for Datacenter — roughly £925 and £5,330 at typical exchange rates, before UK reseller and volume-licensing adjustments. CALs for users or devices are extra, and the Azure Arc pay-as-you-go subscription trades capital cost for a monthly meter.
The full project budget
The licence is often the smallest line. Add engineer time for discovery, testing and cutover; application vendor fees for re-certification or new versions; replacement hardware where the CPU-flag check fails; and a contingency for the server that turns out to matter more than anyone recorded. Weigh the total against the cost of staying put — Extended Security Updates escalate in price every year and buy no new capability, as our end-of-support guide sets out. A managed IT services partner can price the whole programme as a fixed-scope project if you would rather not build the plan internally.
Common Windows Server 2016 to 2025 Migration Mistakes
The same Windows Server 2016 to 2025 migration failures appear in post-incident reviews again and again. All four are avoidable in the planning fortnight.
Upgrading domain controllers in place
It sometimes works, which is exactly why it keeps being tried. When it goes wrong it takes authentication down with it, and the recovery is a directory restore under pressure. Build new controllers and transfer roles — the supported path costs an afternoon, not a weekend.
Testing the operating system but not the applications
A server that boots cleanly on 2025 proves nothing about the twelve-year-old finance package it hosts. Application-owner sign-off against a written test script is the acceptance test that matters; treating OS-level success as project success is how cutover weekend acquires a Monday morning.
Leaving licensing until after cutover
Running unlicensed while procurement catches up undermines the compliance position the project was meant to fix — an unsupported or unlicensed estate quietly weakens your cybersecurity and audit posture either way. Order licences and CALs when the plan is signed off, not when the invoices are chased.
Trusting a backup nobody has restored
The rollback plan is only as real as the last successful test restore. One restore rehearsal per platform type, timed and documented, turns the riskiest assumption in the runbook into a known quantity.
Windows Server 2016 to 2025 Migration FAQ
Can you upgrade directly from Windows Server 2016 to Windows Server 2025?
Yes. Windows Server 2025 supports in-place upgrades from up to four versions back, which includes 2016. The hardware must pass the POPCNT and SSE4.2 processor check, and domain controllers should be migrated by promoting new servers rather than upgraded in place.
How long does a Windows Server 2016 to 2025 migration take?
A small estate of five to ten servers typically takes four to six weeks from discovery to decommissioning, with most of that time in application testing rather than the moves themselves. Each in-place upgrade needs 60 to 90 minutes of downtime; each clean-install role cutover needs minutes.
Do our existing CALs work with Windows Server 2025?
No. Client access licences are version-specific, so 2016 CALs do not cover access to 2025 servers. Budget new user or device CALs alongside the server licences, or consider the Azure Arc subscription model where CALs are handled differently.
Should we move to Windows Server 2022 instead?
Only if a critical application is not yet supported on 2025. You would be landing on a platform with just over five years of extended support left, against more than eight for 2025, for essentially the same Windows Server 2016 to 2025 migration effort.
What happens if we miss the January 2027 deadline?
The servers keep running but stop receiving security fixes, and every later Microsoft patch becomes a public roadmap for attacking your estate. Extended Security Updates can buy up to three increasingly expensive years, and strict network isolation is the only other mitigation — both are stopgaps, not strategies.
References
Windows Server 2016 Lifecycle — Microsoft Learn
Windows Server 2025 Lifecycle — Microsoft Learn
Plan Your Windows Server Upgrade Path — Microsoft Learn
Perform an In-Place Upgrade of Windows Server — Microsoft Learn
Hardware Requirements for Windows Server — Microsoft Learn
What’s New in Windows Server 2025 — Microsoft Learn
Storage Migration Service Overview — Microsoft Learn
Upgrade Domain Controllers to a Newer Version — Microsoft Learn
