InfoPath Forms Migration to Power Apps rebuilds your remaining InfoPath forms on supported Microsoft platforms after the retirement Microsoft has now completed: InfoPath Forms Services in SharePoint Online reached end of support on July 14, 2026, publishing new or updated forms was blocked from May 18, 2026, and Microsoft ships no migration tool — every form is a rebuild. We inventory what you still have, decide form by form between Power Apps, customized SharePoint list forms, and Microsoft Forms, rebuild in priority order, preserve historical submission data, and retire the old form libraries cleanly. Priced by written quote after the inventory; a typical engagement runs about 4 weeks.
The InfoPath deadline is no longer approaching — it has passed. Microsoft announced in 2023 that InfoPath Forms Services in SharePoint Online would retire on July 14, 2026, blocked publishing of new or updated forms in SharePoint Online from May 18, 2026, and offered no extension and no automated migration path; the stated guidance is to rebuild in Power Apps, Power Automate, or Microsoft Forms. If you are reading this page, you are most likely in one of two positions. Either you missed the cutoff and forms your business used every day have stopped working in SharePoint Online — an operational outage, and we treat it as one, triaging the forms that block work first. Or you run InfoPath against SharePoint Server on-premises, where forms still render but the platform is a dead end: the InfoPath 2013 designer client itself left support on July 14, 2026, so every year of new forms deepens a hole Microsoft has already closed online. In both cases the work is the same and there is no shortcut: an .xsn form does not convert, it gets rebuilt. What keeps that honest and affordable is triage. Many InfoPath forms turn out to be dead, duplicated, or simple enough for Microsoft Forms or a customized SharePoint list form — rebuilding everything as a canvas app is how these projects blow up. We inventory the forms and their submission libraries, classify each one, rebuild in priority order, and make sure years of submitted XML — often the only record of inspections, approvals, and HR events — is preserved and readable after the form that created it is gone. Companion SharePoint Designer workflows are rebuilt in Power Automate as separately priced companion scope, so neither project hides inside the other.
We scan the SharePoint environment for .xsn templates and form libraries, gather last-used evidence, interview form owners, and classify every form: rebuild (and on which platform), or retire. Business-blocking forms are flagged immediately. Output: the triage report and a written fixed quote.
The forms people cannot do their jobs without are rebuilt first and released as each one passes its owner's acceptance test — nothing waits for a big-bang launch at the end.
Remaining forms are rebuilt per their disposition, with validation and conditional logic mapped from the originals. Companion Power Automate workflow rebuilds land in this wave where scoped.
Historical submissions in the agreed libraries are archived read-only, exported, or parsed into structured columns, and spot-checked for readability. This runs alongside the rebuild waves so nothing is lost while forms change.
Old form libraries go read-only, archives are verified, removal is scheduled, and the handover pack and walkthrough session transfer ownership to your team.
No — this exact situation is what the service is built for. InfoPath Forms Services in SharePoint Online reached end of support on July 14, 2026, so forms that were still in use have become an operational outage rather than a project. We triage the estate fast, rebuild the business-blocking forms first, and release each one as it passes acceptance testing rather than waiting for the whole scope to finish. Your submission data in the form libraries is still there and is preserved as part of the work.
Per Microsoft's announcements: InfoPath Forms Services in SharePoint Online reached end of support on July 14, 2026, and publishing new or updated forms to SharePoint Online was blocked starting May 18, 2026. The InfoPath 2013 desktop client — the last version ever released — left extended support on July 14, 2026 as well. The retirement was announced in 2023, and Microsoft's stated guidance is to move to Power Apps, Power Automate, or Microsoft Forms.
No. Microsoft ships no converter, and .xsn templates do not import into Power Apps — every form is a rebuild. That is not as bad as it sounds: rebuilds are a chance to retire dead forms, simplify over-engineered ones, and land each form on the lightest platform that does the job. The triage report is what keeps a rebuild project from becoming an everything-becomes-a-canvas-app project.
By the form's actual complexity, not by default. Simple data collection with no logic goes to Microsoft Forms. Forms that front a SharePoint list with modest validation become customized list forms — still Power Apps under the hood, but lightweight and covered by seeded licensing. Multi-view forms with repeating sections, role-based views, or complex conditional logic become canvas apps. Each form's disposition is in the triage report with the reason, and you approve it before build.
They are preserved before anything is retired. Depending on what the data is for, that means a verified read-only archive of the original XML, an export, or — where the data still drives reporting or lookups — parsing the XML into SharePoint list or Dataverse columns so it stays queryable. Nothing is deleted until its archive is verified, and the retention decision stays yours.
Yes, on a different clock. Your forms still render, but the InfoPath 2013 designer client is out of support since July 14, 2026, and SharePoint Online — where most Server customers eventually land — no longer runs InfoPath at all. Rebuilding your forms on Power Apps now, or as part of a SharePoint Online migration, beats rebuilding them in a hurry later; we sequence the two projects together when both are in play.
They are the most common companion casualty — many InfoPath forms only make sense with their approval or routing workflow. Workflow rebuilds in Power Automate are companion scope: we quote them as their own line so you see both numbers, and we rebuild form and workflow together where they belong together. What we do not do is silently absorb a workflow project into a forms quote.
Usually not. Customized SharePoint list forms and canvas apps using the standard SharePoint connector are covered by the Power Apps rights seeded into most Microsoft 365 enterprise plans. Premium licensing enters only if a form's rebuild genuinely needs Dataverse or premium connectors — and we flag any such form in writing before building it that way, so the licensing decision is made by you, not discovered on an invoice.
By written quote after the inventory, because the honest cost driver is how many forms you really have and how complex the survivors are — numbers nobody knows before triage. The triage report arrives with a fixed quote for the rebuild scope; you approve it before build begins and pay after you approve delivery.
A typical engagement runs about 4 weeks: inventory and triage in the first week, then rebuild waves in priority order with data preservation alongside, then retirement and handover. Business-blocking forms are rebuilt and released first — if forms are down today, the useful question is time-to-first-form, and that is days, not weeks.
In SharePoint Online, no — nobody can. Microsoft stated there is no option to extend InfoPath Forms Services beyond the July 14, 2026 retirement, and we would rather tell you that plainly than sell a workaround that fails. On-premises farms keep working within their own support lifecycle, which buys sequencing time but is not a strategy.
Mostly yes, but as a redesign rather than a copy. Repeating sections map to galleries and child lists, conditional views to app screens, and code-behind logic to Power Fx and Power Automate. A few InfoPath habits — pixel-perfect print layouts, some XML data connections — have no clean equivalent, and the triage report names every form where the rebuilt behavior will differ so the owner approves the differences up front.
Everything: the rebuilt forms, flows, archives, and documentation live in your tenant. There is no proprietary runtime and no ongoing dependence on IT Partner — enhancements are available at our published rates if you want them, and your team can equally take the handover pack and run.