Updated
Microsoft retired InfoPath Forms Services in SharePoint Online on 14 July 2026. Lightning Tools Form Migrator migrates InfoPath form designs to Power Apps or Lightning Forms and converts Form Library XML submissions into SharePoint list items. Power Apps has no native InfoPath import. Continued availability in a tenant does not mean support has been extended.
Brett Lonsdale is Co-Founder and CEO of Lightning Tools, where he works with SharePoint and Microsoft 365 customers on form modernisation and InfoPath migration. He became a Microsoft 365 MVP in 2018. Brett’s LinkedIn profile.
InfoPath has served many organisations for years, but following its retirement, teams are facing the task of migrating forms — and more importantly, the data associated with them.
Most of the hesitation around InfoPath migration stems from one issue: Form Library XML data. Migrating a form design is manageable. Migrating the hundreds or thousands of XML records behind it is not.
Lightning Tools Form Migrator was created to solve exactly this problem.
Four-minute demo: migrating an InfoPath form design and its XML data with Lightning Tools Form Migrator.
Why is InfoPath XML data hard to migrate?
InfoPath Form Libraries store user submissions as XML, which often includes:
- Deeply nested data
- Multiple sections and views
- Conditional fields
- Legacy workflows and metadata
- Variations in schema over time
This makes mapping data into modern SharePoint lists or Power Apps a significant challenge if done manually.
How does Form Migrator migrate InfoPath forms and data?
Form Migrator provides a guided, automated migration process:
Form Design Migration
- Map InfoPath fields to SharePoint columns
- Convert layouts and structures
- Carry over rules, validation, and logic
- Target migration options:
- Power Apps
- Lightning Forms
Data Migration
- Parse XML data automatically
- Extract fields and convert them into list items
- Import all existing submissions
- Ensure consistent, clean data in Microsoft 365
The result is a modernised solution that preserves the full history of your InfoPath forms.
On-demand demonstration: migrating InfoPath forms and XML data
The on-demand demonstration shows the migration process. Key steps to plan include:
- How to review existing InfoPath Forms
- How to migrate the design to Power Apps or Lightning Forms
- How to migrate Form Library XML data
- How to validate and publish the modernised solution
- Tips for handling large or complex libraries
Whether you’re planning a phased migration or tackling everything at once, the demonstration can help you plan the next steps.
Who needs this migration?
- Organisations still using InfoPath
- Teams responsible for forms and workflows
- Anyone modernising forms after InfoPath retirement
- IT and digital transformation leaders
Watch the on-demand demonstration
Get a clear, practical plan for moving away from InfoPath following the retirement date.
What does Microsoft say about the InfoPath retirement?
Microsoft set 14 July 2026 as the retirement date for InfoPath Forms Services in SharePoint Online, with removal from tenants after that date. Do not assume that a form still working means support has been extended. Plan and validate your migration to a supported solution.
The Microsoft Lifecycle page for InfoPath 2013 records that extended support ended on 14 July 2026. InfoPath 2013 should no longer be relied on as a supported platform for business-critical forms or workflows.
Microsoft has also deprecated InfoPath Forms Services in modern versions of SharePoint Server, signalling that InfoPath is legacy across both SharePoint Online and on-premises deployments. This highlights the strategic importance of modernising forms and data structures following the 2026 retirement.
Some third-party migration guides, such as KatProTech’s “InfoPath Migration Roadmap”, highlight the urgency around modernising InfoPath forms. These resources often focus on the transition to Power Apps, but it is important to note that Power Apps does not provide native capabilities to import InfoPath forms or automatically migrate Form Library XML data. Lightning Tools Form Migrator bridges this gap by handling both the form design migration and the underlying XML data conversion, giving organisations a complete and reliable migration path.
Industry consultants such as Rightpoint also highlight the risks of holding onto legacy technologies and the importance of modernising forms and workflows. While they focus on strategic transformation rather than automated InfoPath migration, their guidance reinforces the need for organisations to plan their transition following InfoPath retirement.
InfoPath migration resources
- Explore Lightning Tools Form Migrator
- Compare InfoPath replacement options
- Read the comprehensive InfoPath migration guide
- Plan an InfoPath to Power Apps migration
- Understand the position after InfoPath retirement
Frequently asked questions
Can Power Apps import InfoPath forms and XML data?
No. Power Apps has no native way to import InfoPath forms or migrate Form Library XML data. Lightning Tools Form Migrator converts the form design and XML submissions.
What happens to InfoPath form data after retirement?
Retirement does not itself convert or migrate existing XML submissions. Inventory and preserve the Form Library files, then migrate the data to SharePoint list items or another supported platform. Do not rely on continued InfoPath Forms Services availability in your tenant.
Where can Form Migrator send migrated InfoPath forms?
Form designs can be migrated to Power Apps or Lightning Forms. XML data is parsed, mapped to SharePoint columns and imported as list items.
Why is InfoPath XML data difficult to migrate manually?
Submissions can contain deeply nested data, multiple sections and views, conditional fields, legacy workflow metadata and schema variations over time, making manual mapping slow and error-prone.
About the author
Brett Lonsdale is Co-Founder and CEO of Lightning Tools, where he works with SharePoint and Microsoft 365 customers on form modernisation and InfoPath migration. He became a Microsoft 365 MVP in 2018. Connect with Brett on LinkedIn.
