Assessment
Plan the move off SharePoint Designer workflows
Answer what you know about your workflows 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 SharePoint 2010 and SharePoint 2013 workflows in a SharePoint Server farm.
.DESCRIPTION
Written to list the SharePoint 2010 workflow associations on sites, lists and list
content types, and the SharePoint 2013 workflow subscriptions, with what each is
attached to, whether it is enabled and its dates. Until it has been run against a
farm (see NOTES), its output is a starting inventory to confirm, not a complete one. It also saves a copy of each SharePoint 2013
workflow definition and each SharePoint Designer 2010 workflow file to a folder, to
review them and to keep them as a record before content moves. It reads and
writes nothing to the farm; its only outputs are a CSV file and that folder.
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
SharePoint 2013 workflows are read through the farm's workflow service. Where no
workflow engine is registered with the farm, the script says so in the CSV and
lists SharePoint 2010 workflows only. SharePoint 2013 workflows have no content
type scope, so content types are read for SharePoint 2010 workflows only.
The object model members it reads are documented in Microsoft's SharePoint
Server 2013 reference; Microsoft publishes no separate reference for 2016, 2019 or
Subscription Edition.
pH7x Systems has syntax-checked this script; it has not run it against a farm.
.OUTPUTS
workflow-inventory.csv and a workflow-definitions folder, in the current directory
by default.
#>
[CmdletBinding()]
param(
[string]$Path = (Join-Path -Path (Get-Location) -ChildPath 'workflow-inventory.csv'),
[string]$DefinitionFolder = (Join-Path -Path (Get-Location) -ChildPath 'workflow-definitions')
)
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
}
# The SharePoint 2013 workflow services live in their own assembly, which the shell does not load.
Add-Type -AssemblyName 'Microsoft.SharePoint.WorkflowServicesBase, Version=16.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c'
New-Item -ItemType Directory -Path $DefinitionFolder -Force | Out-Null
$rows = [System.Collections.Generic.List[object]]::new()
function Add-Row([string]$Platform, [string]$Scope, $Web, [string]$List, [string]$ContentType, [string]$Name,
$Enabled, $Running, $Created, $Modified, [string]$Detail, [string]$File) {
$rows.Add([pscustomobject]@{
Platform = $Platform
Scope = $Scope
Web = $Web.Url
List = $List
ContentType = $ContentType
Name = $Name
Enabled = $Enabled
RunningInstances = $Running
Created = $Created
Modified = $Modified
Detail = $Detail
SavedCopy = $File
})
}
# A file name for a saved copy: the web's id keeps copies from different sites apart.
function Save-Copy($Web, [string]$Name, [byte[]]$Bytes) {
$safe = ($Name -replace '[^\w\.\- ]', '_')
$target = Join-Path -Path $DefinitionFolder -ChildPath "$($Web.ID)-$safe"
[System.IO.File]::WriteAllBytes($target, $Bytes)
return $target
}
function Add-2010([string]$Scope, $Web, [string]$List, [string]$ContentType, $Association) {
$template = if ($Association.BaseTemplate) { $Association.BaseTemplate.Name } else { '' }
Add-Row 'SharePoint 2010' $Scope $Web $List $ContentType $Association.Name $Association.Enabled `
$Association.RunningInstances $Association.Created $Association.Modified "Template: $template" ''
}
foreach ($site in Get-SPSite -Limit All) {
try {
foreach ($web in $site.AllWebs) {
try {
# SharePoint 2010 site workflows are associated with the site itself.
foreach ($association in $web.WorkflowAssociations) { Add-2010 'Site' $web '' '' $association }
foreach ($list in $web.Lists) {
foreach ($association in $list.WorkflowAssociations) { Add-2010 'List' $web $list.Title '' $association }
foreach ($contentType in $list.ContentTypes) {
foreach ($association in $contentType.WorkflowAssociations) {
Add-2010 'Content type' $web $list.Title $contentType.Name $association
}
}
# SharePoint Designer 2010 keeps each workflow's files in the site's hidden Workflows library.
if ($list.BaseTemplate -eq [Microsoft.SharePoint.SPListTemplateType]::NoCodeWorkflows) {
foreach ($item in $list.Items) {
if ($item.File -and $item.File.Name -like '*.xoml') {
$saved = Save-Copy $web "$($item.File.ParentFolder.Name)-$($item.File.Name)" $item.File.OpenBinary()
Add-Row 'SharePoint 2010' 'Definition' $web '' '' $item.File.ParentFolder.Name '' '' '' `
$item.File.TimeLastModified 'SharePoint Designer workflow file' $saved
}
}
}
}
# SharePoint 2013 workflows, through the farm's workflow service.
$manager = New-Object -TypeName Microsoft.SharePoint.WorkflowServices.WorkflowServicesManager -ArgumentList $web
if (-not $manager.IsConnected) {
Add-Row 'SharePoint 2013' 'Site' $web '' '' '' '' '' '' '' 'No workflow engine is registered for this site' ''
continue
}
$definitions = @{}
foreach ($definition in $manager.GetWorkflowDeploymentService().EnumerateDefinitions($false)) {
$saved = Save-Copy $web "$($definition.DisplayName)-$($definition.Id).xaml" ([System.Text.Encoding]::UTF8.GetBytes([string]$definition.Xaml))
$definitions[$definition.Id] = $saved
Add-Row 'SharePoint 2013' 'Definition' $web '' '' $definition.DisplayName '' '' '' '' `
"Published: $($definition.Published); restricted to: $($definition.RestrictToType)" $saved
}
$subscriptions = $manager.GetWorkflowSubscriptionService()
# List workflows, list by list.
foreach ($list in $web.Lists) {
foreach ($subscription in $subscriptions.EnumerateSubscriptionsByList($list.ID)) {
Add-Row 'SharePoint 2013' 'List' $web $list.Title '' $subscription.Name $subscription.Enabled '' '' '' `
"Definition: $($subscription.DefinitionId)" $definitions[$subscription.DefinitionId]
}
}
# Site workflows: a site workflow's event source is the site itself.
foreach ($subscription in $subscriptions.EnumerateSubscriptions()) {
if ($subscription.EventSourceId -eq $web.ID) {
Add-Row 'SharePoint 2013' 'Site' $web '' '' $subscription.Name $subscription.Enabled '' '' '' `
"Definition: $($subscription.DefinitionId)" $definitions[$subscription.DefinitionId]
}
}
}
catch {
Add-Row '' 'Error' $web '' '' '' '' '' '' '' "Could not read this site: $($_.Exception.Message)" ''
}
finally {
$web.Dispose()
}
}
}
finally {
$site.Dispose()
}
}
$rows | Export-Csv -Path $Path -NoTypeInformation -Encoding UTF8
Write-Output "$($rows.Count) rows written to $Path; saved copies in $DefinitionFolder"This page is for teams that still run business processes on SharePoint 2010 or SharePoint 2013 workflows, most of them built in SharePoint Designer. Several things ended, on different dates and with different consequences, and the answer depends on where the workflows must run next: SharePoint Online, or SharePoint Server Subscription Edition on premises.
What ended, and where
| What | Where | Status |
|---|---|---|
| SharePoint Designer 2013 | Every platform | Out of support since 14 July 2026. It was the last release. |
| SharePoint Server 2016 and 2019 | On premises | Out of support since 14 July 2026: the products themselves, and every workflow on them. |
| SharePoint 2010 workflows | Subscription Edition | Deprecated, and supported only until 14 July 2026; out of support since. |
| Microsoft Workflow Manager | Subscription Edition | Supported as a SharePoint component until 14 July 2026, and no longer installable. |
| SharePoint 2013 workflows | Subscription Edition | Supported on SharePoint Workflow Manager, which follows the support timeline of the SharePoint Server it serves. |
| SharePoint 2010 workflows | SharePoint Online | Turned off for new tenants on 1 August 2020, removed from existing tenants on 1 November 2020. |
| SharePoint 2013 workflows | SharePoint Online | Deprecated in April 2023, turned off for new tenants on 2 April 2024, fully retired on 2 April 2026. |
A tool going out of support and a runtime being switched off are different problems. The first is a risk you carry. The second is an outage you schedule.
What stops, and what does not
In SharePoint Online, nothing classic runs any more. SharePoint 2013 workflows stopped on 2 April 2026, and SharePoint 2010 workflows in 2020. A process that depended on one does not run slowly or partially; it does not run.
On SharePoint Server 2016 and 2019, Microsoft has not switched anything off, but the products themselves are out of support: every workflow on them runs on software with no fixes and no security updates.
On Subscription Edition, the answer depends on the platform.
- SharePoint 2013 workflows are supported, on SharePoint Workflow Manager. Microsoft Workflow Manager can no longer be installed, and its support as a SharePoint component ended on 14 July 2026, so a farm still running it has an engine to replace. Until it does, Microsoft's Subscription Edition update notes say the classic engine needs server debug flag 53601 set to keep working. Microsoft documents an upgrade to SharePoint Workflow Manager from any version of Microsoft Workflow Manager. Moving to a new farm, the six workflow databases and the App Management database move with the content databases, under the same names, and the workflow service is registered again with the same scope name: without the App Management database, every workflow created before the move fails.
- SharePoint 2010 workflows are out of support since 14 July 2026. Microsoft records an end of support rather than a removal, but its August 2026 update notes say the SharePoint 2010 workflow feature "will be disabled starting with the September 2026 Public Update", and that
Enable-SPLegacyWorkflowenables it for a site collection. Enabling it does not restore support. - SharePoint Designer 2013 is out of support as well. Microsoft states that Visual Studio can still create and edit SharePoint 2013 workflows after that date.
SharePoint Workflow Manager has its own requirements: it is installed separately, on an odd number of hosts, with Azure Service Fabric Runtime 9.1.1583.9590 or later, and SharePoint 2013 workflows need the App Management and Subscription Settings services in the farm.
Microsoft's pages disagree in places. The Subscription Edition list gives 14 July 2026 as the end of support for SharePoint 2010 workflows and still files them, and Microsoft Workflow Manager, as deprecated; another page dates their deprecation on premises to 16 July 2026; and an older workflow page that applies to Subscription Edition still points SharePoint 2013 workflows at Microsoft Workflow Manager. This page follows the Subscription Edition list.
Where each kind of workflow goes
| Workflow | Moving to SharePoint Online | Staying on Subscription Edition |
|---|---|---|
| SharePoint 2013, built in SharePoint Designer | Power Automate: migrated with the SharePoint Migration Tool where it supports the actions, rebuilt where it does not | Kept, on SharePoint Workflow Manager, and maintained in Visual Studio |
| SharePoint 2010, from a template or SharePoint Designer | Power Automate, the same way | Rebuilt: as SharePoint 2013 workflows on SharePoint Workflow Manager, or as server-side code when the logic needs it |
| Built in Visual Studio, with code | Rebuilt as a flow, with the code moved into a service the flow calls | SharePoint 2013 workflows kept; SharePoint 2010 ones rebuilt |
| Built with a third-party product | The vendor's own statement | The vendor's own statement |
Where an on-premises organisation allows cloud services, Microsoft also recommends Power Automate through the on-premises data gateway to users of SharePoint 2010 workflows. Two cautions: the SharePoint connector's documentation names only SharePoint 2016 and 2019 farms, so test it against Subscription Edition before relying on it, and the gateway is a premium feature that moves processing off the premises.
The planner above turns these rows into a plan for your own answers.
Moving to SharePoint Online: what the migration tool carries
The SharePoint Migration Tool (SPMT) migrates workflows from SharePoint Server 2010, 2013, 2016 and 2019 to Power Automate; its pages do not list Subscription Edition as a source. Its boundaries are published, and they are the difference between a migration plan and a surprise.
What it carries
- SharePoint Server 2010 out-of-the-box workflows: Approval, Collect Feedback, Collect Signature and Three state.
- SharePoint Designer 2010 and 2013 workflows.
- List, library and content type workflows.
- Workflow definitions and associations.
What it does not carry
- Site workflows. Only list, library and content type workflows are in scope.
- Workflow history data. Definitions and associations move; the run history does not.
- Workflows in progress. Instances that are running are not migrated.
- A published list of actions, including
Call HTTP Web Service, the dictionary actions,Loop in time,Loop with Condition, parallel blocks,Copy document, the record and document set actions, theWait foractions andStart a List workflow. The full table is documented; pauses for a duration or until a date do migrate. By default the tool stops and reports an error when it meets an unsupported action; it can be told to convert unsupported actions to a Compose action instead, which preserves the shape of the flow and not its behaviour.
Run it with Only perform scanning first: its workflow scan report lists each workflow's version, association type and unsupported actions. Migrated flows arrive in a Power Automate solution, owned by the account that migrated them and turned off until that owner turns them on, and Microsoft warns that a converted flow may not behave exactly like the original.
A flow is not a workflow with a new name. A flow run, pending approvals included, times out after 30 days, and its run history is kept for 30 days: long approvals and waits are redesigned, and history that matters is exported before the move.
The honest planning assumption: workflows that use only core actions migrate; workflows built around HTTP calls, dictionaries or loops are rebuilt.
Finding the workflows
On SharePoint Server, the planner's read-only inventory script is written to list the SharePoint 2010 and SharePoint 2013 workflows on a farm, Subscription Edition included, and to save a copy of their definitions before anything moves. 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. For a source on SharePoint Server 2010 to 2019 moving online, the migration tool's scan adds which actions it cannot carry.
Two older instruments are gone: the SharePoint Migration Assessment Tool is no longer available since 1 October 2026, and the Microsoft 365 Assessment tool's Workflow 2013 module, which covered SharePoint Online only, was retired in June 2026.
What M365 Governance as Code can observe
- It does not detect SharePoint 2013 workflows.
- It does not inventory workflow definitions.
- It does not determine migration readiness.
- Workflow retirement remains a discovery activity, which the planner's inventory script supports on SharePoint Server.
Primary Microsoft sources
- What's deprecated or removed from SharePoint Server Subscription Edition
- Install and configure workflow for SharePoint Server
- Update to SharePoint Workflow Manager when upgrading farms
- SharePoint connector reference
- SharePoint Workflow Manager lifecycle
- Microsoft Workflow Manager 1.0 lifecycle
- Modernize SharePoint 2013 workflows
- Migrate from classic workflows to Power Automate flows
- Overview: migrate SharePoint Server workflows to Power Automate
- Designer workflow actions not migrated
- Power Automate: limits of automated, scheduled and instant flows
- SharePoint Designer 2013 lifecycle
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