Updated September 2026
If you need to migrate InfoPath forms to Power Apps, the first thing to understand is that this is usually a migration and rebuild project, not a simple file conversion.
Microsoft has retired InfoPath Forms Services in SharePoint Online as of July 14, 2026 and recommends moving existing InfoPath forms and workflows to supported solutions such as Power Apps, Power Automate, Microsoft Forms, or other modern platforms.
There is now Microsoft AI-assisted tooling that can help generate a Power Apps Canvas App from an InfoPath .xsn file. However, it does not eliminate the need to review the original form, validate the generated application, rebuild unsupported functionality, test the data and workflow architecture, and determine whether Power Apps is the right destination in the first place.
This guide explains how to migrate InfoPath forms to Power Apps, what happens to InfoPath features and workflows, what the migration can cost, how long it can take, and when another InfoPath replacement may make more sense.
Quick answer: Can you migrate InfoPath forms to Power Apps?
Yes, but InfoPath forms do not simply import into Power Apps as finished applications.
A typical InfoPath to Power Apps migration involves:
- Inventorying your existing InfoPath forms.
- Documenting each form’s fields, rules, views, data sources, and workflows.
- Determining which forms should be rebuilt, simplified, replaced, or retired.
- Using available migration or AI-assisted tools to accelerate the rebuild where appropriate.
- Recreating the form experience in Power Apps.
- Moving or retaining the underlying data in an appropriate data source.
- Rebuilding approvals and business processes in Power Automate or another supported workflow platform.
- Testing the complete process with real users and data.
- Decommissioning the old InfoPath implementation after validation.
Microsoft’s Power CAT team now provides an infopath-to-canvas skill designed to migrate InfoPath .xsn forms to modern Canvas Apps. This can accelerate parts of the process, but organizations should still treat the output as something to review and validate rather than assuming it is a finished production application.
Why migrate InfoPath forms to Power Apps?
Microsoft InfoPath 2013 reached the end of support on July 14, 2026, and InfoPath Forms Services was removed from SharePoint Online after that date. Microsoft recommends migrating existing InfoPath forms and workflows to supported Microsoft 365 solutions.
For organizations using InfoPath in SharePoint Online, the migration is therefore no longer simply a modernization project. It is part of maintaining a supported application environment.
Microsoft specifically identifies Power Apps, Power Automate, and Microsoft Forms as potential modern solutions for scenarios that previously used InfoPath.
The right destination depends on what your InfoPath forms actually do.
A simple form that collects a few fields may be relatively straightforward to rebuild. A form with repeating tables, complex validation, multiple data connections, custom code, approvals, or specialized security requirements can require substantially more redesign.
How to migrate InfoPath forms to Power Apps
The most reliable approach is to treat the project as an application migration rather than a form replacement.
1. Inventory every InfoPath form
Start by determining exactly where InfoPath is being used.
Do not rely on institutional knowledge alone. Older forms may still be supporting important processes even if the original creator has left the organization.
Microsoft has provided an assessment approach for identifying InfoPath usage across a Microsoft 365 environment. Its guidance describes using the Microsoft 365 Assessment tool to identify InfoPath usage by site collection and site and to understand the lists, libraries, and content types involved.
For each form, record:
- Form name
- SharePoint site
- List or library
- Department or business owner
- Primary users
- Frequency of use
- Business importance
- Data sources
- External connections
- Validation rules
- Conditional logic
- Repeating sections or tables
- Attachments
- Workflows
- Custom code
- Security requirements
- Whether the form is still needed
This inventory becomes the foundation for the migration plan.
2. Decide whether each form should be migrated
Not every InfoPath form needs to become a Power Apps application.
For every form, classify it as one of four options:
Rebuild: The business process is still important and Power Apps is an appropriate destination.
Simplify: The original InfoPath form contains complexity that is no longer necessary.
Replace: The process should move to another platform or architecture.
Retire: The form is obsolete and no longer needs to be supported.
This step can save significant migration effort. Rebuilding every historical form exactly as it existed can preserve complexity that the organization no longer needs.
3. Document the existing form before rebuilding it
An InfoPath form may contain considerably more than the fields users see on the screen.
Document:
- Fields and data types
- Default values
- Validation rules
- Conditional formatting
- Conditional visibility
- Calculated values
- Repeating sections
- Repeating tables
- Multiple views
- Data connections
- Submit behavior
- Attachments
- User permissions
- Custom code
- External systems
- Approval and routing processes
This is especially important for older forms that were developed over many years.
The goal is to understand the business process, not simply reproduce the original screen.
4. Evaluate AI-assisted migration and other tools
Microsoft’s Power CAT team now publishes an infopath-to-canvas skill specifically for migrating InfoPath .xsn forms to modern Canvas Apps.
This changes the migration conversation.
It is no longer accurate to say that there is no tooling that can help convert or generate a Power Apps version of an InfoPath form.
At the same time, AI-assisted generation is not the same as a fully automated production migration.
You still need to verify:
- Fields
- Form layout
- Business rules
- Conditional behavior
- Data connections
- Repeating structures
- Validation
- Security
- Integrations
- Workflow behavior
- User experience
- Performance
The more complicated the original InfoPath form, the more important this validation becomes.
5. Rebuild the form experience
Power Apps provides a modern application framework for rebuilding the user experience.
Simple InfoPath forms may map relatively easily to a Canvas App.
More complex forms usually require design decisions around:
- Screens
- Forms
- Galleries
- Collections
- Power Fx formulas
- Data sources
- Component design
- Validation
- Navigation
- Permissions
- Responsive behavior
The objective should not necessarily be to reproduce every visual detail of the old InfoPath form.
Instead, ask:
What does the user need to accomplish, and what is the simplest supported way to accomplish it?
6. Rebuild the workflow
The form itself is only one part of many InfoPath implementations.
If the original process included approvals, notifications, routing, assignments, or downstream actions, those processes need to be addressed separately.
Microsoft fully retired SharePoint 2013 workflows from existing SharePoint Online tenants on April 2, 2026 and recommends migrating those workflows to Power Automate or other supported workflow solutions.
That means an InfoPath migration may actually involve two related projects:
Form migration: InfoPath → Power Apps
Workflow migration: SharePoint workflow → Power Automate or another supported workflow platform
Treating the two as separate workstreams makes the project easier to scope and test.
7. Test the entire business process
Do not test only whether the new Power Apps form opens.
Test the complete process:
- New submissions
- Editing existing records
- Validation
- Conditional logic
- Attachments
- Approvals
- Notifications
- Permissions
- Mobile behavior
- Data updates
- Integrations
- Error handling
- Reporting
- Workflow history requirements
Business users should test the process before the old InfoPath implementation is retired.
What happens to InfoPath features when you move to Power Apps?
There is no universal one-to-one mapping between every InfoPath feature and Power Apps.
The following examples illustrate where migration effort can increase.
| InfoPath feature | Typical Power Apps approach | Migration consideration |
|---|---|---|
| Basic fields | Power Apps controls | Usually straightforward |
| Validation rules | Power Fx | Rules need to be recreated and tested |
| Conditional formatting | Power Fx and control properties | Logic must be redesigned |
| Repeating sections | Galleries, collections, related data | Usually requires multiple components and formulas |
| Multiple views | Screens and conditional visibility | User experience may need redesign |
| Data connections | Power Apps connectors and data sources | Connections need to be recreated and tested |
| Calculated fields | Power Fx or data-source logic | Formulas need to be recreated |
| Attachments | SharePoint or another supported storage approach | Storage and security need to be reviewed |
| Custom code | Power Fx, Power Automate, connectors, or custom development | Often requires significant redesign |
| Digital signatures | Specialized control or alternative process | No universal one-to-one replacement |
| Workflows | Power Automate or another workflow platform | Separate migration effort |
What happens to InfoPath repeating sections?
Repeating sections are one of the areas where a migration can require significant redesign.
An InfoPath repeating section does not simply become a single Power Apps control.
A Power Apps implementation may use a gallery to display multiple rows, a collection to manage the data in the application, and formulas or a data model that saves the related records.
The correct architecture depends on what the repeating section represents.
For example, an order form containing multiple line items may be better modeled as:
Order → Order Lines
rather than trying to force all of the information into one record.
This is an example of why an InfoPath migration should be treated as an application redesign rather than a simple visual conversion.
What happens to InfoPath data?
The form and the data are separate parts of the migration.
Before rebuilding a form, identify:
- Where current data is stored
- How much historical data exists
- Whether the data needs to remain in SharePoint
- Whether Dataverse is appropriate
- Whether related records exist
- Whether attachments need to be retained
- Whether historical workflow information matters
- Whether reporting depends on the existing structure
For some applications, keeping the existing SharePoint data source may be appropriate.
For others, the migration may be an opportunity to redesign the data model.
Do not assume that moving the form automatically moves or restructures all historical data.
What happens to InfoPath workflows?
InfoPath workflows need to be evaluated separately from the form.
A common modern architecture is:
Power Apps → SharePoint or Dataverse → Power Automate
The exact design depends on the process.
For example, a purchase request might use Power Apps for data entry, SharePoint or Dataverse for storage, and Power Automate for approval routing and notifications.
Organizations that still have SharePoint 2013 workflows in SharePoint Online should address those workflows as part of the broader modernization effort because Microsoft fully retired the SharePoint 2013 workflow engine on April 2, 2026.
How much does it cost to migrate InfoPath forms to Power Apps?
The cost depends on two separate factors:
- The effort required to rebuild the applications
- The licensing and infrastructure required to run them
Power Apps Premium is currently listed by Microsoft at $20 per user per month with annual billing. Microsoft has announced that the list price will increase to $22 per user per month on January 1, 2027. The 2,000-seat minimum Premium plan is currently $12 per user per month and will increase to $14.
Microsoft also states that Power Apps Premium provides licensed users with the ability to build, modernize, and deploy applications, along with Dataverse entitlements and other capabilities.
Your actual migration budget should account for:
- Power Apps licensing
- Power Automate licensing where applicable
- Dataverse capacity where applicable
- Development
- Migration tooling
- Data migration
- Workflow migration
- Testing
- Security
- Training
- Ongoing administration
- Integration work
The license price alone does not represent the total cost of an InfoPath migration.
How long does an InfoPath to Power Apps migration take?
There is no reliable single timeline because InfoPath environments vary dramatically in complexity.
A useful starting point is to classify forms by complexity.
| Complexity | Typical characteristics | Migration considerations |
|---|---|---|
| Simple | Basic fields, limited validation, few integrations | Often the easiest to rebuild |
| Moderate | Conditional logic, multiple views, lookups, data connections | Requires more design and testing |
| Complex | Repeating tables, extensive rules, multiple data sources, custom code, complex workflows | May require significant redesign and architecture work |
A portfolio of 20 simple forms can require very different effort from a portfolio of 20 complex forms.
The most useful way to estimate the project is therefore to inventory the forms first and estimate each form individually.
7-step InfoPath to Power Apps migration checklist
Use this checklist before beginning the rebuild:
1. Inventory
Find every InfoPath form and identify where it is used.
2. Classify
Determine which forms are simple, moderate, or complex.
3. Document
Capture fields, rules, data sources, workflows, integrations, security, and dependencies.
4. Decide
Determine whether each form should be rebuilt, simplified, replaced, or retired.
5. Design
Define the Power Apps, data, workflow, integration, and security architecture.
6. Build and test
Use available migration and AI-assisted tools where appropriate, then validate the resulting application against the original business requirements.
7. Deploy and decommission
Train users, monitor the new process, migrate required data, and retire the old InfoPath implementation only after validation.
When Power Apps may not be the right InfoPath replacement
Power Apps is an important option for organizations moving away from InfoPath, but it is not automatically the best destination for every form.
Evaluate other approaches when your requirements include:
SharePoint Server or on-premises requirements
If your organization needs the form application to remain entirely within a SharePoint Server environment, evaluate platforms that specifically support that architecture.
Power Apps is primarily designed around Microsoft’s cloud Power Platform ecosystem, so an organization with a significant SharePoint Server footprint should evaluate the complete deployment architecture before choosing it.
Air-gapped environments
Organizations operating disconnected or air-gapped environments need to evaluate whether the selected form and workflow platform can operate within their security architecture.
A cloud-dependent service may not satisfy those requirements.
Complex legacy functionality
Some InfoPath applications contain years of accumulated business logic.
If a form has extensive custom code, complicated repeating structures, multiple integrations, or highly specialized behavior, rebuilding it feature-for-feature may not be the most efficient approach.
Licensing requirements
Organizations with very large numbers of occasional form users should model licensing costs before selecting the replacement platform.
The cost of a migration is not just the development project. It includes the ongoing cost of operating the new application.
Power Apps vs. other InfoPath replacement options
Power Apps is only one possible destination.
Depending on your requirements, you may also evaluate:
- Microsoft Forms for simpler data collection
- Power Automate for workflow orchestration
- SharePoint forms for simpler SharePoint-based scenarios
- Custom applications for specialized requirements
- Third-party SharePoint form and workflow platforms
- Platforms that support both SharePoint Online and SharePoint Server
The right choice depends on your environment, complexity, licensing requirements, security model, integrations, and long-term application strategy.
For organizations that need an InfoPath replacement that works across SharePoint Online and SharePoint Server, NITRO Studio by Crow Canyon Software is one option to evaluate. NITRO Studio provides no-code and low-code forms and workflow automation for Microsoft 365, Teams, and SharePoint, including SharePoint environments where a cloud-only Power Apps approach may not fit the deployment requirements.
The important question is not simply, “What replaces InfoPath?”
It is:
“What platform can support this business process, in our environment, at an acceptable level of complexity and ongoing cost?”
Frequently Asked Questions
Can InfoPath forms be converted to Power Apps?
InfoPath forms can be migrated to Power Apps, but organizations should not assume that an InfoPath form becomes a finished Power Apps application through a single automated conversion.
Microsoft’s Power CAT team now provides an infopath-to-canvas skill designed to migrate .xsn InfoPath forms to modern Canvas Apps. The resulting application still needs to be reviewed, tested, and potentially redesigned to account for business rules, data connections, workflows, unsupported features, and user experience requirements.
Is there an InfoPath to Power Apps converter?
Microsoft now provides AI-assisted tooling through the Power CAT infopath-to-canvas skill, which is specifically designed to help migrate InfoPath .xsn forms to Canvas Apps.
That is different from a fully automated migration that reliably produces a production-ready replacement for every InfoPath form.
How do I migrate an InfoPath form to Power Apps?
Start by inventorying the form, documenting its fields and business rules, identifying its data sources and workflows, and deciding whether the form should be rebuilt, simplified, replaced, or retired.
Then design the Power Apps application and data model, rebuild the associated workflow, migrate required data, test the complete business process, and retire the InfoPath implementation after validation.
What happens to InfoPath repeating sections in Power Apps?
There is no universal one-to-one replacement for an InfoPath repeating section.
Depending on the application, Power Apps may use galleries, collections, related SharePoint records, Dataverse tables, and Power Fx formulas to reproduce the behavior.
Complex repeating structures should be treated as a data-model and application-design issue rather than simply a control conversion.
Does Power Apps work with SharePoint Server?
Power Apps does not provide the same native SharePoint form replacement experience for SharePoint Server that it provides for SharePoint Online.
Organizations that need to maintain applications on SharePoint Server should evaluate a form platform designed to support their on-premises architecture.
Do I need Power Automate as well as Power Apps?
Often, yes.
Power Apps can provide the application and user interface, while Power Automate can handle approvals, notifications, routing, integrations, and other workflow automation.
The exact architecture depends on what the original InfoPath process does.
How much does Power Apps Premium cost?
Microsoft currently lists Power Apps Premium at $20 per user per month with annual billing. Microsoft has announced that the list price will increase to $22 per user per month on January 1, 2027. The 2,000-seat minimum Premium plan will increase from $12 to $14 per user per month.
Licensing is only one part of the total cost of an InfoPath migration.
What happens to the workflows behind my InfoPath forms?
The workflows need to be migrated separately.
For SharePoint Online environments, SharePoint 2013 workflows were fully retired on April 2, 2026. Microsoft recommends migrating those workflows to Power Automate or another supported workflow solution.
Can I still use InfoPath?
Microsoft InfoPath 2013 reached the end of support on July 14, 2026. InfoPath Forms Services was also removed from SharePoint Online after July 14, 2026. Microsoft recommends migrating existing InfoPath forms and workflows to supported solutions.
Organizations with SharePoint Server environments should separately evaluate their version, support status, and InfoPath dependencies.
How long does an InfoPath to Power Apps migration take?
It depends on the number and complexity of the forms.
Simple forms with limited logic can require substantially less work than applications with repeating tables, complex validation, multiple data connections, custom code, integrations, or multi-stage workflows.
The most accurate way to estimate the project is to inventory and classify the forms before development begins.
What should I do first if I have hundreds of InfoPath forms?
Do not start rebuilding them one at a time.
Start with an inventory.
Identify where the forms are used, who owns them, how frequently they are used, how important they are to the business, what workflows and data sources they depend on, and whether they are still needed.
Then prioritize the forms that are business-critical and determine the appropriate replacement for each one.
Final takeaway
Migrating InfoPath forms to Power Apps is not simply a matter of opening an old form and converting it to a new format.
The most successful migrations start with an inventory and then evaluate the entire application:
Form → Data → Workflow → Integrations → Security → Users
Microsoft’s newer AI-assisted tooling can accelerate the form conversion process, but it does not remove the need for architecture decisions, validation, testing, and business-process redesign.
For organizations already invested in Microsoft 365 and SharePoint Online, Power Apps can be an important part of an InfoPath modernization strategy.
For organizations with complex forms, SharePoint Server, air-gapped environments, specialized security requirements, large numbers of users, or extensive legacy workflows, it is worth evaluating multiple replacement approaches before committing to a platform.
The first step is not rebuilding the first form.
The first step is understanding the entire InfoPath environment and deciding what each form should become.
Ready to plan your InfoPath migration?
Crow Canyon Software can help organizations inventory, evaluate, and modernize InfoPath forms and workflows across Microsoft 365 and SharePoint environments.
