Most small businesses no longer need an on-premises server. If email, files and identity already live in Microsoft 365 or Google Workspace, the box in the closet is usually a cost with no job. The on-premises server vs cloud decision stays open when a line-of-business app, large local files, poor internet or a compliance rule demands local hardware.
When does a local server still make sense?
A local server earns its place when something has to run on it that cannot run anywhere else, or when the connection to the cloud cannot be trusted. The genuine cases:
- A line-of-business application that only installs on Windows Server. Practice management, dental and veterinary systems, legacy accounting, shop-floor and job-costing software, anything with a SQL Server database the vendor will not host. If the vendor has no cloud edition, or their cloud edition is a remote desktop into their own server at a higher price, the app decides for you.
- Large files worked on locally. CAD assemblies, video, GIS and survey data, high-resolution imaging. Opening a multi-gigabyte file over a sync client is a different experience from opening it over a wired gigabit link, and the people doing that work will tell you so.
- Poor or single-path internet. If the office has one line and no realistic second provider, every cloud workload goes down with it. A local server keeps the practice running through the outage.
- A compliance or contractual requirement for on-site control. Some contracts, auditors and government customers specify where data lives and who can touch it. Cloud services can meet most of these, but if your contract names on-premises storage, that is the requirement until it is renegotiated.
- Devices that depend on it. Door controllers, building systems, lab instruments and older multifunction printers that authenticate against Active Directory or scan to a file share. Each can be replaced; the question is whether you want to replace them this year.
When does an on-premises server no longer make sense?
When its only jobs are the ones the cloud already does. Walk into most small offices with a server and you find it doing four things: holding user accounts in Active Directory, sharing a folder tree, sharing a printer and running backups of itself. If the company also pays for Microsoft 365 or Google Workspace, every one of those has a cloud equivalent already included or close to it: Entra ID for identity, SharePoint and OneDrive or Google Drive for files, cloud or direct-IP printing, and cloud backup for the lot. At that point the server is a second copy of services you already pay for, with its own patching, its own hardware risk and its own licensing. The common tell is a Windows Server 2016 box kept alive to run a file share. Those files belong in Microsoft 365, and the box can be retired.
What does the server in the closet actually cost?
More than the invoice for the hardware, which is the only part most owners remember paying. The recurring costs:
- Hardware refresh. Servers have a service life. Once the warranty lapses you are one failed drive, power supply or RAID controller from a very bad week, and the replacement arrives as a lump sum on a date you did not choose.
- Windows Server licensing and CALs. The operating system is licensed per core, and every user or device that touches it needs a client access license. These are easy to under-buy and expensive to true up in an audit.
- Backup. A local server needs its own backup target, an offsite copy, and someone checking that the jobs ran. If the backup is a USB drive plugged into the server, it is not a backup against ransomware or fire.
- Power, cooling and a UPS. Small individually, constant collectively, and a dead UPS battery is a common cause of the outage that finally forces the conversation.
- The one person who knows it. Every closet server has one. When they leave, the password to the hypervisor leaves with them.
- Patching and monitoring. A server nobody is paid to patch is the one running the unpatched remote-access service. Proper server management is a monthly cost whether you do it in-house or not; the mistake is pretending it is zero.
- End of support. This is the deadline that forces decisions. According to Microsoft's Windows Server release information, Windows Server 2016 reaches the end of extended support on January 12, 2027, Windows Server 2019 on January 9, 2029, and Windows Server 2022 leaves mainstream support on October 13, 2026 with extended support running to October 14, 2031. The Windows Server 2016 lifecycle page lists the same January 2027 end date; after it, no more security updates. A server past that date fails most cyber insurance questionnaires and compliance frameworks on its own.
What does the hybrid middle look like?
Hybrid means cloud identity with some local hardware kept for a reason, and for a lot of small businesses it is the right answer for the next few years. The common shapes:
- Entra ID join with no local server at all. Laptops and desktops join Entra ID directly, policy and patching come from Intune or an RMM platform such as NinjaOne, and files live in SharePoint and OneDrive. This is the end state for an office whose only server job was Active Directory.
- Entra ID plus a local file server. Identity in the cloud, but a Windows file server or a NAS stays for the CAD and video files, with a cloud backup of it. Users get one login, and the heavy files stay on the wired network.
- Hybrid join for an app that needs Active Directory. If the line-of-business app insists on domain accounts, keep a single small domain controller synced to Entra ID, and give it no other jobs. Plan its retirement for the day the app can go.
- The app hosted elsewhere. Move the Windows Server app to a cloud virtual machine or the vendor's hosted edition and retire the local hardware entirely. This keeps the app and still empties the closet.
A NAS deserves a word. It is a server with fewer jobs, not a server with no responsibilities: it still needs patching, MFA on its admin account, no exposure to the internet, and a backup that is not another folder on itself.
What does a migration actually involve?
- Inventory what the server really does. Shares and their permissions, printers, scheduled tasks, the scanner that drops PDFs in a folder, the certificate someone issued years ago, the app's database and its backup job. Most surprises in a migration are things nobody listed.
- Decide per workload, not for the server. Identity, files, printing and the app each get their own destination from the table below.
- Identity first. Move accounts to Entra ID or Google, enforce MFA, and join the devices. Everything after this gets easier because people have one login.
- Files. Rebuild the permission structure in SharePoint or Drive rather than copying the old folder tree, which carries years of exceptions nobody can explain. Watch for path lengths and file types the sync client refuses.
- The application. Vendor-hosted, cloud VM, or kept local. This is the step that sets the schedule, and the vendor's willingness to help sets the pain.
- Cutover and decommission. Run both for a short period, take a final backup of the server, keep it powered off but available for a while, then wipe it.
- Test the recovery plan for whatever you ended with. NIST's Contingency Planning Guide, SP 800-34 Rev. 1, is written for federal systems, but its central point applies to a five-person firm: a recovery plan that has never been exercised is a guess. Cloud or local, know how long a restore takes because you have timed it, and keep that under backup and disaster recovery rather than assuming the subscription covers it.
Decision table: on-premises server vs cloud
| Workload | Keep it local when | Move it to the cloud when | Typical answer |
|---|---|---|---|
| Email and calendar | Almost never | Now, if it is not there already | Cloud |
| Identity and logins | An app hard-requires Active Directory | Everything else | Cloud, or hybrid with one small domain controller |
| Office documents | Rarely | Files are normal office sizes and people work from more than one place | Cloud |
| CAD, video, GIS, imaging | Files are large and edited locally | The team is distributed or the files are mostly archive | Hybrid: local file server or NAS, cloud backup |
| Line-of-business app on Windows Server | The vendor has no hosted edition | The vendor hosts it, or it runs well on a cloud VM | Depends on the vendor |
| Printing and scanning | Older devices need a local queue or file share | Devices support cloud print and scan-to-cloud | Cloud at the next printer refresh |
| Internet is poor or single-path | Yes, for anything the business cannot pause | After a second connection is in place | Local or hybrid until connectivity improves |
| Contract says on-site | Yes, until renegotiated | When the contract accepts an equivalent cloud control | Local |
Frequently asked questions
Is the cloud cheaper than an on-premises server?
Often, but not always, and the comparison is rarely done honestly. Cloud trades a lump sum and a hidden maintenance cost for a predictable per-user subscription. For a small office with ordinary files, that usually wins. For a business with terabytes of active media or a server-only app, the subscription can exceed the server's true cost, which is why the decision is per workload.
Can we keep Active Directory and still move to the cloud?
Yes. Hybrid join syncs on-premises Active Directory to Entra ID so users have one identity and devices can be managed from the cloud. Keep the domain controller small, give it no other jobs, and plan the date it goes.
What happens when Windows Server 2016 reaches end of support?
It keeps running and stops receiving security updates after January 12, 2027, per Microsoft's release information. From then on each new vulnerability stays open, insurers and compliance frameworks treat the server as unsupported, and vendors stop testing their software on it. Plan the replacement or migration to finish before that date.
Is a NAS a server?
Functionally, yes. It serves files, runs an operating system that needs patching, has an admin account that needs MFA and holds data that needs a separate backup. It is a good hybrid piece for large local files; it is not a way to avoid server responsibilities.
How long does a migration take?
Identity and files are the quick part; the line-of-business application sets the schedule, because its move depends on the vendor. Get the vendor's answer on hosting before you set a date for anything else.