Attachments

Attachment migration starts with where the files live.

Attachments may be SharePoint list attachments, embedded InfoPath file attachments, form-library XML documents, or media assets inside the template. Each has a different migration and validation path.

01

Attachment patterns

SharePoint list attachments

Often map to the standard Power Apps attachment control when the target remains a SharePoint list.

Form-library submissions

Historical XML documents may need a separate retention and viewing strategy.

Template media

Logos, banners, button images, and other embedded media can be exported as a ZIP from Form Migrator.

02

Validation checklist

  • Create a new item and attach a file.
  • Edit an existing item and verify existing files remain available.
  • Confirm attachment permissions match the SharePoint item or library permissions.
  • Document how historical InfoPath-submitted files will be retained or migrated.
03

What Form Migrator does

Form Migrator can include attachment controls for recognized SharePoint list patterns and can export embedded template media. It does not automatically migrate historical files or XML submissions.

FAQ

Common questions

Does the .msapp include uploaded user files?

No. User-uploaded files are data, not app package assets. Plan data migration separately.

Can I download all media from the source form?

Yes. The Export screen includes a Download all Media option for media captured from the template.

Are attachments always supported in Power Apps?

Standard SharePoint list attachments are common, but production behavior should always be tested in the target tenant.

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.