Windows 11 Migration for Businesses: How to Get It Right

A Windows 11 migration works in five steps: inventory your devices, test software and peripherals, decide per device between upgrade, clean install and replacement, migrate data and switch in waves. Windows 10 reached end of support on October 14, 2025, a year ago now – for every device still running without paid security updates, the move is overdue.

The good news: the switch is primarily a planning task. If you know your devices, software and processes, you can migrate in manageable steps without day-to-day business suffering. This article walks through the approach with test criteria, a decision table and a checklist.

Where you stand a year after end of support

Windows 10 version 22H2 has received no regular security updates since October 14, 2025. Newly discovered vulnerabilities are no longer patched, and attackers know it. On top of that, many vendors of business software, printers and peripherals are focusing their testing and support on Windows 11. Patch levels also matter in audits, with customers and with cyber insurers – an unsupported operating system quickly leads to uncomfortable questions there.

Paid Extended Security Updates (ESU) buy time. They’re offered to businesses on a yearly basis, through October 2028 at the latest, and the price rises each year. The first ESU year ended in October 2026, so anyone still using the bridge now pays more. ESU require Windows 10 version 22H2 and deliver security updates only – no new features and no general bug fixes. They make sense for individual systems that can’t be migrated in the short term.

Note a second deadline: Office 2016 and Office 2019 also left support on October 14, 2025. If you modernize the operating system and Office together, you save yourself a second project round.

Steps 1 and 2: Inventory devices, check software

Step 1: Inventory your devices

Which computers are still running Windows 10, and which ones meet the requirements for Windows 11? This list shows what can be upgraded and what has to be replaced. The key requirements:

• TPM 2.0 (Trusted Platform Module) as a security chip – present on many devices, but disabled in the UEFI
• UEFI with Secure Boot instead of classic BIOS mode – older installations in legacy mode can often be converted with Microsoft’s MBR2GPT tool
• a supported 64-bit processor according to Microsoft’s compatibility list – generally Intel 8th generation or newer and AMD Ryzen 2000 or newer; 32-bit installations can’t be upgraded
• at least 4 GB of RAM and 64 GB of storage – for everyday work, considerably more makes sense

For individual computers, Microsoft’s “PC Health Check” app helps. With many devices, an automated inventory through your device management, such as Microsoft Intune, pays off. In the end you’re left with three groups: devices that can be upgraded directly, devices that qualify with small adjustments – for example by enabling TPM in the UEFI – and devices that have to be replaced. Bypassing the hardware check with a registry change is not an option for business use: Microsoft doesn’t intend such devices to run Windows 11, and updates are not guaranteed there.

Also record who the device is assigned to, where it’s located, how old it is, when the warranty ends and which business applications run on it. This list becomes the basis for wave planning and for your asset management. Special cases such as devices in production or medical technology with specialized Windows editions have their own lifecycles – clarify them with the manufacturer.

Step 2: Check software and peripherals

Business applications, drivers, printers, scanners, specialty devices: test everything that’s used day to day on a Windows 11 pilot system. That way, incompatibilities show up before they paralyze many workstations. Applications that are rarely used but indispensable are especially critical – such as year-end accounting software, a label printer in the warehouse or a measuring device in production. Involve key users from every department in testing.

• Create a list of all applications with version, vendor and maintenance contract
• Obtain vendor statements on Windows 11 compatibility and document them in writing
• Test peripherals, drivers and the scan-to-folder functions of multifunction devices individually – stricter security defaults for network shares can break old configurations
• Check security software, VPN clients and remote access in their current versions
• Record results in a test log and clarify exceptions with the people responsible

Step 3: Upgrade, clean install or replacement?

The decision isn’t just about technology. A device that supports Windows 11 but is already too slow today won’t get faster after the upgrade. So take age, warranty status and performance into account – and decide per device.

Option	Suitable when …	Advantage	Risk
In-place upgrade	hardware and software fit and the device performs well	fast, data and settings are retained	legacy baggage stays; the rollback window is only ten days by default
Clean install with standard image	the device qualifies but should get a clean start	uniform configuration, no legacy baggage	data migration and application installation must be planned
Hardware replacement	the device doesn’t meet the requirements or is too old	new performance, new warranty, automated provisioning possible	procurement, lead times and old-device take-back must be planned in

Often the migration is the right time to bring forward a hardware refresh that was due anyway and carry it out in one go as an IT rollout. New devices can be provisioned largely automatically with Windows Autopilot: the device pulls its configuration and applications itself at first sign-in. How to set up such a rollout is covered in our article Planning an IT rollout.

Steps 4 and 5: Migrate data, switch in waves

Step 4: Migrate data and profiles

User data, bookmarks, signatures, network drives: decide what is migrated automatically and what users check themselves. Typical pitfalls are files stored locally on the desktop, browser profiles with saved logins, email archives and certificates for banking or government portals. A short user checklist – “What do I need to back up before my appointment?” – and a backup before every switch prevent data from going missing the next day. When old devices leave the premises, you need proof that the drives were erased – for example through certified data erasure with a log per serial number.

Step 5: Switch in waves

Switching by department or location keeps operations running. Start with a pilot group that is technically savvy and gives honest feedback. The waves then follow by priority – critical areas such as accounting or customer service ideally outside peak hours. For the days after the switch, a hypercare phase has proven its worth: easily reachable IT support and a dedicated contact resolve small issues before they disrupt the workflow. A short heads-up beforehand and a one-page cheat sheet on the main changes – the centered Start menu, rearranged settings – are usually enough so that employees aren’t caught off guard.

Renew security and standards at the same time

The migration is a good opportunity to shed legacy baggage. Instead of rebuilding the old system one to one, it pays to look at standards and security:

• Disk encryption with BitLocker enabled and recovery keys stored centrally, for example in Entra ID or Active Directory
• Local administrator rights removed for users
• A uniform image and central policies instead of individually configured computers
• Modern sign-in, for example with Windows Hello for Business
• Update rings for the annual Windows 11 feature updates, so updates arrive in an orderly way rather than as a surprise
• Legacy applications retired that nobody needs anymore

Practical example: a service company with 60 workstations

Suppose a service company runs 60 workstations at two locations, and its in-house IT consists of one person. The inventory shows three groups: the larger part of the devices meets the requirements, a few computers only need a UEFI setting changed, and a handful of old devices have to be replaced. Testing reveals that the label printer in shipping needs a new driver and the industry software requires a vendor update.

The pilot group of IT, accounting and two key users switches first, then the departments follow by priority – each in the afternoon and with hypercare the next day. The replacement devices arrive preconfigured and are swapped directly at the workstation during the briefing; the old devices go back with an erasure log. The in-house IT decides on exceptions instead of touching every computer itself.

Common pitfalls and checklist

Common pitfalls

• undiscovered legacy applications that only surface after the switch
• missing drivers for specialty devices such as label printers or card readers
• encryption recovery keys not documented
• hardware ordered too late – lead times push back the waves
• users not informed – appointments fall through or data goes missing
• old devices passed on without documented data erasure

Windows 11 migration checklist

• Inventory of all Windows 10 devices including hardware check and warranty status
• Software and peripherals list with test results and vendor statements
• Decision per device: upgrade, clean install or replacement
• Standard image, encryption and security policies defined
• Backup before every switch and a plan for data and profile migration
• Wave plan with pilot group and hypercare phase
• Documentation and orderly take-back of old devices with erasure proof

How Nano Concepts supports you

We support you from the inventory through to the on-site rollout. Together with our IT service partners RELEDER and FAIMA IT Services, we operate across Germany: Nano Concepts plans and coordinates the jobs, and our partner teams work on site. What the Windows 11 migration service includes is described on the service page; for jobs at individual locations, field service is available. In a free initial consultation we clarify scope and time frame, and you receive a quote after the inventory.