Moving off the server under the desk

Moving off the server under the desk is overdue when that box still runs quotes, files, or the line-of-business app your London SMB cannot work without. If you need to move office server to cloud (or at least off the office floor), the goal is not a rewrite. It is a staged move onto hosting you own, with backups that actually restore and a runbook someone else can follow when the office is empty.

How the under-desk box fails

Power fails, the UPS was never tested, and the office goes dark on a Monday. Backups sit on the same shelf as the server, or the “backup” is a USB stick nobody has restored in two years. Holidays mean the one person who knows the passwords is away. Disk dies, RAID was never monitored, remote access is a brittle VPN or a port forward that IT would not sign off today. I’ve watched owners discover the business stopped the moment a silent PC under reception stopped humming, and that remote “access” was a RDP session over a home broadband link nobody documented.

That is not a home-lab hobby problem. It is operational risk: payroll, job sheets, and customer files tied to one piece of hardware in a room that gets warm in summer.

Do not rewrite first

The under-desk box is usually running something that already works for the team. Replacing the whole application before you move is how projects swell and miss the point. Lift what you have onto durable hosting, prove restores, then modernise if you still need to. A big-bang “rebuild in the cloud” is how you spend six months explaining why the old machine is still under the desk.

Stage the move

Survey what actually runs: apps, databases, file shares, printers, who logs in, and when downtime is tolerable. Stage a twin environment on managed hosting or a small cloud footprint. Cut over with a written rollback. Keep the old box offline but intact until the first week of real use has passed. Then retire it. Client keeps the accounts, the DNS, and the runbooks. Eight Mile’s infrastructure and cloud work is built for that path: survey, fixed-price move plan, owned accounts.

Managed hosting is enough for many office apps and sites that need a stable VM, backups, and someone reachable when the box is sick. Full AWS (or similar) is overkill when you do not need elastic scale or a dozen managed services; we already wrote about that trade-off for small SaaS in AWS vs managed hosting, and the same honesty applies here. This piece is about leaving the floor, not picking a cloud certification path.

Ownership after the move

After cutover you should be able to name who owns the hosting account, where restores live, and how a second person restarts the service. Secrets are not on the old PC. Monitoring and backups are not “we’ll set that up later.” If only one person can still touch production, you moved the cable, not the risk. Replace on-premise server habits with company-owned logins and a restore test you have actually run.

Get the box off the floor

If moving off the server under the desk is on your list, start with what is running and a fixed-price plan to host it somewhere durable — not with a Kubernetes fantasy or a rewrite nobody asked for.

If you want a short survey of what’s under the desk and a fixed-price move plan, contact Eight Mile and say what the box runs and how bad an outage would be this week.