# InfoPath Migration Effort Estimator

Estimate the relative effort of moving an InfoPath estate to Power Apps, SharePoint forms, Dataverse, Microsoft Forms, or another Microsoft-native pattern.

How many forms are in scope?

Count production forms, templates, browser forms, filler forms, and business-critical variants.

- 1-10 forms
- 11-50 forms
- 50+ forms

How complex is the form logic?

Consider rules, repeating sections, conditional fields, calculations, code, and dynamic behavior.

- Basic fields and validation
- Rules and conditional logic
- Code, repeating sections, or complex rules

How many data dependencies exist?

Review SharePoint lists, libraries, XML, SQL, web services, attachments, and reporting dependencies.

- Single list or library
- Multiple lists or data sources
- External services or complex data model

Are forms tied to workflows?

Look for SharePoint workflows, Nintex, Power Automate, approvals, emails, and downstream updates.

- No workflow dependency
- Simple approvals or notifications
- Business-critical workflow chain

How clear is ownership?

Forms without current business and technical owners are harder to validate and cut over.

- Owners and validators are known
- Some owners unclear
- Many orphaned or disputed forms

How much deadline pressure exists?

Consider SharePoint, InfoPath, compliance, merger, or platform retirement deadlines.

- Flexible timeline
- Planning window under 6 months
- Urgent deadline or active platform risk

## Move legacy forms with Form Migrator

For organizations with InfoPath or legacy form sprawl, Form Migrator gives the modernization effort a product-led path instead of a one-form-at-a-time rebuild cycle.

Where Form Migrator fits

- ✓ Inventory and rationalize forms before rebuilding them in Microsoft-native patterns.
- ✓ Prioritize high-value forms by business criticality, usage, data complexity, and owner readiness.
- ✓ Support a repeatable migration motion across Power Apps, Power Automate, SharePoint, Dataverse, and governance workstreams.