What changes when you migrate
InfoPath forms often combine layout, XML data, SharePoint columns, secondary data sources, buttons, rules, and hidden sections. Power Apps can replace many of those patterns, but the right replacement depends on how each form was built.
Views become screens
Multi-view InfoPath forms can become Power Apps screens, and single-view show/hide sections can often become virtual screens.
Fields become data cards
SharePoint-bound fields map to Power Apps cards while preserving the internal SharePoint column binding needed for save behavior.
Rules become formulas
Simple view switches, defaults, validation, and show/hide rules can be scaffolded for review in Power Fx.
A practical migration workflow
Upload the .xsn
Start with the InfoPath form package so the analyzer can inspect the manifest, XSL views, data sources, media, and rule definitions.
Review compatibility
Use the Analyze page to decide whether the form is straightforward, partially supported, or likely to need custom builder work.
Map SharePoint
Connect Microsoft 365, load destination lists and libraries, import real columns, and confirm primary and supporting targets.
Export and validate
Download the .msapp package, reconnect data sources in Power Apps Studio, publish, and test with real list/library data.
Where Form Migrator helps most
Analyze before rebuilding
Upload the InfoPath package and review views, fields, controls, rules, data connections, media, and warnings before committing builder time.
Confirm SharePoint targets
Use Microsoft 365 discovery to confirm the destination SharePoint site, primary list or library, supporting lists, and real column inventory.
Export when supported
Generate a Power Apps .msapp package and a builder handoff when the form pattern is ready for first-pass export.
What still needs review
- Custom code, script, and complex integrations may still require a manual Power Apps pattern.
- Generated packages should be imported, reconnected to the target SharePoint data sources, published, and tested with real business users.
- The compatibility report is the source of truth for what the current uploaded form can and cannot convert automatically.
Common questions
Can Form Migrator fully automate every InfoPath form?
No. It creates a first-pass Power Apps package when supported and flags partial or manual-review work so the builder is not starting from a blank screen.
Does it replace the SharePoint data source?
No. The intended pattern is to keep SharePoint as the data source and generate a Power Apps form or app layer over the existing list or library.
Should we analyze before creating columns?
Yes. Analyze first, then use the Required Settings page to import the real SharePoint column inventory and correct the mapping before export.