The impending end of support for Windows 10 has been a significant concern for IT leaders, prompting many organizations to take proactive measures. With timely migrations to Windows 11 or well-structured Extended Security Update (ESU) plans, these teams have established a foundation for maintaining continuity, security, and compliance. However, a broader analysis of endpoint data reveals a more complex scenario: a notable percentage of endpoints worldwide continue to operate on Windows 10. Recent data from Lakeside’s customer community indicates that approximately 17% of Windows devices within enterprises are still utilizing Windows 10.
To navigate this transition effectively, organizations can draw upon enterprise implementations and endpoint telemetry. The following nine strategies provide a data-driven approach that has already proven beneficial for organizations as they move away from Windows 10.
1. Use hardware and firmware data to assess upgrade readiness
Begin by evaluating each device’s firmware, CPU model, TPM presence, and memory availability. These factors are crucial in determining whether a machine is suitable for Windows 11 or if it could be repurposed for alternative deployments. Even devices that do not meet Windows 11 requirements may still serve valuable roles, such as thin client operations or running different operating systems.
2. Map application usage to target extended support investment
Microsoft’s ESUs enable selective extensions of Windows 10 security support, but blanket adoption can be financially burdensome. By analyzing software usage and dependency data, organizations can pinpoint which systems genuinely require ongoing support—typically those running legacy, business-critical, or non-portable applications. For instance, in a large government finance setting, usage analytics revealed that only a limited number of machines operated a critical reconciliation tool, allowing for a focused ESU scope while other units advanced.
3. Assess device health and digital experience, not just age
Relying solely on device age can be misleading. An older machine that sees light usage may outperform a newer, heavily utilized counterpart. True insights emerge from analyzing metrics such as CPU load, memory pressure, disk latency, and digital employee experience (DEX) scores, which provide a clearer picture of performance issues.
4. Track performance degradation over time
Transitioning to Windows 11 is not a one-time task. Continuous feature and quality updates can alter device performance, making regular assessments vital. Monitoring trends in boot times, memory usage, crash frequency, login delays, and latency can help identify machines that may struggle post-migration or during support extensions.
5. Analyze software dependencies before changing platform
Application compatibility extends beyond mere functionality; it encompasses the underlying dependencies as well. Licensing constraints, authentication layers, middleware, and browser plugins can hinder smooth transitions to Windows 11 or other platforms. These issues often remain unnoticed until workflows break or compliance risks arise. By mapping dependencies based on actual usage data, organizations can flag systems reliant on Windows-specific components, minimizing disruptions and ensuring that only appropriate machines proceed.
6. Validate pilots with comparable data and usage feedback
Piloting new operating systems goes beyond technical trials. For pilots to yield meaningful results, monitoring must reflect the same telemetry used across the Windows domain. Capturing performance, application responsiveness, resource stability, and user feedback consistently is essential. Effective pilots also necessitate anomaly detection, event correlation, and root cause analysis to ensure that feedback from test users can be traced back to specific workload or compatibility issues.
7. Investigate post-upgrade failures with device-level diagnostics
Sometimes, migrations conclude but leave devices in an unstable state. When systems underperform or fail after an upgrade, thorough diagnostics become imperative. Whether the cause is driver misalignment, firmware mismatch, resource contention, or configuration drift, detailed device telemetry reveals what changed and why. This understanding allows for the refinement of driver packs, firmware baselines, and configuration policies, enhancing each subsequent migration wave.
8. Automate fixes for common migration blockers
Common issues such as full disks, outdated firmware, missing patches, or driver conflicts should be identified and resolved prior to migration attempts. Implementing automated remediation scripts or remote updates can prepare machines at scale. Organizations that adopt such practices often report fewer support incidents and smoother deployment experiences.
9. Weigh Windows 11 performance trade-offs carefully
Benchmark comparisons present a nuanced view. In a review of anonymized global endpoint data, upgrading to Windows 11 resulted in approximately 7% better disk throughput and lower latency, yet also led to a 5% increase in CPU usage and a 7% rise in memory demand. Although only about 12% of devices in that dataset had migrated at the time, these metrics offer a realistic perspective on workload trade-offs, suggesting that older or under-spec systems may require hardware upgrades or memory enhancements to avoid performance regressions.
As organizations contemplate their exit from Windows 10, the path forward is not uniform. Some will advance with Windows 11, others will opt for extended support on critical systems through Microsoft’s ESU offering, while some may choose to repurpose devices for alternative roles or platforms. The common thread across all approaches is the necessity for visibility. With comprehensive, real-time insights into hardware, software usage, performance, and user experience, IT departments can make informed, deliberate decisions rather than reactive ones.
