Checklist

A practical checklist for InfoPath migration planning.

Use this checklist to move from uncertainty to a prioritized migration plan. It covers inventory, .xsn collection, SharePoint dependencies, compatibility analysis, export, and validation.

01

Checklist

  1. Inventory forms

    List every SharePoint list, form library, site, owner, and process that still uses InfoPath.

  2. Collect .xsn packages

    Export the template packages and note whether each form is a list form, library form, or standalone template.

  3. Record dependencies

    Capture primary SharePoint targets, secondary lists, people lists, status lists, submit targets, and external data connections.

  4. Run analysis

    Upload each package to Form Migrator and review compatibility, warnings, fields, rules, data sources, and media.

  5. Prepare SharePoint

    Create or confirm destination lists, libraries, columns, lookup data, and sample rows.

  6. Generate package

    Use export credits only after the mapping and required settings are ready.

  7. Validate

    Test create, edit, save, dropdowns, buttons, view navigation, rule behavior, and permissions in Power Apps Studio.

  8. Roll out

    Publish the app, communicate the replacement, keep the old form read-only if needed, and monitor early usage.

02

Minimum inventory columns

  • Form name and source site URL
  • Business owner and technical owner
  • Primary list/library and supporting lists
  • Approximate monthly usage and business criticality
  • Compatibility status, blocker notes, and migration wave
03

Good migration waves

Wave 1: quick wins

Standard SharePoint list forms with low rule complexity and few data connections.

Wave 2: standard forms

Forms with multiple views, supporting lists, dropdowns, media, and simple rules.

Wave 3: complex forms

Custom code, external systems, repeating data models, or business-critical routing.

FAQ

Common questions

Can I use the checklist before I have destination SharePoint lists?

Yes. Use it to discover what needs to be created, then return to Required Settings after the target lists exist.

How many forms should we analyze first?

Start with a representative sample: one simple list form, one complex form, one form-library template, and one high-volume business process.

Who should review the output?

At minimum, include the SharePoint owner, Power Apps builder, business owner, and anyone responsible for compliance or records retention.

Ready to test a real form?

Run a free analysis and see the migration picture.

Start with one representative .xsn package. You can review the report before using any export credits.