SharePoint Online vs On Premises: Which Fits Your Business?

Until recently, a business could put this decision off indefinitely. A SharePoint Server 2016 or 2019 farm sat in the server room, did its job, and received security updates. That changed in July 2026, when both versions reached the end of extended support — Microsoft’s lifecycle pages for SharePoint Server 2016 (opens in new tab) and SharePoint Server 2019 (opens in new tab) carry the authoritative dates. The farm still works. It simply stopped being patched.

This page is about the decision, not the move. It is written for the owner, operations lead or IT manager who has to recommend one direction and defend it. If you have already decided to leave the farm, our SharePoint Server to SharePoint Online migration page covers how that project is scoped and run, including the workflows, forms and custom web parts that need rebuilding. Nothing here carries a price, because licence costs depend on your agreement and user count, and a generic figure would mislead more than it helps.

The real choice: who runs the platform

Strip away the feature lists and the decision is about who carries the work of running SharePoint. With SharePoint Online, Microsoft runs the servers, applies the updates and ships new features; you own the configuration, permissions and content. With SharePoint Server Subscription Edition, you own everything from the hardware and SQL Server to the monthly patch cycle, in exchange for full control over where the data sits and what code runs on it.

Neither is the wrong answer in general. Each is wrong for a particular kind of business, and most of the expensive mistakes come from choosing by habit — staying because the farm has always been there, or moving because everyone else is — rather than by the factors below.

Side by side across the factors that decide it

This comparison covers what changes for a business, not every feature. Where Microsoft publishes the detail, follow the linked documentation rather than this summary; lifecycle and servicing terms in particular are revised over time.

Cost: compare like with like

The most common error in this comparison is setting a Microsoft 365 per-user price against a server licence quote and calling the server cheaper. The server licence is the smallest part of an on-premises farm. The full column includes the SQL Server licences beneath it, the hardware or virtual machines, a tested backup and restore process, a second environment if you want somewhere to test updates, and the hours of a person who knows how to keep a SharePoint farm healthy. When that person leaves, the cost of replacing their knowledge belongs in the column too.

The Online column has its own trap: many businesses already pay for SharePoint Online inside their Microsoft 365 plan and do not realize it. If your staff already have Business Standard, Business Premium or an enterprise plan, the incremental licence cost of moving may be close to zero, and the real cost is the migration project itself. Our guide to what drives SharePoint migration cost for a small business covers that side.

Control and compliance: what actually requires on premises

“We need to keep our data on site” is sometimes a firm requirement and sometimes a preference that has never been tested. It is worth finding out which. A firm requirement usually comes from a specific contract clause, a regulator, a government or defense customer, or a security architecture that keeps certain systems off the internet entirely. In those cases Subscription Edition is the right tool and should be chosen on purpose, not apologized for.

Where the requirement is really about retention, audit or access control, SharePoint Online often gives a compliance officer more to work with, not less, because Microsoft Purview retention policies, sensitivity labels and eDiscovery operate across mail, Teams and files together. Which of those you can use depends on your licence, so confirm against your plan before relying on any one capability. If governance is the real gap, our SharePoint governance consulting covers permissions, ownership and retention design on either platform.

Copilot changes the calculation for many businesses

For a growing number of organizations the deciding factor is no longer storage or cost but AI. Microsoft’s Microsoft 365 Copilot overview (opens in new tab) explains that the licensed Copilot experience grounds its answers in organizational data through Microsoft Graph, scoped to what each user is already permitted to see. SharePoint Online sites are part of that. A Subscription Edition farm is not, by default.

That cuts both ways. If you want Copilot to draft from your proposals, policies and project files, those files need to live in Microsoft 365, and staying on premises effectively rules that out for the content in the farm. But because Copilot respects existing permissions, moving years of over-shared farm content straight into Online without cleaning up access first can surface documents to people who should never have found them. Our checklist on Copilot data governance covers what to fix before switching it on.

The lifecycle commitment you sign up for on premises

Subscription Edition is not a version you install and leave for ten years, which is how many 2016 and 2019 farms were run. Microsoft states that it follows the Modern Lifecycle Policy (opens in new tab), and its servicing policy for Subscription Edition (opens in new tab) says each public update build is supported for a limited period after release, and that you must run a supported build to remain supported. Check Microsoft’s lifecycle page for current dates rather than relying on any third-party summary, including this one.

In practice that means someone on your side owns a recurring patch cycle: testing each update, scheduling downtime and keeping the farm current. That is very manageable for an organization with SharePoint skills in house, and a real burden for one that ran its old farm on goodwill. It also means some legacy features do not come with you. Microsoft publishes the list of features deprecated or removed in Subscription Edition (opens in new tab), and it is worth reading against your farm before assuming an upgrade preserves everything.

When staying on premises is the right call

• A written requirement keeps the data on your infrastructure — a contract, regulator or customer mandate, not just a preference.
• The farm runs on an isolated network that is deliberately kept off the internet.
• A line-of-business system depends on full-trust code that cannot be rebuilt in the cloud yet, and the business accepts the cost of maintaining it.
• You have the people to run it: someone who can patch, back up, restore and troubleshoot a SharePoint farm, with cover when they are away.

When moving to SharePoint Online is the better fit

• You already pay for Microsoft 365, so SharePoint Online is largely licensed and the farm is a second platform you are paying to run.
• Staff work across locations or from home and rely on Teams, where files already live in SharePoint Online sites.
• Copilot is on the roadmap and you want it working over your own documents.
• Nobody wants to own the farm, or the person who did has moved on.

A third answer is legitimate too. Microsoft supports SharePoint Server hybrid configurations (opens in new tab) that connect an on-premises farm with SharePoint in Microsoft 365, which lets most content move while a restricted area stays put. Hybrid works when it is written down, with a named owner for each side and a clear rule about where new content goes. It fails when it is simply the state the migration stopped in.

How we help you decide

We start with an inventory, not a recommendation: what the farm holds, who uses each site, which workflows and forms are still active, which customizations exist, and which requirements are genuinely written down. Sometimes the honest answer is to upgrade to Subscription Edition and keep it well maintained. More often, for the small and mid-sized businesses we work with, the farm moves to Online as fixed-fee SharePoint consulting work, delivered by senior US-based engineers in a typical two to four weeks per scoped phase, with 30 days of hypercare after go-live. If you also have content on a Windows file share, our file server to SharePoint migration playbook covers that path, and our SharePoint migration timeline sets out how the phases usually run.