Support for SharePoint Server 2016 and SharePoint Server 2019 ends on 14 July 2026. After that date, Microsoft stops providing security updates, non-security updates and assisted support for those versions. Your farm will not switch off on 15 July. Sites may still load. That is exactly why this one is easy to leave too late.
Running unsupported SharePoint is not a tidy “we will get to it” item. On-premises SharePoint has seen serious exploited vulnerabilities in recent years, and unsupported software increases the risk because future flaws will not be patched by Microsoft. Cyber insurers and auditors are also becoming less tolerant of end-of-life platforms, especially where the system holds business-critical files, HR data or client documents. It is the same unsupported-software exposure that ran through the lessons from the M&S and Co-op attacks.
The honest bit is this. “Move to SharePoint Online” is a destination, not a migration plan. Real readiness starts with knowing what you actually run. A proper review of how your SharePoint is set up often turns up surprises: permissions nobody remembers granting, abandoned HR sites, old templates, legacy web parts and approval workflows that only one person understands.
The dates that actually matter
| Item | Date | What it means |
|---|---|---|
| SharePoint 2013 workflows in SharePoint Online | 2 April 2026 | Removed from existing Microsoft 365 tenants |
| SharePoint Add-ins and Azure ACS in SharePoint Online | 2 April 2026 | Retired, with SPFx and modern authentication as the forward route |
| SharePoint Server 2016 and 2019 | 14 July 2026 | End of support, with no new Microsoft fixes or support |
| InfoPath 2013 and SharePoint Designer 2013 | 14 July 2026 | End of support for legacy forms and design tooling |
| Office Online Server | 31 December 2026 | Retires, so browser-based editing needs a replacement plan |
| SharePoint Server Subscription Edition | No end before 31 December 2035 | Supported on-premises route under Microsoft’s lifecycle position |
The April point is worth pausing on. SharePoint 2013 workflows in SharePoint Online were removed from existing tenants on 2 April 2026. SharePoint Add-ins and Azure ACS were also retired in SharePoint Online on the same date. If a finance approval, onboarding process or line-of-business integration relied on those features, it may already need rebuilding, often in Power Automate, SharePoint Framework or another supported modern approach.
Your three realistic routes
You have three honest options.
The first is to move to SharePoint Online and Microsoft 365. For many businesses, this is the practical route because it removes the burden of patching SharePoint infrastructure and gives users modern document collaboration, permissions, search and compliance tools.
The second is to stay on premises with SharePoint Server Subscription Edition. This suits organisations with regulatory, operational or data-location reasons to keep workloads in house. It still needs careful maintenance, licensing and patching, but it keeps the platform supported.
The third is a hybrid route while complex workloads are moved in stages. If you operate across borders, data residency and operational consistency often shape the decision. That is where European IT support and international IT project support can help keep the approach consistent across offices.
Why tooling is not the whole plan
Microsoft provides migration tooling, but the tool is not the project. Discovery, clean-up, permissions mapping, information architecture, workflow rebuilds and user testing usually take longer than the file move itself.
With July close, sequencing matters. Start with business-critical sites, sensitive data, active workflows and anything exposed to the internet. Archive what no one uses. Rebuild what cannot migrate cleanly. This is the point to plan proper SharePoint migration support, not just a bulk file transfer.
It is also worth seeing what you gain on the other side, from the useful features inside Microsoft 365 to a clearer view of the Microsoft 365 pricing and security changes so the budget conversation is grounded.
Protect what remains during the move
While you migrate, harden what stays online. End-of-support deadlines follow a pattern, the same one behind the push to upgrade to Windows 11, so treat the transition period seriously.
Reduce public exposure where possible, patch everything still supported, review admin access, test your perimeter with network penetration testing and watch for leaked credentials through dark web credential monitoring.
Frequently asked questions
Can I pay Microsoft for extended support after July 2026?
Do not plan on it. Microsoft’s lifecycle page says support ends on 14 July 2026, with no new security updates or assisted support after that date.
Will my SharePoint stop working on 15 July 2026?
No. The servers may continue to run, but the platform becomes unsupported and risk sits with the business.
How long does a SharePoint migration take?
It depends on data volume, customisations, permissions and workflows. Small, tidy environments can move faster. Complex farms can become multi-month projects.
What is the difference between SharePoint Online and Subscription Edition?
SharePoint Online is the cloud service inside Microsoft 365. SharePoint Server Subscription Edition is the supported on-premises SharePoint route.
Start the assessment, not the panic
The businesses that will be calm on 15 July are the ones treating this as a structured cutover, not a last-minute scramble. If you want a clear inventory of your sites, workflows and permissions, and a realistic timeline to match, the team at Northern Star IT support can scope it with you and sequence the move so nothing important breaks on the way across.
