If your organization is still running SharePoint Server 2016 or SharePoint Server 2019 on-premises, you have a deadline approaching that you can't afford to ignore.
On July 14, 2026, Microsoft officially ends all support for both SharePoint Server 2016 and SharePoint Server 2019. After that date — no more security patches, no more bug fixes, no more technical support. Any vulnerabilities discovered after July 14 will remain unpatched, and Microsoft will not help you resolve issues.
I've been working with SharePoint since 2003, when the platform was called Windows SharePoint Services (WSS). Over the past 20+ years, I've been through every major version launch and every end-of-life cycle. The organizations that plan ahead have smooth transitions. The ones that wait until the last minute scramble, spend more money, and take on unnecessary risk.
Here's everything you need to know about the SharePoint 2016 and 2019 end-of-life, what it means for your business, and what your options are.
What Does "End-of-Life" Actually Mean?
When Microsoft declares a product end-of-life (sometimes called "end of extended support"), it means three things.
First, no more security updates. Microsoft will stop releasing patches for newly discovered vulnerabilities. Your SharePoint servers become increasingly exposed to cyberattacks with every month that passes after the deadline.
Second, no more technical support. If something breaks — a database corruption, a failed search crawl, an upgrade issue — Microsoft support won't help you. You're on your own, or you're paying a third-party consultant premium rates to troubleshoot unsupported software.
Third, no more compliance. Many regulatory frameworks and cyber insurance policies require that production systems run on actively supported software. Running end-of-life SharePoint could put you out of compliance with HIPAA, PCI, SOC 2, or your insurance carrier's requirements.
The End-of-Life Timeline
| Product | Release Date | Mainstream Support Ended | Extended Support Ends |
|---|---|---|---|
| SharePoint Server 2016 | May 2016 | July 13, 2021 | July 14, 2026 |
| SharePoint Server 2019 | October 2018 | January 9, 2024 | July 14, 2026 |
Both products share the same end-of-life date. If you're running either version — or both — the clock is the same.
What Are Your Options?
You have three paths forward.
Option 1: Migrate to SharePoint Online (Most Common)
This is the path the vast majority of organizations are taking, and it's what Microsoft recommends. SharePoint Online is part of Microsoft 365 — a fully managed cloud service where Microsoft handles the servers, security patches, updates, and infrastructure. You get continuous feature improvements, modern user experiences, AI capabilities like Copilot, seamless integration with Teams and OneDrive, and no hardware to maintain.
The migration involves moving your site collections, document libraries, lists, permissions, and content from your on-premises servers to SharePoint Online. Depending on the size and complexity of your environment, this can take anywhere from a few weeks to several months.
Key things to plan for: custom workflows need to be rebuilt as Power Automate flows (SharePoint Designer workflows don't exist in SharePoint Online). InfoPath forms need to be replaced with Power Apps. Custom web parts may need to be rebuilt using the SharePoint Framework (SPFx). And your URL structure will change, so internal links and bookmarks will need to be updated.
Option 2: Upgrade to SharePoint Server Subscription Edition (SE)
For organizations that can't move to the cloud due to data residency requirements, regulatory constraints, or other reasons, Microsoft offers SharePoint Server Subscription Edition (SE). This is a newer on-premises version that operates under a Modern Lifecycle Policy — meaning it receives regular feature updates and has no fixed end-of-life date as long as you stay current on updates.
SE is viable, but understand that you're staying on the on-premises path. You'll still maintain servers, apply updates, and manage the infrastructure yourself. And you won't get cloud-only features like Copilot, modern Teams integration, or the continuous innovation that SharePoint Online receives.
Option 3: Do Nothing (Not Recommended)
Technically, you can keep running SharePoint 2016 or 2019 after July 14. The servers won't stop working on that date. But you'll be running unsupported, unpatched software with increasing security risk, potential compliance violations, and no safety net when things go wrong. The longer you wait past the deadline, the more expensive and disruptive the eventual migration becomes.
What About Older Versions?
If you're still running SharePoint 2013, 2010, or even older versions like MOSS 2007 or WSS 3.0 — those products are already past end-of-life. You're in even more urgent territory. The good news is that migration from these older versions to SharePoint Online is absolutely possible — we've done it many times. The process just requires more careful planning around legacy customizations and content structure.
Related Retirements to Watch
The SharePoint Server end-of-life is part of a broader wave of Microsoft product retirements:
- SharePoint 2016 Workflow — already retired November 2024 for new tenants
- SharePoint 2013 Workflow — retiring April 2, 2026
- InfoPath — retiring July 14, 2026 (same date as SharePoint Server)
- SharePoint Add-Ins and Azure ACS — retiring April 2, 2026
If your SharePoint environment relies on SharePoint Designer workflows, InfoPath forms, or SharePoint Add-Ins, those need to be addressed as part of your migration planning — they won't work in SharePoint Online regardless.
How to Start Planning Your Migration Now
Here's what I recommend as a starting point.
First, inventory your environment. How many site collections do you have? How much content? What customizations are in place — workflows, InfoPath forms, custom web parts, custom solutions? How are permissions structured? This gives you the scope of what needs to move.
Second, identify what needs special attention. Custom workflows, InfoPath forms, heavily customized sites, and third-party integrations won't migrate automatically. They need to be assessed, rebuilt, or replaced. This is the part that catches people off guard if they don't plan for it.
Third, set a realistic timeline. A small environment with a few site collections and limited customization can be migrated in 2-4 weeks. A complex environment with dozens of site collections, extensive customizations, and compliance requirements can take 2-4 months. Work backward from July 14, 2026 — and build in buffer time.
Fourth, get help from someone who's done it before. SharePoint migrations are not a good place to learn on the job. The combination of content migration, permissions mapping, custom solution rebuilding, and user communication requires experience. A botched migration means lost data, broken permissions, missing content, and frustrated employees.
Frequently Asked Questions
Will SharePoint Server stop working on July 14, 2026?
No — your servers won't shut down on that date. But Microsoft will stop providing security patches, bug fixes, and technical support. You can continue running the software at your own risk, but any new vulnerabilities will go unpatched.
Can I just upgrade from SharePoint 2016 to 2019?
You could, but it wouldn't help. Both versions reach end-of-life on the same date — July 14, 2026. Upgrading from 2016 to 2019 just moves you to another product that's about to lose support.
How long does a SharePoint migration take?
It depends on the size and complexity of your environment. A straightforward migration for a small business might take 2-4 weeks. A complex migration with extensive customizations, workflows, and compliance requirements can take 2-4 months. The earlier you start, the more control you have over the timeline.
Will I lose any data during migration?
With proper planning and execution — no. A well-run migration preserves your documents, version history, metadata, list data, and permissions. We validate content completeness and permissions accuracy as part of every migration project.
What happens to my SharePoint workflows?
SharePoint Designer workflows and SharePoint 2013-style workflows do not exist in SharePoint Online. They need to be recreated using Power Automate. We assess every workflow in your environment and rebuild the ones that are still needed.
What about InfoPath forms?
InfoPath is also reaching end-of-life on July 14, 2026. InfoPath forms need to be replaced — typically with Power Apps — as part of your migration. We handle this as part of the migration project.
Do I need a Microsoft 365 subscription for SharePoint Online?
Yes. SharePoint Online is included in most Microsoft 365 Business and Enterprise plans. If you're already using Microsoft 365 for email, Teams, or OneDrive, you likely already have SharePoint Online — you just need to set it up and migrate your content.
The Clock Is Ticking
July 14, 2026 isn't a distant deadline anymore — it's less than four months away. If your organization is still running SharePoint Server 2016 or 2019 on-premises, the time to start planning is now. Not next quarter. Now.
Alpachi has been migrating SharePoint environments since the platform's earliest days. We've seen every version, every scenario, and every challenge. If you need help understanding your options, assessing your environment, or executing a migration — we're here and we're actively doing this work right now.