Recommended scoring columns
- ✓Business criticality: low, medium, high, or mission-critical.
- ✓Monthly usage: unknown, rare, occasional, frequent, or daily.
- ✓Data complexity: single list, multiple lists, external data, relational data, or regulated data.
- ✓Logic complexity: no rules, simple validation, conditional sections, complex rules, or code-behind.
- ✓Workflow dependency: none, notifications, approvals, routing, integrations, or records handling.
- ✓Target fit: retire, SharePoint form, Power Apps, Dataverse app, Form Migrator-assisted modernization, or custom architecture review.
Decision rules
- ✓Retire forms with no active owner, no recent submissions, and no records requirement.
- ✓Replace simple data collection with SharePoint list forms or Microsoft Forms when appropriate.
- ✓Use Power Apps for role-aware interfaces, richer validation, mobile needs, or multi-step processes.
- ✓Use Dataverse when the form is really an application with relational data, stronger security, and lifecycle management needs.
- ✓Use Form Migrator for large estates where repeatability, consistency, and speed matter more than isolated rebuilds.
Product accelerator
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.
Executive rollup
The matrix should produce a portfolio-level story: how many forms can be retired, how many need light replacement, how many require serious rebuilds, and where product acceleration changes the timeline.
- ✓Show form counts by disposition and business unit.
- ✓Show high-risk forms by deadline, compliance impact, or revenue/operations dependency.
- ✓Show estimated migration waves and which waves should use Form Migrator.