Discover
Find templates, fields, rules, data connections, code, views, attachments, owners, and dependent workflows.
InfoPath modernization
Move critical InfoPath processes into a supported Microsoft operating model
The difficult part is not selecting Power Apps. It is finding every form, understanding the process and dependencies behind it, choosing the right target pattern, and moving without breaking data capture, approvals, attachments, or reporting.
Modernization path
Treat the form estate as a portfolio, not a queue of one-off rebuilds
A repeatable program gives the team a consistent inventory, disposition model, target decision process, governance baseline, and migration sequence.
Rationalize
Decide whether each form should be retired, replaced, rebuilt, redesigned, archived, or deferred.
Select the target
Route forms to Power Apps, SharePoint forms, Dataverse, Microsoft Forms, Power Pages, or a custom pattern.
Migrate and validate
Build priority replacements, test business outcomes, cut over in controlled waves, and retire legacy assets.
Before and after
Modernization should improve ownership and support, not only replace the interface
Before modernization
- Forms are distributed across sites with unclear business and technical owners.
- Submit rules, code, data connections, and workflow dependencies are difficult to inventory.
- IT knows the platform is unsupported but lacks a complete disposition plan.
After modernization
- Priority forms are mapped to supportable Microsoft target patterns.
- Power Apps and Power Automate replacements have owners, testing, ALM, and governance.
- Legacy forms are retired, archived, or remediated in controlled waves.
Migration software
Form MigratorInventory and plan legacy form migrations with Form Migrator
Form Migrator helps teams analyze InfoPath and legacy form estates, identify dependencies, and organize which forms should be converted, redesigned, simplified, or retired.
Planning library
InfoPath migration resources and decision guides
InfoPath modernization
InfoPath to Power Apps checklist
Review inventory, target design, testing, cutover, and governance considerations.
Open resource InfoPath modernizationInfoPath inventory matrix
Organize forms by owner, business value, complexity, dependencies, and target disposition.
Open resource InfoPath modernizationInfoPath effort estimator
Get an initial view of complexity across rules, data, views, code, and target architecture.
Open resource InfoPath modernizationInfoPath vs Power Apps
Compare the legacy form platform with the modern application target.
Open resource InfoPath modernizationPower Apps vs Microsoft Forms
Choose a target based on process depth, integration, user experience, and support needs.
Open resource InfoPath modernizationInfoPath migration service
Review the complete Horton Scientific service path for legacy forms modernization.
Open resourceQuestions
Frequently asked questions
What changed for InfoPath in 2026?
Microsoft support milestones for InfoPath 2013 and InfoPath Forms Services passed in July 2026, increasing the operational, security, and support risk of leaving critical processes on legacy form patterns.
Does every InfoPath form need to become Power Apps?
No. Some forms should become Power Apps, some can become Microsoft Forms or SharePoint list forms, and others should be retired, archived, or redesigned.
Where does Form Migrator fit?
Form Migrator provides consistent form inventory, rationalization, and software-supported migration planning for larger or more complex form estates.
Can Horton Scientific help with the rebuild?
Yes. Horton Scientific can support assessment, target architecture, Power Apps and Power Automate delivery, governance, testing, and cutover.