What the closet server used to do
Ten or fifteen years ago, a server in the closet was how a small office worked. It held the shared files, ran email, hosted QuickBooks, managed the printers, and hummed along next to the mop bucket. Buying one was simply what you did when you hit five or ten employees.
That default has flipped. For most small businesses I talk to in the DMV, the honest answer today is no, you do not need a server in the closet, and keeping one is often the most expensive and most fragile part of their setup. But the answer is not no for everyone, so let me lay out both sides with real numbers.
What belongs in the cloud now
Cloud just means the software runs in a provider's data center and you reach it over the internet, paying monthly instead of buying hardware.
- Email and calendars: Microsoft 365 or Google Workspace, roughly 7 to 25 dollars per user per month depending on plan.
- Shared files: OneDrive, SharePoint, or Google Drive, included in those same plans, with version history and access from anywhere.
- Accounting: QuickBooks Online and similar tools have replaced the server-installed versions for most firms.
- Phones: internet-based phone systems have replaced the closet phone box for a fraction of the maintenance.
- Backups: cloud backup of your computers costs a few dollars per machine per month and survives fire, theft, and flood, which the backup drive sitting on top of the server does not.
What still stays local, sometimes
A few legitimate reasons to keep local hardware remain.
- Specialty equipment: machines in dental offices, labs, and manufacturing sometimes require software that only runs on a local Windows machine.
- Legacy line-of-business apps: some industry software has no cloud version worth using, though this list shrinks every year.
- Very large files: video production or CAD teams moving huge files all day can outrun an ordinary internet connection.
- Weak internet: if your location cannot get reliable service, cloud-first is a bad bet until that changes.
Notice what is not on the list: file sharing, email, and backups for a typical office. Those left for good reason. And a local machine that stays is usually a small workstation dedicated to one purpose, not a do-everything server.
The three-year math for a ten-person office
A modest on-premise server costs roughly 4,000 to 8,000 dollars for hardware and Windows Server licensing, plus a battery backup unit, plus backup software and drives. Add maintenance: patching, monitoring, and the occasional emergency visit, commonly 100 to 300 dollars a month if you pay someone, plus electricity, plus the fact that in year four or five you buy it all again.
Over three years that lands somewhere around 10,000 to 20,000 dollars, with a single point of failure sitting in a closet.
The cloud version for the same office: ten users on a mid-tier Microsoft 365 or Google Workspace plan runs roughly 1,500 to 3,000 dollars a year, including email, files, and the office apps, with the provider handling uptime and security patching. Over three years, roughly 4,500 to 9,000 dollars, no hardware refresh, and the office keeps working when the closet floods. These are honest ranges; your numbers depend on head count and plan. But the gap is rarely close for a typical office.
Migration order of operations
If you are moving off a server, sequence matters.
- Back up everything first, and verify the backup actually restores. Not optional.
- Move email to Microsoft 365 or Google Workspace. It is the best-trodden path and the fastest win.
- Move shared files next, cleaning up as you go; a migration is the one time everyone agrees to delete the 2011 folder.
- Deal with applications last, one at a time: cloud version, replacement, or a plan for the one that must stay local.
- Keep the old server powered but unused for a month or two as a safety net, then retire it properly, including wiping the drives.
A ten-person office typically gets through this in a few weeks of part-time effort, not months.
What to do next
Start with an inventory, not a purchase order. List everything the current server actually does; the list is usually shorter than anyone expects. Price the cloud equivalent for each item using the per-user numbers above, then compare against what the server costs you over three years including maintenance and its eventual replacement.
If the math says move, schedule email first and follow the order above. If one stubborn application keeps you partly local, move everything else anyway; a small office with cloud email, cloud files, and one dedicated machine for the stubborn app is still far simpler than a closet server doing everything. I run HashWhales this way, and it is the same approach behind the online store I built for a DC flower shop serving more than 15,000 customers: cloud services doing the heavy lifting, nothing critical humming in a closet.