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

How export credits work

Understand single form exports, migration packs, wave packs, team plans, re-exports, and additional bundles.

Quick answer

In short

Analysis is free. Export credits are consumed when Form Migrator successfully generates a new .msapp package for a form. Re-exporting the same form during review should not require a new credit when it is part of the same migration item.

Most likely cause

Pricing confusion usually comes from thinking every upload is paid. The paid event is package output, not initial analysis.

What to do next

Use the package tier that matches the number of forms you expect to export, not the number of forms you expect to analyze.

Common tiers

  • Single form export for one form or a first production test.
  • Migration Pack for a small set of forms.
  • Wave Pack for a larger department backlog.
  • Team annual plan for ongoing migration teams or consultants.
  • Additional export bundles when a team plan needs more volume.

What counts as a form export

A form export means generating package output for a distinct form migration item. Re-running the same form to fix settings or validate a patch is treated differently from exporting a separate form.

How to avoid wasting credits

  1. Analyze first.
  2. Complete Required Settings fully.
  3. Review Optional Settings for bad mappings.
  4. Export only when the readiness state looks correct.

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

Plan5 min read

When free analysis is enough

Use free analysis to qualify forms before spending export credits or assigning builder time.

Plan8 min read

Triage a portfolio of InfoPath forms

Group forms by complexity, data source, business priority, and export readiness before scheduling migration waves.

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.