What affects migration cost
Low complexity
Single list forms with standard fields, simple choices, and light validation are usually the fastest to migrate and validate.
Medium complexity
Multiple views, supporting lists, dropdowns, buttons, media, and basic rules need more validation but can still fit the guided path.
High complexity
Code-behind, external systems, repeating data, custom XML patterns, or regulated workflows require builder planning.
How export credits work
- Analysis is free and does not consume credits.
- A credit is consumed only when a new form package export succeeds.
- Re-exporting the same source form is included so you can iterate without burning another credit.
- Teams can use shared credit pools for portfolio work.
Which package to choose
One form
Use the single export for a pilot or a one-off replacement.
Small migration
Use the 10-export migration pack when you have a focused batch of related forms.
Larger backlog
Use the 50-export wave pack or annual team plan when you need shared credits and repeatable delivery.
Common questions
Do we pay before we know if a form is compatible?
No. Run free analysis first. Buy export credits when a form is ready for package generation.
Why use export credits instead of per-user pricing?
Migration work is project-based. Export credits line up with the number of forms you need to generate, not the number of people reviewing them.
Can complex forms still use Form Migrator?
Yes. Even when export is partial, the analysis and builder handoff can reduce discovery and scoping time.