InfoPath Migration: Rebuild Your Forms in Power Apps Before the Platform Quits
InfoPath is retired, and Microsoft did not build a successor. That sentence deserves a moment, because it's an unusual one in enterprise software. Products get replaced; InfoPath was simply ended. There is no "new InfoPath" to upgrade to, no migration wizard that converts your forms, no tool that reads an .xsn file and produces a modern equivalent. Every InfoPath form in your environment is a rebuild — the only questions are when, in what order, and whether the rebuild happens on a schedule or after a failure.
If your organization runs on InfoPath forms — and many still do, quietly, in HR onboarding, safety inspections, purchase requests, field data collection — this page, part of our wider SharePoint practice, describes how to get out deliberately.
Why this is urgent, without embellishment
We won't invent deadlines, and this situation doesn't need them. The facts as Microsoft has stated them are enough:
- InfoPath is retired with no successor. Every form built on it is unsupported technical debt with a known expiration.
- The workflows behind the forms are going too. InfoPath forms rarely work alone; they submit into SharePoint Designer workflows. Designer 2010 workflows are already retired, and 2013 workflows are on borrowed time. A form whose workflow dies is a form that collects data into a void. The two retirements compound each other — which is why we treat forms and workflows as one program; see workflow modernization.
- SharePoint Server support windows are closing. Organizations running InfoPath against on-premises SharePoint are stacking an unsupported form technology on a platform whose own clock is running. See SharePoint migration for that half of the problem.
- Failure is silent and inconvenient. Retired form technology doesn't fail during planning meetings. It fails when a browser update, a patch, or an environment change breaks something nobody was watching — and the first symptom is a business process that stops mid-stride.
Organizations that move now choose their sequence, protect their data, and train their users properly. Organizations that wait do the same rebuild as an emergency, with a process down while they do it.
InfoPath to Power Apps: what the rebuild really is
The modern destination for InfoPath forms is Power Apps, usually paired with Power Automate for the routing and approvals the old Designer workflows handled. But "convert the form" is the wrong mental model. A good InfoPath exit is a redesign with the benefit of hindsight:
The form logic transfers as intent, not as code.
Rules, conditional sections, calculated fields, data validation — Power Apps does all of it, differently and generally better. We map what each form's logic was for, then implement that intent natively rather than imitating InfoPath's structure.
The data layer gets a real decision.
InfoPath forms typically wrote XML into SharePoint form libraries — a format that has aged badly and reports poorly. The rebuild is the moment to decide, form by form, whether data belongs in SharePoint lists or in Dataverse. We make that call based on volume, relationships, security requirements, and reporting needs, and we'll tell you plainly when the simpler option is the right one.
The historical data needs a plan of its own.
Years of submitted forms hold operational and compliance history. Depending on retention requirements, we extract and convert historical XML into the new structure, archive it in a searchable read-only form, or both. What we don't do is leave a decade of records stranded in a format nothing can open.
The process gets one hard look.
Many InfoPath forms encode a process as it worked years ago. Before rebuilding, we ask the owner one question: is this still how it should work? Sometimes the answer removes half the form.
How we run the exit
The engagement follows the IMP0WER GRID, our published methodology, laid out in full on the methodology page.
Gauge.
A complete inventory of every InfoPath form in the estate: where it lives, what it does, who owns the process, how often it's actually submitted, what workflows it triggers, and what data history sits behind it. Usage data is clarifying — a meaningful share of forms turn out to be dead already, which shrinks the real project before it starts.
Route.
Each form gets a disposition: rebuild in Power Apps, fold into another form or process, replace with something simpler (sometimes a list form is enough), or retire. Then a wave plan — highest-risk and highest-use forms first — with the data-layer decision and licensing implications settled per form, in plain English, before anything is built.
Install.
Forms rebuilt in waves, each against our published Ø Standard: a named owner, no personal-credential dependencies, auditable permissions, documentation a stranger could operate from, monitoring on the flows behind the form, and a support path after go-live. Old and new run in parallel through a validation window before the old form is switched off — no leaps of faith.
Distribute.
Users trained on the new forms, process owners handed run-books, historical data archived per the plan, and the InfoPath estate formally retired rather than left to rot.
Already broken? The rescue path
Retired form technology doesn't fail during planning meetings.
If a form has already failed — or the workflow behind it has — the order changes: stabilize the process first, even with an interim manual path, so the business keeps moving; protect the historical data; then rebuild properly. What we don't do is spend weeks trying to resuscitate retired technology. There's no version of that story that ends well, and paying for the attempt is money spent postponing the rebuild you'll do anyway.
Who does this work
Our founder has worked in SharePoint since 2010 — statewide government deployments, aerospace, defense, Fortune-100 retail — which means the InfoPath era isn't history to us; it's territory we built in the first time around. That matters in this niche specifically: exiting InfoPath well requires understanding how the forms were built, not just what should replace them. A founder leads every engagement, extended by the IMP0WER delivery team.
Where to start
The InfoPath inventory and exit map are core deliverables of the SharePoint Modernization Blueprint — a fixed-price assessment: $7,500 focused, $15,000–$25,000 deep for larger or regulated estates. If you engage us, 100% of the focused-tier fee is credited toward any implementation engagement of $25,000 or more signed within 90 days of your readout. You keep the census and the plan either way. We respond within one business day.
Frequently asked questions
Is there any tool that converts InfoPath forms to Power Apps automatically?
No — and be wary of anything marketed as one. Tools can inventory forms and extract their structure, which genuinely helps the census, but the rebuild itself is design work: form logic, data layer, and workflow all need human decisions. Anyone promising push-button conversion is selling you a demo, not an exit.
How many of our forms will actually need rebuilding?
Fewer than you fear, usually. The census consistently finds forms that are dead, duplicated, or replaceable with something far simpler than a custom app. The disposition step — rebuild, simplify, fold, retire — is where the project gets smaller. Paying for a census before committing to a rebuild count is the whole logic of assessment-first pricing.
What happens to years of submitted form data?
It gets a deliberate plan, form by form: convert into the new data structure where it needs to stay operational, archive read-only where it's compliance history, or both. Retention requirements drive the call. The one unacceptable outcome is discovering after retirement that a decade of records lives in a format nothing reads.
Do rebuilt forms need Premium Power Apps licensing?
It depends on the data layer and connectors each form needs — SharePoint-backed forms generally run on licensing you already own, while Dataverse-backed forms carry licensing implications we spell out before building. Licensing is settled per form in the Route phase, so it's an approved line item, not a surprise.
Our InfoPath forms run on SharePoint Server on-premises. Which comes first, the migration or the forms?
They're planned together. Forms are dispositioned inside the migration wave plan so nothing gets moved twice and nothing gets orphaned. Sometimes forms rebuild straight into SharePoint Online ahead of their site's wave; sometimes they follow it. The sequencing is exactly what the Blueprint works out.
Can we keep using InfoPath a bit longer while we plan?
You can — running forms don't stop the day you decide to leave. Plainly: every month on InfoPath is unsupported risk you're choosing to carry, and it's a reasonable choice only if it comes with a funded exit plan and a sequence. Carrying the risk with no plan isn't a decision; it's a default.