InfoPath Replacement Options for SharePoint and Microsoft 365
Choose the right destination for each InfoPath form, preserve the business process and historical data behind it, and migrate without rebuilding everything manually.
What should replace Microsoft InfoPath?
There is no single replacement that is right for every InfoPath solution. A simple form attached to a SharePoint list may be best rebuilt as a modern SharePoint form. A complex application with several data sources and business rules may be better suited to Power Apps and Dataverse. A completed form that only needs to be retained may not need rebuilding at all.
Microsoft’s 14 July 2026 retirement date for InfoPath Forms Services in SharePoint Online has passed. If some forms continue to work, that should not be treated as renewed support or a long-term guarantee. The practical priority is to discover what still exists, understand which processes depend on it and choose a proportionate replacement for each form.
A successful InfoPath replacement programme therefore starts with an estate assessment—not with a blanket decision to rebuild every form in the same technology.
Start with the complete guide
Understand the retirement position, replacement choices, migration risks and planning process.
Why replacing InfoPath is more than rebuilding the screen
InfoPath solutions often contain much more than visible fields. They may include validation rules, repeating sections, conditional formatting, calculated values, connections to other systems, approval workflows and years of submitted XML files.
Before choosing a replacement, assess:
- Form controls, views, rules and conditional behaviour
- Data connections, code and third-party dependencies
- Workflows, approvals, notifications and document generation
- Existing XML submissions, attachments and metadata
- Retention, audit and accessibility requirements
- Business ownership, usage and criticality
Ignoring the data and process around the form is one of the most common causes of migration delay.
How Form Migrator reduces manual work
Lightning Tools Form Migrator helps organisations discover their InfoPath estate, analyse form complexity and move each solution towards the most appropriate modern destination.
- Scan SharePoint Online and SharePoint Server for InfoPath forms and libraries
- Review form structure, controls and migration complexity
- Recreate forms for Power Apps, modern SharePoint and Lightning Forms scenarios
- Migrate XML submissions, attachments, metadata and relationships
- Preserve completed submissions as accessible PDF records
- Validate migrated content before releasing the replacement solution
Learn how Form Migrator handles InfoPath designs and XML data →
A safer InfoPath replacement plan
1. Discover
Create an inventory of forms, libraries, owners, usage and dependencies across the SharePoint estate.
2. Classify
Separate business-critical forms from simple, duplicate, inactive and archive-only solutions.
3. Choose
Select the right destination for each form instead of forcing every process into one platform.
4. Pilot
Test representative forms, validate the design and agree acceptance criteria with process owners.
5. Migrate
Move the form experience together with required submissions, attachments and metadata.
6. Retire
Archive what must be retained, remove obsolete components and record the new support owner.
See an InfoPath migration workflow
Watch how an organisation can move from discovery and assessment to a modern replacement without losing the information held in existing forms.
Frequently asked questions
Can InfoPath forms be converted to Power Apps?
Yes, but the effort depends on the original form’s controls, rules, data connections and workflows. Assessment is essential before committing to a target design.
What happens to existing InfoPath XML data?
Required submissions can be migrated with their attachments and metadata, or preserved as PDF records when they only need to remain readable for audit and reference.
Should every InfoPath form be migrated?
No. An inventory commonly identifies forms that can be retired, consolidated or archived instead of rebuilt. This lets the organisation focus investment on active business processes.
Find the right replacement for your InfoPath forms
Discover your estate with Form Migrator or book a live demonstration to discuss your migration requirements.