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

Use reports and builder handoff artifacts

Keep the generated analysis, mapping, media, and validation notes with the exported app package.

Quick answer

In short

The .msapp is only one part of the handoff. Keep analysis summaries, mapping notes, warnings, media files, and validation decisions with the app package.

Most likely cause

Makers lose time when they receive only the app file and have to rediscover why a field, rule, or supporting list was generated a certain way.

What to do next

Download available reports and media from Export, then attach them to the migration ticket or handoff folder.

Recommended handoff bundle

  • .msapp package.
  • Analysis summary and warnings.
  • Field mapping export or builder notes.
  • Media ZIP and manifest.
  • SharePoint provisioning notes or script.
  • UAT/smoke-test checklist.

Why the artifacts matter

Form migrations are easier to validate when the maker can see what was detected, what was intentionally excluded, what was manually overridden, and what still needs business-owner review.

Good ticket language

Include the source file name, app name, destination site/list, export date, known manual-review items, and the owner for production validation.

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

Views5 min read

Download all media from the source form

Export the embedded InfoPath media files as a ZIP so makers can reuse or inspect them during rebuild.

Export8 min read

Validate the generated app before publishing

Run a focused test pass that covers screens, dropdowns, labels, checkboxes, save behavior, and business rules.

Plan5 min read

What to send support for a conversion issue

Send the right source package, screenshots, reports, and expected behavior so a conversion issue can be reproduced quickly.