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.
Want this plan checked against your own forms and workflows? Ask for a technical assessment.
<#
.SYNOPSIS
Read-only inventory of InfoPath forms in a SharePoint Server farm.
.DESCRIPTION
Written to list form libraries, lists whose forms were customised in InfoPath,
data connection libraries, administrator-approved form templates and central
data connection files, with item counts and last-modified dates. Until it has
been run against a farm (see NOTES), its output is a starting inventory to
confirm, not a complete one. It reads and
writes nothing to the farm; its only output is a CSV file.
Applies to SharePoint Server 2016, 2019 and Subscription Edition. Run it in
the SharePoint Management Shell on a farm server, as an account that can read
every site collection.
It opens every site and every list, so on a large farm it takes time and
load: run it outside business hours.
.NOTES
Detecting InfoPath list forms reads the `_ipfs_infopathenabled` property that
InfoPath sets on a content type's resource folder when it customises a list
form. Microsoft does not document that property: confirm the result on a test
list before relying on it.
pH7x Systems has syntax-checked this script; it has not run it against a farm.
.OUTPUTS
A CSV file, infopath-inventory.csv by default.
#>
[CmdletBinding()]
param(
[string]$Path = (Join-Path -Path (Get-Location) -ChildPath 'infopath-inventory.csv')
)
if (-not (Get-Command -Name Get-SPSite -ErrorAction SilentlyContinue)) {
# SharePoint Server 2016 and 2019 ship a snap-in; Subscription Edition loads its module itself.
Add-PSSnapin -Name Microsoft.SharePoint.PowerShell -ErrorAction Stop
}
$rows = [System.Collections.Generic.List[object]]::new()
function Add-Row([string]$Kind, [string]$Site, [string]$Web, [string]$Name, $Items, $Modified) {
$rows.Add([pscustomobject]@{
Kind = $Kind
Site = $Site
Web = $Web
Name = $Name
Items = $Items
LastModified = $Modified
})
}
foreach ($site in Get-SPSite -Limit All) {
try {
foreach ($web in $site.AllWebs) {
try {
foreach ($list in $web.Lists) {
$kind = $null
if ($list.BaseTemplate -eq [Microsoft.SharePoint.SPListTemplateType]::XMLForm) {
$kind = 'Form library'
}
elseif ($list.BaseTemplate -eq [Microsoft.SharePoint.SPListTemplateType]::DataConnectionLibrary) {
$kind = 'Data connection library'
}
elseif ($list.ContentTypes | Where-Object { "$($_.ResourceFolder.Properties['_ipfs_infopathenabled'])" -eq 'True' }) {
$kind = 'InfoPath list form'
}
if ($kind) {
Add-Row $kind $site.Url $web.Url $list.Title $list.ItemCount $list.LastItemModifiedDate
}
}
}
finally {
$web.Dispose()
}
}
}
finally {
$site.Dispose()
}
}
# Templates a farm administrator uploaded through Central Administration: these can carry code.
foreach ($template in Get-SPInfoPathFormTemplate) {
$name = @($template.DisplayName, $template.Name) | Where-Object { $_ } | Select-Object -First 1
Add-Row 'Administrator-approved template' '' '' "$name" '' ''
}
# Data connection files stored centrally in the farm.
foreach ($file in Get-SPDataConnectionFile) {
$name = @($file.DisplayName, $file.Name) | Where-Object { $_ } | Select-Object -First 1
Add-Row 'Central data connection file' '' '' "$name" '' ''
}
$rows | Export-Csv -Path $Path -NoTypeInformation -Encoding UTF8
Write-Output "$($rows.Count) InfoPath items written to $Path"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 run | The product | InfoPath Forms Services |
|---|---|---|
| SharePoint Server 2016 | Out of support since 14 July 2026 | Out of support: Microsoft matched its support to the 2016 lifecycle |
| SharePoint Server 2019 | Out of support since 14 July 2026 | Deprecated for the 2019 release, and out of support with the product |
| SharePoint Server Subscription Edition | Supported, until at least 31 December 2035 | Deprecated, and supported only until 14 July 2026 |
| SharePoint Online | Supported | Microsoft'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.
| Replacement | Runs on | A cloud service | Fits |
|---|---|---|---|
| SharePoint's own list form, with column validation and column formatting | SharePoint Online and Subscription Edition | No | List forms that arrange fields and validate values |
| Power Apps customised list form | SharePoint Online | Yes | List forms with lookups, rules and conditional sections |
| Power Apps over SharePoint Server, through the on-premises data gateway | Data on the farm, the app in Microsoft 365 | Yes, a hybrid design | Cloud services allowed, data on premises |
| SharePoint Framework form | SharePoint Online; Subscription Edition with SPFx v1.5.1 from Version 23H1, v1.4.1 before | No | Conditional sections, repeating data, form libraries |
| An application for the logic, SharePoint for the data | On premises, or a service in the cloud | Depends where it is hosted | Code-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\userdo not work online and must becomei: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
- Products ending support in 2026
- What's deprecated or removed from SharePoint Server Subscription Edition
- What's deprecated or removed from SharePoint Server 2019
- Configure InfoPath Forms Services
- Migrate InfoPath forms to SharePoint
- InfoPath Forms Services differences between SharePoint Online and on premises
- SharePoint Framework platform compatibility
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