SharePoint 2016 and 2019 Support Has Ended: Your Options
SharePoint Server 2016 and 2019 support ended July 14, 2026, with no ESU. Compare Subscription Edition and Microsoft 365, and what to check before moving.

SharePoint Server 2016 and SharePoint Server 2019 reached the end of extended support on July 14, 2026. Both followed Microsoft's Fixed Lifecycle Policy and ended on the same day, so a farm on either version no longer receives security updates or Microsoft support. Unlike SQL Server 2016, which has a paid Extended Security Updates option, SharePoint Server has no ESU program to bridge the gap.
If a 2016 or 2019 farm is still serving users, you're not alone, and the fix doesn't have to be a rushed project. It does need a decision and a plan. Here is what changed, the two supported destinations, and what to check before you move anything.
The dates Microsoft publishes
- SharePoint Server 2016: mainstream support ended July 13, 2021; extended support ended July 14, 2026 (SharePoint Server 2016 servicing policy).
- SharePoint Server 2019: mainstream support ended January 9, 2024; extended support ended July 14, 2026 (Microsoft Lifecycle: SharePoint Server 2019).
- InfoPath and SharePoint Designer 2013: InfoPath 2013 and InfoPath Forms Services reached end of support on the same date, and SharePoint Designer 2013 isn't supported beyond July 2026 (InfoPath Forms Services support update; SharePoint 2013 workflow retirement).
The farm keeps running after the date. What stops is the flow of fixes, and every month without them widens the gap between your farm and what Microsoft supports.
The Canadian Centre for Cyber Security made the same point in July 2026. Its alert AL26-015 covered active exploitation of a SharePoint Server vulnerability (CVE-2026-45659) affecting 2016, 2019 and Subscription Edition. Fixed builds were published for all three versions. The alert recommended three things: identify every on-premises SharePoint Server, especially any exposed to the internet; move to a supported version; and apply the latest security updates. Microsoft has not announced further security fixes for 2016 and 2019 farms.
Two supported destinations
1. SharePoint Server Subscription Edition (stay on-premises)
Subscription Edition (SE) is the current on-premises version and follows the Modern Lifecycle Policy, so it keeps receiving updates as long as you stay current. Microsoft supports upgrading to SE directly from both SharePoint Server 2016 and 2019, which means a 2016 farm doesn't need an interim hop through 2019 (upgrade process overview).
There is no in-place upgrade. You build a new SE farm, copy the content and service application databases across with backup and restore, attach and upgrade them, then upgrade site collections. Databases must be at version 16.0.4351.1000 or higher, or the upgrade is blocked. You can set the old databases to read-only during the move so users can still read their content.
Plan for the platform under it too. SE runs on Windows Server 2019, 2022 or 2025, and needs SQL Server Standard or Enterprise that supports compatibility level 150, such as SQL Server 2019 CU5 or later or SQL Server 2022 (SE database requirements). If your current farm sits on Windows Server 2016 or SQL Server 2016, this is one project, not three. See our notes on Windows Server 2016 end of support and SQL Server 2016 after end of support.
2. SharePoint in Microsoft 365 (move to the cloud)
If you already license Microsoft 365, SharePoint Online removes patching and version upgrades from your team's list entirely. Microsoft's free migration tools (the SharePoint Migration Tool and Migration Manager) move sites, libraries, lists and file shares into the tenant. The work that takes time isn't the copy. It's deciding the site structure, cleaning up permissions and retiring content nobody needs.
A migration path to SharePoint Online is easier when the cleanup comes first. Review who has access to what, remove old sharing and inherited permissions nobody can explain, and archive stale sites before they are copied.
Moving is also a chance to settle information governance. Decide who owns each site, how long each type of content is kept, and how records are structured and labelled, so retention and access rules are in place when users arrive rather than added later.
Some organizations use both: SE for the small set of sites that must stay on-premises, and Microsoft 365 for everything else. Hybrid with SharePoint Online still requires a supported on-premises farm, so it starts with SE.
Check what runs on top before you choose
The version upgrade is usually the easy part. The customizations decide the timeline.
- Workflows. SharePoint 2013 workflows were removed from existing SharePoint Online tenants on April 2, 2026. SE supports SharePoint 2013 workflows through SharePoint Workflow Manager, but SharePoint 2010 workflows reached the end of support on SE on July 14, 2026. Anything heading to Microsoft 365 needs rebuilding in Power Automate.
- InfoPath forms. InfoPath Forms Services was removed from SharePoint Online after July 14, 2026, and Microsoft doesn't provide an automated conversion. Inventory the forms and rebuild the ones still in use in Power Apps, Power Automate or Microsoft Forms.
- Farm solutions and custom code. Full-trust farm solutions don't exist in SharePoint Online. On SE, test them on the new farm before the databases move.
- Search and integrations. Line-of-business connections, search scopes and anything that reads SharePoint through old APIs. If search is part of the plan, our guide to SharePoint search with PnP Modern Search covers the modern approach.
A short plan
- Inventory the farm. Version and build, content database sizes, site collections, service applications, custom solutions, workflows and InfoPath forms.
- Sort sites by destination. What must stay on-premises, what moves to Microsoft 365, and what can be archived or retired.
- Clean up content and permissions. Retire stale content, tidy access groups and agree the governance and records structure before anything moves.
- Fix the dependencies first. Rebuild workflows and forms, and replace farm solutions before cutover, not after.
- Run a pilot. Upgrade or migrate a representative site collection, test with real users and time it. That gives you a realistic schedule for the rest.
- Cut over in phases and retire the old farm. Move one group of sites at a time, so disruption for users stays low. Keep old databases read-only until each phase is signed off, then decommission the servers.
If you're reviewing licensing at the same time, our Microsoft 365 renewal checklist is a useful companion. For a parallel case on the messaging side, see Exchange 2016/2019 updates have ended.
Plan the move with a senior engineer
We help organizations inventory their SharePoint farms, choose between Subscription Edition and Microsoft 365, clean up content and permissions, set up governance and records structure, and cut over in phases, with your team trained to run what's left. If a 2016 or 2019 farm is still in production, start with an inventory and a plan.
Subscribe for the field notes
Join our community of 100+ IT professionals and get tech tips and BITSUMMIT updates once a month.



