Microsoft ended support for SharePoint Server 2016 and SharePoint Server 2019 on 14 July 2026. If your organisation still runs either version, your farm no longer receives security patches, bug fixes or technical support. The servers keep working, which is exactly why this decision gets postponed. This guide explains what has changed, what it puts at risk, the three realistic options, and a 90-day plan you can start now.
What actually ended on 14 July 2026
- Extended Support ended for both SharePoint Server 2016 and 2019. There are no more security updates, fixes or Microsoft support for either version.
- SharePoint Designer 2013 and the InfoPath 2013 client also reached end of support on the same date.
- What did not end: your data, your sites and your farm keep running. SharePoint Online and SharePoint Server Subscription Edition are unaffected.
Why an unsupported farm is a real risk
An unsupported farm is not an emergency on day one. The risk builds every month, because every new vulnerability stays unpatched.
- Security: unpatched servers are easier targets for data theft and ransomware, especially when they can be reached from the internet or by partners.
- Compliance: auditors are less forgiving of breaches on unsupported platforms, and classic sites can sit outside the coverage of your Microsoft Purview audit log. That can turn into findings in ISO 27001, SOC 2 or sector audits.
- Broken customisations: farm solutions, SharePoint Designer workflows and InfoPath forms have no supported future. They need to be rebuilt, not just moved.
One point catches many teams out. In Microsoft 365, the SharePoint Add-in model and Azure Access Control Services (ACS) were retired on 2 April 2026. Any add-in based solution you hoped to carry across to SharePoint Online has to be rebuilt first, usually with the SharePoint Framework, Power Apps or Power Automate.
Planning a SharePoint project? Talk to an expert
Your three options
1. Move to SharePoint Online
This is the default route. Microsoft patches and maintains the platform, and your content connects naturally to Teams, Power Automate and Microsoft 365 Copilot. InfoPath forms and old workflows must be rebuilt before cutover. See our SharePoint migration service for how we run these projects.
2. Upgrade to SharePoint Server Subscription Edition
Choose this when regulation or policy requires data to stay on-premises. Subscription Edition follows Microsoft's Modern Lifecycle Policy, so it has no fixed retirement date. It needs Windows Server 2019 or 2022 and SQL Server 2019 or newer, and your old customisations still need a plan. Read more on our Subscription Edition upgrade page.
3. Hybrid
Run a Subscription Edition farm alongside a SharePoint Online tenant. This lets you move content and teams in stages while sensitive data stays on-premises. It is more to manage, so use it as a bridge or for a genuine split, not as a way to avoid deciding.
A 90-day plan
Ninety days is enough to decide, rebuild your highest-risk workflows and move a first wave. Large farms usually need six to eighteen months for the full programme, so starting matters more than finishing in one go.
Days 1 to 14: inventory and decide
- Scan the farm with the free SharePoint Migration Tool (SPMT) and list every site, its size and its last activity.
- Catalogue customisations: farm solutions, add-ins, InfoPath forms, SharePoint Designer workflows and custom code.
- Rank sites by business criticality, then choose a destination for each one.
Days 15 to 45: triage and rebuild
- Retire sites nobody uses. Most old farms hold a lot of content that does not need to move.
- Rebuild priority forms and workflows in Power Apps and Power Automate before the content arrives.
- Clean up permissions now, so old access mistakes do not follow the content into the new tenant.
- Design the SharePoint Online structure, including hub sites and naming.
Days 46 to 90: pilot, migrate in waves, cut over
- Pilot with one department and fix what the pilot exposes.
- Migrate in waves by priority, with clear communication and short training for each group.
- Get business sign-off before cutover, keep a verified backup, and switch off the old farm only after that sign-off.
What a migration costs
Cost depends on data volume, the number of sites, how much customisation exists, and how many forms and workflows need rebuilding. Our SharePoint Online migration cost and timeline guide breaks these drivers down, and the SharePoint migration planning guide gives you a checklist to work from.
Mistakes to avoid
- Lifting and shifting everything. Moving years of unused content makes the new environment as cluttered as the old one.
- Leaving InfoPath until last. Forms take the longest to rebuild, and people notice them first when they stop working.
- Migrating before cleaning permissions. Oversharing is much harder to fix once content is spread across a new tenant, and it matters more once Copilot can search it.
- Switching off the old farm too early. Keep it read-only until the business has confirmed that nothing is missing.
Not sure where your SharePoint farm stands?
Book a free SharePoint environment review. We list your sites and customisations, flag what will break, and recommend a route and timeline for your organisation.
Book a free reviewFrequently asked questions
Is SharePoint 2016 or 2019 still safe to use?
Both received their last security updates when Extended Support ended on 14 July 2026. Any vulnerability found from now on stays unpatched, so the exposure grows the longer you wait.
Do we have to move to the cloud?
No. SharePoint Server Subscription Edition keeps data on-premises and has no fixed end date under the Modern Lifecycle Policy. It needs a server upgrade, and your old customisations still need to be rebuilt or retired.
How long does a migration take?
It depends on size and customisation. A focused first wave can be live in around 90 days, while large environments typically take six to eighteen months overall.
What happens to our InfoPath forms?
InfoPath is no longer supported and its forms will not run in SharePoint Online. They are usually rebuilt in Power Apps, with approvals handled in Power Automate.
You may also like

What SharePoint migration services include, what drives the cost and timeline, and the questions to ask before you pick a migration partner.

Learn what impacts SharePoint Online migration cost and timeline for enterprises. Understand key factors before moving to SharePoint Online.

Plan your SharePoint 2013 to Online migration with a structured strategy. Learn risks of legacy systems, upgrade steps.

Plan a file server to SharePoint Online migration: audit, clean-up, structure, permissions, tools, pilot and cutover, plus the limits to check first.
