Put January 2027 on the wall now

Windows Server 2016 extended support ends January 12, 2027. After that: no security patches without paying for Extended Security Updates, which cost real money in year one and multiply after.

Thirteen months out is when this work is cheap. Count what a migration actually needs: inventory the 2016 fleet (a week), classify what upgrades in place versus what needs an application move (two weeks), then the long tail of the applications themselves. The servers were never the problem. The problem is the app on four of them whose vendor went out of business in 2019.

The checklist, short version:

1. Count the 2016 boxes today. The number is bigger than the CMDB says. It always is.
2. Sort into three piles: upgrade in place, replatform the app, retire. Every box goes in a pile, and "unknown" is a pile that gets two weeks to empty itself, not a resting place.
3. Price the ESU fallback now, per box, from the lifecycle page, so the January 2027 conversation is arithmetic instead of panic.
4. Schedule the retirements first. Every box in pile three is budget you get back before the hard work starts.

The wall calendar matters more than the plan document. Teams hit dates they can see from their desks. January 12, 2027, big letters, by the coffee. We are not joking. It works.