SharePoint Server 2016 and SharePoint Server 2019 reached the end of extended support on 14 July 2026. Microsoft’s product lifecycle lists the same date for SharePoint Designer 2013, InfoPath 2013 and Project Server 2016 and 2019. If your organisation still runs any of them, it is running software that no longer receives security updates.
We move organisations off SharePoint 2016 and 2019 to SharePoint Online in Microsoft 365 or to SharePoint Server Subscription Edition. We bring across the documents, metadata and permissions you want to keep, and for each custom solution we decide with you whether to rebuild it, replace it or retire it.
What End of Support Means
Your SharePoint farm did not switch off on 14 July. It still serves pages and stores documents. What changed is that, in Microsoft’s words, there are no longer any “new security updates, non-security updates, free or paid assisted support options or online technical content updates”.
No Security Updates
Microsoft no longer releases security patches for SharePoint 2016 or 2019. Newly found vulnerabilities are yours to mitigate.
No Support
If something breaks, Microsoft will not help. It is down to your own team or your partner.
Compliance Exposure
Auditors, insurers and customers may ask whether your systems are supported, and unsupported software is hard to defend.
Waiting makes it harder. The Windows Server and SQL Server underneath the farm have support dates of their own, the people who understand its custom solutions move on, and the content keeps growing.
Your Options
There are three supported destinations. The right one depends on your content, your custom solutions and your regulatory obligations.
SharePoint Online
SharePoint in Microsoft 365. Microsoft runs and updates it, and it connects to Teams, OneDrive and Copilot. The best long-term home for most organisations.
SharePoint Server Subscription Edition
The current on-premises version, under Microsoft’s Modern Lifecycle Policy. Content databases from 2016 and 2019 can be upgraded to it directly.
Hybrid
Subscription Edition for content that must stay on your own infrastructure, SharePoint Online for the rest, with search and navigation joined up.
Whichever you choose, the hard part is rarely the documents. It is everything that was built on top of SharePoint over the years.
What We Do
Discovery
sites · content · customisations · usage
We inventory the farm: sites, libraries, content volumes, permissions, custom solutions, workflows, forms and integrations, and find out what is actually used. Much of it usually isn't.
Decide and design
destination · information architecture
We recommend the right destination, and design the information architecture, content types and metadata for the new platform, deciding what moves, what is restructured and what is archived.
Rebuild custom solutions
SharePoint Designer · InfoPath · farm solutions
SharePoint Designer workflows, InfoPath forms and server-side farm solutions don't move to SharePoint Online as they are. We rebuild what's still needed with Power Automate, Power Apps, SharePoint Framework or custom code.
Migrate and verify
content · metadata · permissions
We move the content with automated tooling that preserves metadata, versions and permissions, then verify content, search, permissions and automations before handing over.
Metadata That Survives the Move, With AutoTag
Old farms often hold years of documents with little or no metadata, which makes them hard to find, govern or label once they reach Microsoft 365. Tagging them by hand isn’t realistic.
AutoTag, our own product, can tag content against your taxonomy before the move, on SharePoint Server 2016 or 2019, or after it, on SharePoint Online or Subscription Edition. Once content is in Microsoft 365, AutoTag’s Governance Bots can also apply the Microsoft Purview sensitivity and retention labels you have designed.
Better metadata also makes for a safer Copilot rollout, because it lets you find and label sensitive content before Copilot can surface it. See Permission-Aware Isn’t the Same as Safe.
Why JFDI
We have worked with SharePoint since its earliest versions and have migrated many on-premises farms. We know what tends to be hiding in one: customisations nobody documented, workflows that run part of the business without anyone noticing, broken permission inheritance and content that should be left behind. For Countryside Properties, we moved an existing SharePoint collection of contract and legal documents into a new system with its metadata intact.
Systems that have outgrown SharePoint altogether may be better rebuilt elsewhere; see SharePoint outgrowth. For the wider service, see SharePoint migration.
SharePoint 2016 and 2019 End of Support FAQs
Still running SharePoint 2016 or 2019?
Tell us about your farm and we’ll help you plan a move to a supported platform.

