Sign up / Sign in
InfoPath to Power Apps
Free analysis

Turn InfoPath forms into Power Apps.

Upload an .xsn, see what converts, connect the destination SharePoint list, and download a Power Apps .msapp package when the form is exportable.

Start free analysisCheck compatibilityView pricing
Free compatibility reportSharePoint-aware setupPaid export credits only when needed
Analyze screen showing the Form Migrator guided workspace, summary tabs, and compatibility review dashboard.
01Best first step
Analyze an InfoPath form
Upload an .xsn and get a free report covering views, fields, rules, media, and SharePoint data sources.
Start free analysis →
02Before upload
Check compatibility
See what Form Migrator handles automatically, what needs builder review, and what usually requires manual rebuild.
View compatibility →
03When ready to export
Choose export credits
Analysis is free. Paid credits are used only when you generate downloadable Power Apps output for a form.
View pricing →
How it works

Four steps from upload to builder handoff.

The workflow is intentionally short: analyze first, configure only what is required, then export when the form is ready.

01
Upload
Start with the form package.
Upload the InfoPath .xsn package. Form Migrator reads the manifest, views, schema, rules, and embedded media.
02
Analyze
Understand the conversion picture.
Review the summary, views, fields, rules, connections, media, and warnings before choosing export settings.
03
Configure
Point the app at SharePoint.
Load the destination site, confirm the target list or library, and review generated options such as images and buttons.
04
Export
Download the builder-ready package.
Generate the Power Apps .msapp package, import it into Power Apps Studio, reconnect data sources, and validate save behavior.
What you get

Outputs that help you decide and build.

Use the free report to scope the work. Use export credits when you are ready to generate Power Apps output.

Analyze
Compatibility report
See what will convert before you spend time rebuilding the form.
  • Supported, partial, and manual-review classification
  • Detected views, fields, rules, media, and data connections
  • Clear notes for blockers and cleanup work
Configure
SharePoint-aware mapping
Connect to Microsoft 365, load the real list schema, and confirm the target app settings.
  • Primary SharePoint list or library target
  • Supporting list and lookup data-source targets
  • Field mapping review before package generation
Export
Power Apps .msapp package
When the form is exportable, generate a package your builder can import and validate.
  • Generated screens, data cards, buttons, and media where supported
  • Download all embedded media separately when needed
  • Re-export the same form after settings changes without using another credit
Compatibility

Know where the tool fits before you depend on it.

Full compatibility guide
Best fit

SharePoint-backed InfoPath forms

Form Migrator is strongest when the replacement app will use the same SharePoint site, list or library, and columns.

  • InfoPath forms published to SharePoint lists or libraries
  • Standard fields, views, dropdowns, checkboxes, dates, and text controls
  • Secondary SharePoint lists used for choices or lookup-style data
Plan review time

Complex behavior still needs a builder

The app gets you to a structured starting point, then flags areas where Power Apps logic or manual cleanup is still expected.

  • Script, code-behind, or unsupported InfoPath controls
  • Complex rule chains, submit behavior, and section show/hide logic
  • Secondary-list CRUD experiences that need dedicated Power Apps screens
Who it helps

Built for the teams replacing InfoPath.

The same output can support admin review, SharePoint setup, builder handoff, and client-facing estimates.

Power Platform admins
Standardize migrations across environments, data connections, and governance requirements.
  • Consistent export settings and package outputs
  • Clean handoff to Power Apps builders
  • Better visibility into blockers before build work starts
SharePoint admins
Replace legacy InfoPath forms while keeping SharePoint as the system of record.
  • Real list and library schema discovery
  • Primary and supporting target mapping
  • Clear notes for field and data-source cleanup
Consultants and MSPs
Estimate, package, and hand off migration work with fewer surprises.
  • Free analysis for early triage
  • Export credits for package generation
  • Repeatable artifacts for client review
Pricing

Analyze free. Pay when you need export output.

See all packages
Free analysis
Upload a form and see the conversion picture before you spend anything.
Free
$0
analysis
  • Compatibility report with supported, partial, and manual-review items.
  • Detected SharePoint lists, views, fields, rules, and media.
  • Export packages require a paid form export credit or team plan.
Start free analysis
Single form export
Good for one form or the first production export test.
Starter
$49
one form
  • One export credit for a downloadable Power Apps package.
  • Re-export the same form without consuming another credit.
  • Best when you want to prove the end-to-end path.
View pricing
Migration Pack
A practical starting point for a small InfoPath migration project.
Recommended
$399
10 form exports
  • Ten form export credits.
  • Microsoft 365 discovery for SharePoint sites, lists, libraries, and columns.
  • Run history and handoff evidence for builder review.
View pricing
Wave Pack
For teams working through a larger backlog of InfoPath forms.
Wave
$1,499
50 form exports
  • Fifty form export credits.
  • Portfolio, History, My Work, and Connections workspace tools.
  • Good for migration teams planning several batches.
View pricing
Questions

Answers before you upload.

Browse Knowledge Base
What does Form Migrator generate?
The free step generates an analysis report. Paid export credits generate a Power Apps .msapp package when the form is exportable, plus supporting guidance for builder review.
Is this a one-click production migration?
No. Form Migrator is designed to create a practical first-pass replacement and handoff package. Builders should still import, reconnect data sources, validate the layout, and test save behavior before production use.
When do I need a paid export?
Run the analysis first for free. Buy a single export or package when you are ready to download Power Apps output for an exportable form. Re-exporting the same form after settings changes does not consume another credit.
What if my form uses many views, images, or buttons?
Form Migrator can create screens from InfoPath views and can carry over images and buttons where supported. You can also disable imported buttons or images in Required Settings if you want a cleaner generated app shell.
What if my form is unsupported or only partially supported?
The report tells you what needs review or rebuild. For complex gaps, send us the form package and report from the Contact page so we can review the pattern and prioritize coverage improvements.

Start with one form.

Upload a representative InfoPath package and use the free analysis report to decide whether to export, rebuild, or ask for help.

Start free analysisContact support