Assessment

Plan the move off InfoPath

Answer what you know about your forms and where they must run. The plan changes with your answers: the target architecture, the alternatives, the work and the tests.

Questionnaire-based. It reads your answers; it does not scan a farm or a tenant, and nothing you enter leaves your browser.

Where the forms run, and where they must go
Where do the forms run today?
Where must the replacement run?
May the solution use Microsoft cloud services (Power Apps, Power Automate, Azure)?

SharePoint Online implies yes. For an on-premises target, this decides whether cloud options can even be listed.

Which Subscription Edition feature update is, or will be, installed?

It sets the SharePoint Framework version you can build with: v1.5.1 from Version 23H1, v1.4.1 before it.

The forms
What kind of InfoPath forms are they?
How many forms?
How many are still in use?
What the forms depend on
What do the forms use? Select everything that applies.
Does a workflow run when a form is submitted?
People, data and constraints
Who fills in the forms?
How do people sign in to SharePoint today?
How critical are the processes behind the forms?
What must happen to forms already submitted?
Who will build the replacement?

Want this plan checked against your own forms and workflows? Ask for a technical assessment.

The planner above builds a plan from your answers. This reference sets out what it rests on: what Microsoft documents, platform by platform, and what each replacement can and cannot do.

What ended, and where

Where the forms runThe productInfoPath Forms Services
SharePoint Server 2016Out of support since 14 July 2026Out of support: Microsoft matched its support to the 2016 lifecycle
SharePoint Server 2019Out of support since 14 July 2026Deprecated for the 2019 release, and out of support with the product
SharePoint Server Subscription EditionSupported, until at least 31 December 2035Deprecated, and supported only until 14 July 2026
SharePoint OnlineSupportedMicrosoft's InfoPath migration page says only that the forms service "will be supported in Office 365 until at least the next major release of Office"; no Microsoft page found gives a date

The client. InfoPath 2013, the last release and the only designer for these forms, has been out of support since 14 July 2026.

Microsoft's pages disagree about Subscription Edition. The list of deprecated features says InfoPath Forms Services is deprecated and was supported until 14 July 2026. A Health Analyzer rule page says the service is removed and no longer supported. Both agree it is unsupported now; whether it is still present in a given build is something to check on your farm, not to assume.

What stops, and what does not

End of support is not a switch. Forms that open today keep opening the day after: what ends is fixes, security updates and Microsoft's help when something breaks. The debt is real all the same, because the forms sit on a service nobody maintains, and they block the next platform move.

That matters most before an upgrade. A farm moving from 2016 or 2019 to Subscription Edition carries its InfoPath forms onto a service that is out of support there too, so the replacement belongs in the upgrade plan, not after it.

The replacements, and where each runs

We know of no conversion tool, and Microsoft documents none: every form is rebuilt. The choice depends on what the form does and on where it must run, and both are settled before a form is rebuilt.

ReplacementRuns onA cloud serviceFits
SharePoint's own list form, with column validation and column formattingSharePoint Online and Subscription EditionNoList forms that arrange fields and validate values
Power Apps customised list formSharePoint OnlineYesList forms with lookups, rules and conditional sections
Power Apps over SharePoint Server, through the on-premises data gatewayData on the farm, the app in Microsoft 365Yes, a hybrid designCloud services allowed, data on premises
SharePoint Framework formSharePoint Online; Subscription Edition with SPFx v1.5.1 from Version 23H1, v1.4.1 beforeNoConditional sections, repeating data, form libraries
An application for the logic, SharePoint for the dataOn premises, or a service in the cloudDepends where it is hostedCode-behind, data connections, integrations

Power Apps, Power Automate and Microsoft Forms are Microsoft 365 services. They are not part of SharePoint Server, and a farm whose constraints keep data and processing on premises cannot adopt them. Microsoft's InfoPath guidance points to them, and to developer-built solutions for forms with extensive code; on premises, the second half of that advice is the one that applies.

Moving forms to SharePoint Online: documented traps

Microsoft documents differences between InfoPath Forms Services online and on premises that catch forms moved as they are:

  • UDCX data connections that contain explicit credentials or Secure Store details fail online, because the options they rely on are not enabled in the cloud.
  • Accounts written into forms as i:0#.w|domain\user do not work online and must become i:0#.f|membership|user@domain.
  • In form libraries, attachments are embedded in the XML file, so large attachments weigh on every form that carries them.

Finding the forms

On SharePoint Server, the planner's first step carries a read-only PowerShell inventory: form libraries, lists with InfoPath forms, data connection libraries, administrator-approved templates and central data connection files, with item counts and last-modified dates. It reads and changes nothing, and it says which of its checks rests on an undocumented property. It has been checked for syntax only and not yet run against a farm, so treat its output as a starting inventory to confirm, not as a complete one.

Most estates find that the forms worth rebuilding are far fewer than the forms present. The inventory's dates and counts are what separate the two.

What M365 Governance as Code can observe

  • It does not detect InfoPath forms.
  • It does not inventory SharePoint Designer solutions.
  • It can identify modernisation signals elsewhere in a tenant, such as classic publishing infrastructure or custom master pages, but not these technologies directly.

Primary Microsoft sources

Where this fits

The full picture of what ended and what to build on is in our analysis of the state of SharePoint in 2026.

This tool is free, and it stays free. If it saved you time, you can support its maintenance.

Buy me a coffee (opens in a new tab)João Lívio's page on buymeacoffee.com