Planning your business move from Windows 10
Inventory Windows editions, check upgrade compatibility and use eligible extended security updates only as a planned bridge to a supported setup.

A computer can keep running after its operating system’s standard support ends. That doesn’t tell you whether it still receives the security updates your business needs.
For Windows 10 devices, identify the edition and version, check the support arrangement and decide how each computer will move to a supported setup. A list of models and purchase dates isn’t enough.
Check which Windows edition you have
Standard support for Windows 10 version 22H2 ended on October 14, 2025. Microsoft’s supported-version list also shows separate lifecycles for long-term servicing and IoT editions. Don’t apply the ordinary Windows 10 deadline to every specialist device.
Record the edition, version, recent update status and any Extended Security Updates enrolment. If a device runs laboratory, imaging or production equipment, obtain the vendor’s support position before changing it.
An operating system can also be supported while the application or hardware around it isn’t. Include those dependencies in the inventory.
Assess eligible Windows 11 upgrades
Check Microsoft’s Windows 11 system requirements against each device. They include a compatible processor, TPM 2.0 and Secure Boot capability, alongside other hardware requirements.
Use the vendor’s assessment tools or your management system, then test the business applications, printers, scanners and integrations. A device can pass the hardware check and still break a workflow after the upgrade.
Prepare a tested backup, encryption recovery information and a rollback plan. Pilot with representative staff before scheduling the rest. Account for deployment time, training and support even when an upgrade licence has no additional charge under your agreement.
Don’t bypass hardware checks to extend a business computer’s life without a supported plan. Confirm licensing and the supported Windows 11 version with IT.
Use commercial ESU as a dated bridge
Microsoft’s commercial ESU guidance describes eligible Windows 10 devices receiving specified security updates after standard support. Organizations buy it a year at a time, for a maximum of three years, and the price doubles each year. It covers critical and important security updates only: no technical support, new features or guarantee that your applications stay supported.
Have your licensing provider confirm eligibility, activation, update requirements and the term you’re buying. Then check that enrolled devices are receiving the updates.
Obtain a quote in Canadian dollars that identifies licence, implementation and renewal costs. Don’t apply consumer enrolment offers to work computers or assume a US-dollar list price is your local cost.
Give each ESU device an owner and a migration date. Review that date before the next term so an application dependency doesn’t become an open-ended reason to keep extending it.
Replace devices that don’t fit the plan
For computers that can’t meet the supported target, compare replacement with the complete cost of temporary support and later migration. Include configuration, accessories, staff downtime and secure disposal.
Choose specifications from the employee’s work and application requirements. A general replacement age won’t tell you whether a particular device is suitable or economical to keep.
For vendor-controlled equipment that can’t move immediately, document the exception and agree restrictions with the supplier and IT. Network segmentation may reduce exposure, but it doesn’t create security patches or substitute for a supported replacement plan.
Verify the result and keep the records
After an upgrade or replacement, confirm management enrolment, encryption, endpoint protection, updates and the employee’s main tasks. Check that needed records were transferred and the old device has been handled according to the disposal process.
Ask your insurer or relevant adviser about requirements in your own agreements. Running a particular Windows version doesn’t by itself decide whether a claim or compliance obligation is satisfied.
Keep the inventory current with the chosen path, responsible person and completion date. The next review should show which devices have moved and which exceptions still need attention.


