SharePoint 2016 & 2019
End of Support

What end of support actually means here

A SharePoint farm still running 2016 or 2019 doesn't stop working the day support ends — it keeps serving content and accepting requests exactly as before. What disappears is security patches, cumulative updates, bug fixes, and Microsoft technical support. For a platform typically holding an organisation's document libraries, intranet, and often years of business-critical content, that's a materially different risk than "the server turns off."

The absence of an ESU option is the detail that catches people off guard. With Exchange, organisations that weren't ready by October 2025 had a paid bridge to buy more time. SharePoint offers no such bridge — the only supported paths forward are SharePoint Server Subscription Edition (staying on-premises) or migrating to SharePoint Online.

Why SharePoint migrations tend to run longer than people expect

Email migrations are largely mechanical — mailboxes move, structure is preserved. SharePoint migrations carry more variables:

• Customisations and classic workflows. SharePoint 2016/2019 environments often accumulate years of custom web parts, classic (SharePoint Designer) workflows, and InfoPath forms. None of these carry forward automatically — each needs to be assessed and either rebuilt with a modern equivalent (Power Automate, modern pages) or deliberately retired.
• Permissions complexity. Site permissions that have drifted from the original design over years of ad-hoc access grants are common, and migration is often the point where these get audited and cleaned up rather than blindly carried across.
• Large lists and libraries. Document libraries that have grown well past their original design — sometimes into the hundreds of thousands of items — need specific handling to migrate without hitting list view thresholds or throttling in SharePoint Online.
• Third-party integrations. Line-of-business systems, PDF/e-signature tools, or intranet add-ons wired into the on-premises farm need their own reconnection plan against SharePoint Online.

What we look at during discovery

Site and content inventory. Every site collection, library, list, and permission structure mapped before anything moves.

Customisation assessment. Classic workflows, InfoPath forms, and custom web parts catalogued and triaged — rebuild, replace, or retire.

Migration planning. Batched by site or department, sequenced to avoid disrupting active work.

Migration and validation. Content, permissions, and metadata verified against source before the legacy farm is decommissioned.

For the parallel guidance on OneDrive, see our OneDrive migration service, and for the full SharePoint picture, our SharePoint migration service.