InfoPath to Power Apps migration services
A fixed-fee forms replacement for the SharePoint lists and libraries you already run, delivered by senior US-based Microsoft engineers. We inventory every InfoPath template, rebuild the ones people still submit as Power Apps forms with their rules, data connections and routing intact, and convert the XML history you need to keep — one written price, typical delivery in 2–4 weeks, 30 days of hypercare included. This is not a new-app build and not a move off another product; it is the forms layer, put back where your data already lives.
Representative dashboard — sample data
What you get
An InfoPath template bundled the layout, the validation rules, the data connections and the submit logic into one file. Power Apps keeps each of those visible and editable, which is most of the rebuild.
Every template in every form library and every customized list form is catalogued with its last submission date and owner. Forms nobody has used since the last reorg are retired on purpose rather than rebuilt out of habit.
Where InfoPath customized a list form, the list, its columns and its permissions already exist. The new Power Apps form is attached to that list, so views, alerts and existing flows keep working the day it goes live.
Templates that saved one XML file per submission get a designed list with typed columns instead, so the fields become sortable, filterable and reportable rather than locked inside a document nobody can query.
Conditional formatting, validation rules, multi-view templates and repeating tables each have a Power Apps equivalent. We map every rule to it in writing so the behaviour your staff rely on is preserved, not approximated.
Email-on-submit, approval chains and the SharePoint Designer workflows that ran behind the form are rebuilt as Power Automate flows with their trigger, condition and recipients documented, and editable by someone other than the original author.
Past submissions are either extracted into list columns beside the new records or left in a read-only archive library, depending on whether anyone reports on them. Either way, nothing is deleted to make the rebuild tidier.
How it works
A free consultation plus a pass over your form libraries, customized list forms, data connections and the workflows behind them tells us which forms still run a process. You get a written scope, one fixed price and a delivery date.
List forms are rebuilt in Power Apps on their existing list. Form-library templates get a designed list first, then the form. Rules, views and submit logic are recreated, routing moves to Power Automate, and your form owners review working screens early.
Each form goes live with its history handled as agreed, the old library set to read-only, and documentation your own admins can maintain. We stay on for 30 days of hypercare after the last form is switched over.
Two deadlines landed on the same day. Microsoft's lifecycle entry for InfoPath 2013 (opens in new tab) shows extended support for the desktop designer and filler ending on 14 July 2026, and Microsoft retired InfoPath Forms Services in SharePoint Online on the same date. Forms Services was the piece that rendered a browser-enabled template as a web form, so its removal is the reason a form that opened in June now does not. The same date closed the door for InfoPath Forms Services on SharePoint Server 2016, 2019 and Subscription Edition, which is why an on-premises farm gets no reprieve either; if your farm is still running, our SharePoint Server to SharePoint Online migration handles the forms as one part of the larger move.
What did not go anywhere is your data. A customized list form always wrote its values into ordinary list columns, and those columns, their views and their permissions are untouched. A form library saved each submission as an XML file, and those files are still sitting in the library with their metadata. The rebuild therefore starts from a much better place than a migration from another product: the container is there, the history is there, and in most cases the people who use the form are the same people who used it in June. What is missing is the form itself, and that is what this service puts back.
Almost every InfoPath template is built from the same dozen features. The table is the mapping we work from, and the inventory in your written scope is a filled-in copy of it, form by form.
| InfoPath feature | What it did | Where it lands after the rebuild |
|---|---|---|
| Customized list form | Replaced the default new, edit and display forms on a SharePoint list | A Power Apps form attached to the same list, built the way Microsoft documents for customizing a list form (opens in new tab) |
| Form library template (.xsn) | Saved one XML document per submission, with promoted fields as library columns | A designed SharePoint list with typed columns, plus a Power Apps form on top; the library becomes a read-only archive |
| Rules: validation, formatting, actions | Field-level checks, show or hide logic, and set-a-value behaviour | Power Fx formulas on the control's properties, listed rule by rule in the scope so nothing is silently dropped |
| Multiple views | One template showing different layouts to requester, approver and finance | Separate screens or role-driven visibility in a single form, chosen by how different the views really are |
| Repeating tables and sections | Line items inside one submission, such as expense rows or attendees | A gallery bound to a child list with a lookup to the parent record, so line items are queryable rather than buried in XML |
| Data connections | Lookups into other lists, web services or SQL for drop-down values and defaults | Standard SharePoint connector for list lookups; SQL and web services assessed for connector type and its licensing impact |
| Submit options and email on submit | Where the form went when the button was pressed, and who was told | The form saves to the list; notification and routing move to a Power Automate flow triggered on item created |
| SharePoint Designer or 2010 workflow behind the form | Approval, status updates and task assignment after submission | A Power Automate approval flow that records the decision, the comment and the timestamp on the item |
| Digital signatures and code-behind | Signed sections and managed code inside the template | Reviewed individually; usually replaced by an approval record with identity and timestamp, or by a flow step, and scoped as a separate line |
| Historical XML submissions | Years of completed forms stored as documents | Extracted into list columns where reporting or audit needs them; otherwise retained in a read-only library |
Two rows decide the timeline. If your forms are customized list forms with modest rule logic, the project is mostly rebuilding screens and it moves quickly. If they are form-library templates with repeating sections, external data connections and a workflow behind each one, there is a data model to design before any form can exist, and we price that as the real scope it is rather than discovering it in week three.
Most InfoPath rebuilds do not need a new license. A Power Apps form on a SharePoint list uses the standard SharePoint connector, and the Power Apps use rights that come with most Microsoft 365 business and enterprise plans cover exactly that pattern; Microsoft's own summary of Power Apps licensing and plans (opens in new tab) sets out the boundary. A standalone Power Apps license enters the picture when a form must read from SQL Server or another premium connector, or when the data belongs in Dataverse because it is genuinely relational and needs row-level security. Some InfoPath estates do cross that line, particularly where a data connection reached into an ERP. We say which side of it each form sits on in the written scope, so the licensing decision is made before work starts and not after the first invoice.
We publish several pages that end in a Power App, and they are not interchangeable. The differences are in where you start and how much of the data model already exists.
| Your starting point | What the work mostly is | The right service |
|---|---|---|
| InfoPath forms on SharePoint lists or libraries that stopped opening | Rebuilding the form, its rules and its routing on data that already exists | This page |
| Nintex workflows and Nintex Forms that stopped running in April 2026 | Inventorying a retired workflow product and rebuilding each workflow as a cloud flow, with its form rebuilt in Power Apps | Nintex to Power Automate migration services |
| Sheets, forms and alerts living in Smartsheet | Designing a data layer first, then screens and flows, then cancelling a subscription | Smartsheet to Power Apps migration services |
| A process with no system behind it yet, or a spreadsheet that broke | Mapping the workflow and building an application from scratch | Power Apps consulting |
| A whole on-premises SharePoint farm to move, forms included | Farm inventory, destination design and staged content migration, with forms as one workstream | SharePoint Server to SharePoint Online migration |
This page is for an organization of roughly 20 to 500 people whose SharePoint Online or SharePoint Server estate carried a handful of InfoPath forms that mattered: an expense claim, a new-hire request, a safety inspection, a purchase requisition, a change request with an approval chain behind it. The usual trigger is blunt. Someone tried to submit one in July and it did not open, and the interim fix has been email or a shared spreadsheet ever since. If that describes you, the forms are the scope, the lists are already there, and the work is measured in weeks.
Ongoing app work once the forms are back sits under our custom Power Apps development service. The approval and notification flows that replace your submit logic are the territory of Power Automate approval workflow consulting, and if the lists and libraries the forms sit on need restructuring, permissions cleaned up or a site redesigned around them, that is shaped by our SharePoint intranet and document management consulting. We serve all US states remotely from our Orange County, CA base.
Most InfoPath estates sort into three phases. The table shows scope and typical timeline rather than prices, because an honest number requires reading your templates first, which is the same principle described on how our fixed-fee process works.
| Phase | Scope | Typical timeline | Fee |
|---|---|---|---|
| Phase 1 — inventory and the form that hurts most | Every template and customized list form catalogued with owner and last use; the highest-traffic form rebuilt in Power Apps with its rules and routing, reviewed by the people who submit and approve it | About the first week | Fixed fee — scoped after your free consultation |
| Phase 2 — the remaining active forms | Form-library templates given a designed list, repeating sections rebuilt as child lists, data connections re-pointed, Designer workflows rebuilt as approval flows, historical XML extracted where agreed | Weeks 2–3 | Fixed fee — scoped after your free consultation |
| Phase 3 — cutover, archive and handover | Old libraries set to read-only, unused forms retired by agreement, admin documentation and a short owner walkthrough, then 30 days of hypercare | Week 4 and close-out | Fixed fee — scoped after your free consultation |
Everything produced is yours from the first day. The forms, the lists, every flow and the documentation live in your own Microsoft tenant, never in ours, and your own admins can edit any of it after we leave.
Related services
Fixed-fee app development for the builds that start from a process rather than from a retired form.
Approvals, notifications and routing built as flows — the layer that replaces InfoPath submit logic and Designer workflows.
The lists, libraries, permissions and site structure your rebuilt forms sit on.
How an approval chain that used to run behind a form is rebuilt as a flow.
How to pick the form worth rebuilding first instead of the loudest one.
When a packaged product is the better answer, and when building genuinely wins.
FAQ
No. There is no Microsoft converter, and the third-party tools that exist import fields, not behaviour. We read each form template, list its fields, rules, data connections and views, then rebuild it as a Power Apps form on the same SharePoint list or a new list designed for it. The XML data stays where it is.
Two things ended on the same day. InfoPath 2013 left extended support, and Microsoft retired InfoPath Forms Services in SharePoint Online, the component that rendered your forms in the browser. The form libraries and their XML files remain in your tenant, but the forms themselves no longer open in the browser, so nothing new is being submitted through them.
Usually not for list forms. A Power Apps form customized on a SharePoint list uses the standard SharePoint connector, which the Power Apps rights included with most Microsoft 365 business and enterprise plans already cover. A standalone Power Apps license only enters the picture when a form needs Dataverse or a premium connector, and we flag that in the scope.
It is XML, one file per submission, and it stays readable in the library after the rebuild. Where the history matters for reporting or audit, we extract the fields into columns on the new list so old and new records sit in one view. Where it does not, the library is set to read-only and kept as an archive.
Most projects run two to four weeks and are quoted as one fixed fee after a free consultation. The number is driven by how many forms are still genuinely used, how much rule and data-connection logic each one carries, and whether historical submissions need to become list data. Thirty days of hypercare follow go-live.
No. This service replaces forms on SharePoint lists and libraries you already run, so the data model mostly exists and the work is the form, its rules and its routing. The Smartsheet migration moves data out of another product first, and Power Apps consulting builds a new application from a process. Pick the page that matches your starting point.
Book a free consultation
Tell us what you’re trying to fix — a report, an approval process, an intranet, a Copilot rollout. We scope it as a fixed-fee project, you approve, and a senior engineer delivers in 2–4 weeks.
The fastest way to reach us is the form — tell us the task and we’ll reply within one business day.