From 2016 SharePoint to modern
Shelter moved from a 2016 SharePoint intranet to modern SharePoint, mostly out of the box, with retention labels and policies to keep content governed.
SharePoint classic retirement
Classic SharePoint customisations have stopped.
SharePoint Add-Ins, Azure ACS and SharePoint 2013 workflows stopped working in Microsoft 365 on 2 April 2026, and legacy IDCRL authentication was retired on 1 May 2026. We audit your tenant for anything that relied on them and rebuild it in Power Automate, Power Apps, SPFx and modern SharePoint.
What to read next
Moving on from classic SharePoint.
If the classic retirement is driving your plans, these are the services that usually come next, from the migration itself to what replaces a classic publishing intranet.
SharePoint migration services
How we move on-premise and classic SharePoint to SharePoint Online.
SharePoint Server 2016 and 2019
The separate on-premise end of support date, 14 July 2026, and what it means.
Out of the box intranet
What to replace a classic publishing intranet with, using modern SharePoint.
SharePoint governance
Getting permissions and ownership right as you move to modern SharePoint.
Power Automate
Where SharePoint 2013 workflows get rebuilt, often simpler than the originals.
Power Apps
The replacement for InfoPath forms, from simple forms to full applications.
2 April 2026
SharePoint Add-Ins, Azure ACS and 2013 workflows stopped working
1 May 2026
legacy IDCRL authentication retired
14 July 2026
SharePoint Server 2016 and 2019 reached end of support
How we work
How a classic migration project runs.
01
Discovery
We audit your tenant for Add-Ins, ACS integrations, 2013 workflows, InfoPath forms, IDCRL scripts and classic publishing sites, and list what each one supports.
02
Design
A prioritised migration roadmap mapping each component to its modern replacement: SPFx, Entra ID app registrations, Power Automate, Power Apps or modern communication sites.
03
Build
We rebuild workflows in Power Automate, forms in Power Apps, Add-Ins as SPFx web parts and extensions, and move publishing sites to modern pages.
04
Train
Training for the people who own the rebuilt workflows and forms, so they can maintain them without us.
05
Go live
Each replacement goes live in turn, tested against the process it supports, with the old component retired once the new one is proven.
Client feedback
What it is like to work with us.
“ThinkShare were a delight to work with and supported us every step of the way with great client service and strong technical expertise.”
“The migration went very smoothly, and our new intranet ensures our data is secure and easily accessible.”
Case studies
Case studies we have delivered.
Read the Shelter case study
A smooth migration
CitNOW's move to a SharePoint intranet and document management system included migrating data from the old setup, and the migration went smoothly.
FAQ
Frequently asked questions.
What stopped working in 2026?
SharePoint Add-Ins, Azure ACS and SharePoint 2013 workflows stopped working in Microsoft 365 on 2 April 2026. Legacy IDCRL authentication was retired on 1 May 2026, and SharePoint Server 2016 and 2019 reached end of support on 14 July 2026.
Are classic SharePoint pages being removed?
No. Microsoft has confirmed the classic user experience, including classic pages and lists, will coexist with modern. It is the technologies behind classic customisations that have been retired.
What replaces InfoPath forms?
Power Apps or Microsoft Forms, depending on how complex the form is. InfoPath Forms Services is deprecated and has had no new feature development since 2014.
What should we do first?
Audit your environment for Add-Ins, 2013 workflows, InfoPath forms and IDCRL scripts, then prioritise the processes that have broken or are most important to the business.
Book a call about classic SharePoint.
Tell us what you are working on and we will come back to you within one working day to arrange a call.