InfoPath migration to Power AppsReplace InfoPath forms and old SharePoint workflows before they hold up the business.
We find every InfoPath form and SharePoint Designer workflow you still depend on, retire what you do not need, and rebuild the rest in Power Apps and Power Automate. Written fixed price before any work starts.
InfoPath end of life: where things stand
Microsoft has retired InfoPath. Its published timeline removed InfoPath Forms Services from SharePoint Online in July 2026, and the InfoPath 2013 desktop client is out of support. SharePoint 2013 workflows have also been retired in SharePoint Online. If your organisation still relies on these forms or workflows, they are either already broken or running without support.
On-premises SharePoint Server has its own support lifecycle, so dates differ. Check Microsoft's current guidance for your version, or ask us and we will confirm the position for your environment in the scoping call.
Sound familiar?
What InfoPath and SharePoint Designer retirement looks like in practice.
Most organisations find out which forms matter when someone cannot submit one. An inventory now is cheaper than an emergency later.
Forms that no longer open
Browser-based InfoPath forms in SharePoint Online stop working once InfoPath Forms Services is removed, leaving staff with links that go nowhere.
Workflows that stopped running
Approvals built in SharePoint Designer on the 2013 workflow engine no longer run in SharePoint Online, so requests sit unapproved without anyone being told.
Nobody knows what the forms did
The person who built the forms left years ago. Rules, calculated fields and data connections are hidden inside .xsn files nobody can read easily.
Years of submitted data
Thousands of completed forms are stored as XML in form libraries. You need to keep them for records purposes, but they are not easy to search or report on.
Migration approach
How we migrate InfoPath to Power Apps in five steps.
There is no automatic converter, so every migration is a rebuild. The order below keeps the rebuild small and the cutover calm.
1. Inventory
We find every InfoPath form template, form library and SharePoint Designer workflow across your sites, with usage, last submission date and data volume.
2. Triage
Each form is put into one of three groups: retire it, rebuild it in Power Platform, or replace it with something simpler such as Microsoft Forms or a SharePoint list form.
3. Rebuild
Forms that matter are rebuilt as Power Apps with proper validation, and their workflows as Power Automate flows inside solutions, rather than copied screen for screen.
4. Data handling
Historic submissions are either moved into SharePoint lists or Dataverse, converted to PDF for records, or left read-only, depending on retention needs.
5. Cutover
New forms go live with user guidance, old links are redirected or removed, and the original templates are archived with a record of what replaced them.
Triage
Retire, replace or rebuild: not every form deserves an app.
Triage is where most of the saving comes from. We agree each decision with the form's business owner, so nothing disappears that someone still needs.
Retire
Forms with no submissions in the last year, duplicates and forms for processes that no longer exist. Usually a surprising share of the estate.
Replace
Simple data capture with no rules or approvals. Microsoft Forms or a customised SharePoint list form is often enough and avoids building an app.
Rebuild
Forms with business rules, repeating sections, approvals or integrations. These become Power Apps with Power Automate, built to be maintained.
Rebuilding forms in Power Apps
InfoPath forms often carry years of extra fields, hidden sections and rules nobody remembers adding. We rebuild the form your users need today: a canvas app or a customised SharePoint list form, with validation in plain sight, the same data structure where it still makes sense, and role-based access where the old form relied on obscurity.
Where a form fed a database or web service through a data connection, we replace it with a supported connector, and note any premium licensing that implies before you commit.
SharePoint Designer workflow migration to Power Automate
SharePoint Designer 2010 and 2013 workflows become Power Automate cloud flows. We map each workflow's stages, conditions and emails, then rebuild them with modern approvals, clear failure alerts and at least two owners, so the next person to leave does not take the process with them.
Flows are packaged in solutions with connection references, ready to move between test and production environments.
Pricing
Start with an inventory, then a fixed price per form group.
If you want the wider Power Platform estate reviewed at the same time, start with the Health Check and we will scope the InfoPath inventory alongside it. A single important form can go straight to a two-week proof. Larger estates are quoted as a fixed price after triage.
Power Platform Health Check
An audit of your environments, flows and apps with a ranked list of risks and quick wins.
from£1,450
5 working days
- Environment, DLP policy and security role review
- Inventory of apps and flows, including ownerless and failing ones
- Connector and data exposure risks
- Prioritised action plan and a 60-minute walkthrough
2-Week Proof of Value
A working Power App, flow or Copilot agent on your own data, built in two weekly sprints.
from£4,950
2 weeks
- Scoping session and success criteria agreed up front
- Working app, automation or agent in your tenant
- Two demos, one at the end of each week
- Recommendation and quote for production rollout
Spreadsheet-to-App
Replace a business-critical spreadsheet with a secure Power App, approvals and reporting.
from£6,500
3 to 6 weeks
- Data model in Dataverse or SharePoint
- Canvas or model-driven app with role-based access
- Power Automate approvals and notifications
- Handover, documentation and 30-day warranty
The fee for a Licensing Review, Health Check or Automation Sprint is credited in full against a build that follows within 60 days.
All prices exclude VAT. Final fixed price confirmed in writing after a free scoping call.
Honest fit check
When to replace InfoPath forms with Power Apps, and when not to.
A good fit when
- You use SharePoint Online and still have InfoPath forms or SharePoint Designer workflows
- Forms carry business rules, approvals or repeating sections
- You want the replacement to be owned and maintained in-house
- You need historic form data kept searchable for records purposes
Probably not the right tool when
- The process has moved to a dedicated system that already has its own forms
- All your forms are simple enough for Microsoft Forms, which your team can set up
- You are staying on an on-premises SharePoint version that still supports InfoPath and have no plan to move
FAQ
InfoPath migration questions
What happens to InfoPath forms after July 2026?
Microsoft's published timeline retired InfoPath Forms Services in SharePoint Online in July 2026, and the InfoPath 2013 desktop client has reached end of support. Browser-based InfoPath forms in SharePoint Online stop working once the service is removed. On-premises SharePoint Server follows its own lifecycle, so check Microsoft's current guidance for your version.
Is there a tool to migrate InfoPath to Power Apps automatically?
Microsoft does not provide a tool that converts InfoPath forms into Power Apps. Some third-party tools extract form structure, but rules, data connections and workflows still need rebuilding by hand. In practice a manual rebuild is also the chance to drop fields nobody uses and fix the process.
What replaces InfoPath in Microsoft 365?
Power Apps is Microsoft's recommended replacement for complex forms, with Power Automate replacing SharePoint Designer workflows. For simple data capture, Microsoft Forms or a customised SharePoint list form may be enough. We recommend the lightest option that does the job for each form.
How long does an InfoPath migration take?
Inventory and triage usually take one to two weeks. A simple form with an approval can be rebuilt in a few days, while a complex form with repeating sections and integrations can take two to three weeks. The total depends on how many forms survive triage, which is often fewer than expected.
What about SharePoint Designer and SharePoint 2013 workflows?
Microsoft has retired SharePoint 2013 workflows in SharePoint Online, following the earlier retirement of 2010 workflows, and SharePoint Designer 2013 is out of support. These workflows should be rebuilt as Power Automate cloud flows, ideally inside solutions so they can be moved between environments and owned by more than one person.
Can we keep our old InfoPath data?
Yes. Submitted forms are XML files in SharePoint libraries and stay there unless deleted. We can move the data into SharePoint lists or Dataverse so it can be searched and reported on, render it to PDF for records, or keep the library read-only. Your retention policy decides which.
Related
Related services
Tell us which InfoPath forms your teams still rely on.
A free 20-minute call with the consultant who would do the migration. You get a view on scale, the likely retire, replace and rebuild split, and a rough budget.