Windows Mobile is end of support. Here is how to plan the migration.

If you are still running Windows Mobile or Windows CE on the floor, the devices have not stopped working — and that is exactly what makes this easy to put off. Nothing breaks on the day support ends. It breaks later, at the worst possible moment, and usually all at once.

Windows Embedded Handheld 6.5, the version most warehouse and retail handhelds ran, reached end of extended support in January 2020. Windows CE and the older Windows Mobile releases went before it. There are no more security updates, no patches, and no path to a fix when something goes wrong.

What actually goes wrong

The risk is rarely the device itself. It is everything attached to it.

Security. An unpatched handheld sits on the same network as your WMS, your ERP and everything else. In regulated environments — pharmaceutical, medical device, food — that is increasingly the thing an auditor asks about, and "it still works" is not an answer.

No support path. When a device fails, you are on your own. So is your software vendor: most WMS and MES platforms have already dropped support for the old clients, which means a problem you could once escalate is now yours to solve.

Spares get expensive. These devices are long out of production. What is left is refurbished, and the price goes one direction. Teams often end up cannibalising dead units for batteries and printheads — which works right up until it does not.

The applications age out. Browser-based and green-screen apps written for the old platform will not move to modern hardware unchanged. That work has to happen sometime, and it takes longer than the hardware swap.

The migration is mostly not about hardware

Almost every operation we help through this expects the project to be "buy new scanners." The device is the small part. What takes the time is everything that touches it.

1. Find out what you actually have. Not the count in the asset register — the real inventory, by model and OS version. Most operations we walk find devices nobody knew were still in service, and a handful already failed and quietly worked around.

2. Work out what the applications need. Is it a browser-based client, a terminal emulator, or a native app? Terminal emulation usually moves across with configuration. A native app written for Windows Mobile generally does not, and that is the long pole in the project.

3. Choose the device class before the device. Handheld, wearable, vehicle-mounted, rugged tablet. The right answer depends on what the person is doing with their hands, not on a spec sheet. Getting this wrong is expensive because you find out months in.

4. Roll out by area, not all at once. Take one zone or one shift, run it in parallel, and let the people using it tell you what is wrong before it is on every device. A staged rollout costs a little more in time and saves a great deal in disruption.

5. Plan for what rides along. New devices mean new batteries, new charging, new mounts, new holsters — and often new label and ribbon combinations. This is the part that gets left off the budget and then holds up the go-live.

What replaces it

In practice, Android. The rugged handhelds, wearables and tablets from the major manufacturers all run it now, with long support lifecycles and security update commitments that the old platform never had. Devices can be centrally managed, updated and locked down — which for most operations is a genuine improvement rather than a like-for-like swap.

When to start

Sooner than feels necessary. A migration planned over a couple of quarters is routine. The same migration forced by a failure — a device that cannot be replaced, an audit finding, a software vendor withdrawing support — is expensive and badly timed.

If you are running Windows Mobile or CE today, the useful first step is small: find out exactly what you have and what those devices are running. That inventory tells you whether this is a six-week project or a six-month one, and it costs nothing to do.

We have taken operations through this in manufacturing, warehousing, healthcare and logistics, and we are happy to look at yours and tell you honestly what needs to move first and what can wait. Every recommendation starts with a conversation.