Identify the exact edition first
Microsoft states that standard support for Windows 10 22H2 ended on October 14, 2025. LTSC and LTSB editions can have different lifecycles, while eligible ESU enrollment is a separate consideration. Do not decide solely from the statement that a machine runs Windows 10. Check its edition, purpose and support status. ESU is not equivalent to full product support; verify the current scope of the applicable program.
Technical source: Microsoft Learn — Windows 10 release information
Map business dependencies before counting devices
An inventory needs software details as well as processor and memory information. Accounting software, printer drivers, barcode readers or older production equipment can affect the schedule. Test the assumption that a new computer will solve everything before purchasing. A list connecting each device to a business process and the people affected by failure makes prioritization much easier.
Define distinct migration paths
A compatible device may need an upgrade, unsuitable hardware may need replacement, and a system with special dependencies may need a temporary plan. Treat these as separate groups instead of one mass change. Every temporarily retained system should have an owner, review date and target resolution. Open-ended exceptions tend to make the same problem larger at the next refresh cycle.
Test a full working day in a small pilot
A test computer booting successfully is not enough. Check user files, email access, printing, meetings and critical applications together. Include people from different departments. Record issues with the application, version, operation and time rather than simply noting that something does not work. Clarify rollback conditions and the usability of backups before expanding deployment.
Assess costs alongside disruption
Replacing a device involves more than its purchase price: setup, employee time, data migration and secure retirement of the old machine also matter. Agree on suitable change windows with departments. At handover, verify the supported operating system, working applications, user access and updated inventory. A regular refresh schedule helps prevent the next support deadline from becoming another urgent project.