Your InfoPath migration,
mapped.
Microsoft has retired InfoPath. If your team has decided to move your forms off it, this guide brings the dates, the replacement options, and what a rebuild actually involves into one place, each sourced to Microsoft.
InfoPath Forms Services removed
Microsoft removed InfoPath Forms Services from SharePoint Online. No extension was offered.
Removed July 14, 2026Microsoft removed InfoPath Forms Services in SharePoint Online on this date. Microsoft had stated there would be no option to extend it. Microsoft
Publishing blocked earlierAfter May 18, 2026, you can no longer publish new or updated InfoPath forms, ahead of the full removal. Microsoft
InfoPath 2013 is the final versionThere is no InfoPath 2016 or later. The client and Forms Services reached end of support together in July 2026. Microsoft
Existing data stays readableAfter removal you cannot create, edit or submit forms, but you can still view and export existing form data. Microsoft
No automated converterMicrosoft's recommended replacements are Power Apps, Microsoft Forms and Power Automate. Forms are rebuilt, not converted.
The Complete InfoPath
Exit Playbook
The dates, the replacement options (Power Apps, Microsoft Forms, Power Automate), a form-by-form triage method, and what a rebuild actually involves. Written for teams running the whole migration, not just reading about it.
Get the playbook
Enter your work email and it opens immediately, no waiting on a follow-up.
By submitting, you agree to be contacted about this. See our Legal & Disclaimers.
No spam. Unsubscribe anytime.
InfoPath has been retired
InfoPath was Microsoft's forms tool built into SharePoint. It has now been wound down, and SharePoint Online is where the hard date landed.
InfoPath Forms Services
This is where the firm deadline applied. Forms Services was removed on July 14, 2026, with publishing of new or updated forms blocked from May 18, 2026. No extension was offered.
InfoPath 2013 client
InfoPath 2013 is the last release; there is no newer version. The client reached end of support in July 2026, so it no longer receives updates and fixes.
On-premises Forms Services
On-premises InfoPath is tied to your SharePoint Server edition's lifecycle rather than the July 2026 online date. Confirm your server's support timeline before planning.
Existing submissions
Already-submitted form data remains viewable and exportable after retirement. What stops is authoring and new submissions, so plan how existing records are preserved.
Which environment are you actually on?
Tick everything that applies, then generate a summary tailored to your setup.
…
Get this as a PDF
A short summary of what applies to your setup, sent to your inbox.
By submitting, you agree to be contacted about this. See our Legal & Disclaimers.
The dates that matter
Two Microsoft-set dates drive InfoPath planning in SharePoint Online. Confirm both against Microsoft's own message before acting.
Publishing of new and updated forms blocked
Ahead of full removal, organisations could no longer publish new or changed InfoPath forms to SharePoint Online. Microsoft
InfoPath Forms Services removed; client end of support
Forms Services was removed from SharePoint Online with no extension, and the InfoPath 2013 client reached end of support. Microsoft
What's driving the 2026 move
You've made the decision to move off InfoPath. This section covers the context behind that decision and the factors worth carrying into your planning, each attributed to its source.
The deadline left no choice
For forms still live in SharePoint Online, the Microsoft retirement schedule was an operational hard stop. Publishing froze on May 18, 2026, and Forms Services was removed on July 14, 2026, after which authoring and submission stopped entirely.
No converter, so a rebuild is required
There is no automated path from an InfoPath form to Power Apps, Microsoft Forms or a SharePoint list form. Every form is recreated by hand, which is the main driver of project timeline and cost.
The forms model changes
Power Apps uses a different design paradigm to InfoPath's XML-based forms. Practitioners report that rules, data connections and validation logic need re-thinking, not just re-drawing, especially for complex forms.
Forms are often more embedded than expected
InfoPath forms tend to be wired into approval chains, list workflows and other business processes over the years. Retirement risk is rarely just the form; it's what depends on it.
Where InfoPath forms go next
Microsoft splits what InfoPath did as one tool across a few modern services. The right mix depends on each form's complexity.
Power Apps
Microsoft's primary recommendation for logic-heavy forms: multi-section layouts, rules, and data connections. This is where most non-trivial InfoPath forms land.
Microsoft Forms
Well suited to straightforward surveys and lightweight data collection where you don't need complex logic or layout.
SharePoint list forms
For forms that sit directly on a SharePoint list, the modern list form (customisable with Power Apps) is often a straightforward replacement.
Power Automate
The rules, routing and workflow that InfoPath handled inline are rebuilt as Power Automate flows alongside the new form.
How to route each form
Don't default every form to Power Apps. Score each one against the same questions and let the answer decide the target.
- →Does the form need conditional logic, multiple sections or data connections, or is it a flat list of fields?
- →How many people actually use this form, and when did it last receive a real submission?
- →Does it feed a workflow or approval chain that has to be rebuilt alongside it?
- →Is the data it collects still needed, or is the form itself a candidate for retirement?
- →Who will own and maintain the rebuilt version: a citizen developer or a professional one?
- →What's the cost of rebuilding this form versus the cost of simply retiring it?
What an InfoPath migration involves
The move is a rebuild, not a conversion. A structured pass keeps it predictable and stops you rebuilding forms nobody uses.
Inventory every form
Catalogue InfoPath forms across sites and libraries, including where each is published and how often it's used.
Triage
Retire forms that are unused or duplicated before rebuilding. This is the biggest single lever on effort.
Classify by complexity
Route simple forms to Microsoft Forms or list forms, and complex, logic-heavy forms to Power Apps.
Rebuild the form
Recreate layout, fields and rules on the target. There is no automated converter, so expect hand-rebuilding.
Reconnect the logic
Rebuild InfoPath rules and routing as Power Automate flows and data connections.
Preserve existing data
Plan how already-submitted records are retained or exported, since new submissions stop after removal.
Test and cut over
Validate each rebuilt form with real users and switch over before the July 2026 date.
“While the URLs are correct, when I go to publish I am getting an error stating that the library doesn't exist.”
Playbooks, guides and templates
Everything you need to plan and run the migration, in one place.
The InfoPath Exit and Migration Playbook
A field manual: the deadline, why teams move, destination options, and a six-phase method.
View the PDFarrow_forwardThe Step-by-Step Migration Guide
The sequence in order, with the trap to avoid at each step.
View the PDFarrow_forwardMigration Cost & Effort Estimator
Build a defensible number: form volume, complexity mix, and rebuild hours.
View the PDFarrow_forwardForm Inventory & Readiness Template
Inventory, score, and triage every form before you migrate.
View the PDFarrow_forwardThe InfoPath Exposure Report
Which 2026 dates apply to your setup, and recommended next steps.
View the PDFarrow_forwardQuestions teams ask
Drawn from Microsoft's guidance and practitioner write-ups, answered plainly.
What happened on July 14, 2026?expand_more
InfoPath Forms Services was removed from SharePoint Online. You can no longer create, edit or submit InfoPath forms. You can still view and export data from forms already submitted.
Can I extend InfoPath past 2026?expand_more
Not in SharePoint Online. Microsoft has stated there is no option to extend InfoPath Forms Services beyond July 14, 2026.
Is there a tool that converts InfoPath to Power Apps?expand_more
No automated converter exists. Microsoft recommends rebuilding forms on Power Apps, Microsoft Forms or SharePoint list forms, with Power Automate for the logic.
What does Microsoft recommend as a replacement?expand_more
A combination: Power Apps for complex forms, Microsoft Forms for simple data collection, and Power Automate for the workflow InfoPath handled inline.
We run InfoPath on SharePoint Server. Are we affected by the July date?expand_more
The July 2026 removal is specific to SharePoint Online. On-premises InfoPath follows your SharePoint Server edition's own lifecycle, so confirm that timeline separately.
How long does an InfoPath migration actually take?expand_more
It depends on how many forms are genuinely active and how complex they are, which is why an inventory and triage pass comes first. Simple forms move quickly; forms with heavy conditional logic or data connections take longest.
Should we migrate every form, or retire some instead?expand_more
Retire what you can. Many InfoPath estates carry forms that are rarely used or duplicated. Removing them before rebuilding is the single biggest lever on effort and cost.
Every source we pulled from
Grouped by who published it. Confirm the dates against Microsoft's own message before acting.