What admins get
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.
Admin checklist
- Identify lists, libraries, and content types that still launch InfoPath.
- Collect .xsn packages and destination site information.
- Load destination lists and libraries from Microsoft 365 in Required Settings.
- Resolve supporting SharePoint lists before export testing.
Where to involve makers
Bring in Power Apps builders after analysis but before production export. That timing gives them compatibility details, mapping context, and known risks without making them do raw discovery from scratch.
Common questions
Does this scan my tenant automatically?
Form Migrator analyzes uploaded packages and connected SharePoint targets. Tenant-wide discovery should be handled through your admin inventory process.
Can admins prepare supporting lists?
Yes. Admins can create or confirm target lists/libraries and then use Required Settings to map them.
What should be handed to builders?
The analyzer report, field mapping, SharePoint targets, package output, and list of manual-review items.