The last server room.

Somewhere in your building there's a room with a lock, an air-conditioning unit working harder than anyone else in the company, and a collection of humming boxes that everything depends on. Someone once knew exactly how it all fits together. That person may or may not still work for you.

"Move to the cloud" has been the advice for a decade, and most businesses have done it — partially. Mail went years ago. A file share moved. But the server room is still there, because the things left in it are the things that feel too risky to touch. Here's what actually retiring it involves — and how to tell whether you should.

A full migration is five moves, not one

Identity first. Who can access what has to live somewhere, and until it lives in the cloud, nothing else can move safely. Cloud identity — with multi-factor authentication and conditional access — becomes the new perimeter. This is unglamorous and non-negotiable, and it's the first project, not the last.

Devices second. Every laptop enrolled, compliant and patched from the cloud — so access can depend on the health of the device asking for it. Once this works, "the office network" stops being a security boundary, which is the whole point.

Mail and files are usually partly done. Finish them — hybrid setups are where complexity hides.

Desktops are the surprise. Cloud-delivered desktops change the economics of growth: a new starter needs a login, not a build; a new office needs an internet connection, not a comms cabinet. We've seen a sales office double its headcount with zero additional IT footprint — no procurement cycle, no on-site setup, no delay — because the desktops lived in the cloud and scaling was a licensing decision.

The stubborn workloads last. The ERP, the label printers, the machine on the shop floor with software from 2009. These need individual answers — cloud-hosted, replaced, or deliberately kept local with a plan — and they're why the sequence above matters: by the time you face them, everything around them is already modern.

What changes when it's done

• Cost shape: capital purchases and surprise replacements become a predictable monthly figure. Not always cheaper — but honest and flexible.
• Resilience: your disaster recovery plan stops being "hope the server room never floods".
• Security posture: patching, backup and monitoring become services rather than jobs someone has to remember.
• Hiring and growth: location stops being an IT constraint. Work-anywhere stops being a policy debate and becomes an architecture fact.

When you shouldn't (yet)

Honest advisers say this part out loud. If your connectivity is genuinely poor, fix that first. If a critical workload has a hard dependency on local hardware, plan around it rather than pretending. And if the business case rests on "the cloud is cheaper" alone, redo the case — the value is resilience, security and flexibility; cost usually lands roughly neutral once done properly.

The test: if your server room disappeared tonight, how long until you're trading again? If the answer makes you uncomfortable, that's not a reason to avoid the migration — it's the reason to do it.