If your organisation is still relying on InfoPath or legacy Nintex forms in SharePoint, this is no longer something to “review later.” In SharePoint Online, InfoPath forms will stop working on July 14th 2026 as the platform continues to modernise. In SharePoint On-Premises, they may continue to run, but they will be unsupported.
This is why spring cleaning your forms matters. Not as an upgrade exercise, but as a way of regaining control before the platform forces your hand.
InfoPath stops working in SharePoint Online on the 14th July 2026 Support update for InfoPath Forms Services in Microsoft 365 | Microsoft Community Hub
When legacy forms fail in SharePoint Online, they don’t fail politely. Business processes halt, users can’t submit critical information, and IT teams are pushed into urgent recovery mode. At that point, migration isn’t a strategic decision — it’s damage control. On-premises environments can feel safer, but unsupported systems quietly accumulate risk. Over time, forms become fragile, knowledge becomes tribal, and justifying those systems to auditors or stakeholders becomes increasingly difficult.
What’s often missed in these conversations is that the biggest risk isn’t the form design itself — it’s the data behind it.
Most consultants will happily rebuild your forms. They’ll recreate the layout in Power Apps or another modern tool and demonstrate that the form “works.” On the surface, that looks like progress. But the hard question is rarely asked: what happens to the years of data already collected?
For many organisations, that data lives in XML Form Libraries. Rebuilding the form without migrating the data leaves historical records trapped in legacy formats, reporting fractured across old and new systems, and compliance teams struggling to prove continuity. The form may be modern, but the problem hasn’t gone away.
This is where a proper migration changes everything. Migrating the XML itself — not just the form design — allows legacy submissions to be transformed into structured, governed data. When XML form data is migrated into SharePoint Lists (in both SharePoint Online and On-Premises) or into Dataverse for organisations operating in Microsoft 365, the benefits are immediate. Data becomes queryable. Permissions and retention policies apply consistently. Auditing and reporting stop being special cases. What was once technical debt becomes usable, defensible information.
Modernising forms properly doesn’t require a big-bang rewrite or a forced move to the cloud. On-premises organisations can modernise their forms using Lightning Forms, improving usability and maintainability while remaining fully on-prem. Cloud-first organisations can use Power Apps and Dataverse where it makes sense. The critical point is that both the form and the data move forward together.
The cost of waiting is higher than most teams realise. In SharePoint Online, legacy forms will eventually stop working. On-premises, they remain unsupported and increasingly indefensible. Either way, delay removes choice.
Spring cleaning your forms estate is about acting while you still have control — choosing when and how modernisation happens, and ensuring that years of business-critical data aren’t left behind when the UI gets a facelift.
Rebuilding forms is the easy part. Migrating your data properly is what separates a cosmetic fix from a real solution.
