Two replacement patterns
Standalone canvas app
Generate a Power Apps app that connects to the configured SharePoint list. This is often best for validation and builder handoff.
Customized list form
Use Power Apps from SharePoint Integrate → Power Apps → Customize forms, then rebuild or copy the generated layout into the SharePoint form shell.
Hybrid rebuild
Use the generated app as the reference, then manually tune integration, permissions, navigation, and launch behavior.
Required SharePoint checks
- Confirm the target site URL and primary list or library.
- Import the real SharePoint column inventory before export.
- Map InfoPath fields to the correct internal SharePoint column names.
- Resolve supporting lists used by dropdowns, people lists, status lists, or lookup-style controls.
Why internal names matter
Power Apps must save to SharePoint internal column names even when the user-facing label is friendlier. Form Migrator keeps the binding names intact and uses extracted form labels for the visible card labels when available.
Common questions
Does Form Migrator delete or change my SharePoint list?
No. The generated app connects to the configured SharePoint target. Schema creation, column cleanup, and list-form replacement remain controlled steps.
Can it discover supporting lists?
Yes. The Required Settings page can load lists and libraries from the destination site and map required SharePoint targets to matching lists.
Why does a generated app sometimes need reconnecting?
Power Apps stores SharePoint data sources by connection and list identity. After import, makers may need to reconnect or refresh the data source in the target tenant.