Consulting workflow
Collect a sample set
Ask the client for representative .xsn packages across simple, standard, and complex processes.
Analyze and group
Use compatibility results to estimate effort by pattern instead of guessing from form names.
Prepare targets
Confirm SharePoint sites, lists, libraries, and supporting data before package generation.
Deliver handoff
Provide the .msapp, media ZIP, field mapping, rule notes, and QA checklist to the implementation team.
Best client deliverables
- Portfolio inventory with compatibility status and complexity notes.
- Per-form summary with fields, rules, data connections, and warnings.
- SharePoint target mapping and provisioning notes.
- Builder punch list for manual-review items.
Pricing fit
Use the migration pack or wave pack for client batches. Use the annual team plan for recurring portfolio work.
Common questions
Can consultants use the tool across clients?
Yes, but keep client data separated by account, tenant, and project process. Use credit pools and run history intentionally.
Does the output replace implementation services?
No. It reduces discovery and scaffolding time; implementation still requires validation and cleanup.
Can Form Migrator help with proposals?
Yes. The compatibility report gives more concrete evidence for scope, exclusions, and assumptions.