Sign up / Sign in
Supported6 min readUpdated June 5, 2026

How to start your first InfoPath form analysis

Upload the right .xsn package, run analysis, and get a useful first report without over-configuring the project.

Quick answer

In short

Start with the original InfoPath .xsn package. Run Analyze before entering SharePoint settings so Form Migrator can detect fields, views, rules, connections, and media first.

Most likely cause

Most poor first runs come from uploading a partially extracted package, an unrelated SharePoint list export, or a template that no longer matches the production list.

What to do next

Upload the .xsn, confirm the Analyze summary, then continue to Required Settings only after the detected source looks like the form you expected.

Before you upload

  • Use the original .xsn whenever possible, not screenshots or copied view files.
  • Keep the package intact so the manifest, schemas, XSL view files, rules, and media stay together.
  • Know whether the form replaced a SharePoint list form or used a form library/document library.
  • If the form depends on lookup lists, make sure you know where those lists will live in the destination site.

What analysis does first

The analyzer reads the InfoPath manifest, view transforms, XML schemas, rules, data connections, media references, and promoted SharePoint fields. It does not require destination SharePoint access for the first pass.

A useful first report should show the expected form name, source file, view count, field count, connections, and warnings. If those numbers look wrong, fix the upload before mapping SharePoint columns.

Good first-run workflow

  1. Upload the InfoPath package.
  2. Open Analyze and check the Summary, Views, Rules, Connections, Media, and Warnings tabs.
  3. Connect Microsoft 365 only when you are ready to map the detected form to a destination site.
  4. Use Required Settings to choose the destination site, list/library, and generation options.
  5. Use Optional Settings only for mapping cleanup and builder overrides.
  6. Export the .msapp package and validate it in Power Apps Studio.

Keep reading the next most relevant guides for this form pattern.

Start7 min read

How to read the Analyze screen

Use the summary, tabs, warnings, and detected connections to decide whether the form is ready for mapping.

Start8 min read

How to complete Required Settings correctly

Set the app name, destination SharePoint target, supporting lists, and generation options in the right order.

Export6 min read

Generate the Power Apps .msapp package

Use Export to create a ready-to-import Power Apps canvas package after analysis and setup are complete.