What the converter reads
Manifest
Template metadata, data connections, fields, rules, and view references.
XSL views
Layout signals, controls, labels, buttons, images, repeating regions, and view-specific bindings.
Resources
Embedded images and other media assets that can be exported or placed on generated screens.
How .xsn conversion works
Upload
Drop in the native InfoPath package.
Analyze
Review views, fields, controls, rules, data sources, media, and warnings.
Map
Confirm primary SharePoint list/library and supporting data sources.
Export
Generate the .msapp package and download embedded media when needed.
Best-fit .xsn packages
- SharePoint list forms with standard text, choice, date, number, Yes/No, and person patterns.
- Form-library templates with promoted fields and clear SharePoint destinations.
- Multi-view forms where buttons switch sections or views using declarative rules.
- Forms where secondary lookup lists can be recreated or mapped in the destination site.
Common questions
Do I upload XML submitted forms or the .xsn template?
Start with the .xsn template. Submitted XML may be useful for data migration planning, but the converter needs the form template to understand layout, fields, rules, and connections.
Can the media be exported separately?
Yes. The export screen includes a media download option for embedded files that were captured from the InfoPath package.
What if the .xsn contains custom code?
The analyzer flags custom code or script as manual review because those behaviors need a Power Apps, Power Automate, or custom connector strategy.