Updated September 2026
SharePoint 2010 workflows were retired from Microsoft 365 in 2020, and SharePoint 2013 workflows were fully retired from Microsoft 365 on April 2, 2026. But the situation for on-premises SharePoint is different.
For organizations running SharePoint Server on-premises, the retirement timeline depends on the SharePoint Server version and the workflow technology being used. Microsoft supported SharePoint 2010 workflows on SharePoint Server 2016 and SharePoint Server 2019 through the end of those products’ support lifecycles. SharePoint Server Subscription Edition supported SharePoint 2010 workflows until July 14, 2026.
If your organization still uses SharePoint 2010 or SharePoint 2013 workflows, now is the time to identify those workflows and plan their replacement or migration.
This guide explains the SharePoint 2010 and 2013 workflow retirement timelines, what retirement means for on-premises SharePoint, which versions are affected, and what you can use instead.
SharePoint 2010 Workflow Retirement at a Glance
| Environment | SharePoint 2010 workflow status |
|---|---|
| SharePoint Online | Retired November 1, 2020 |
| New Microsoft 365 tenants | Turned off August 1, 2020 |
| SharePoint Server 2016 | Supported through the SharePoint Server 2016 lifecycle |
| SharePoint Server 2019 | Supported through the SharePoint Server 2019 lifecycle |
| SharePoint Server Subscription Edition | Support ended July 14, 2026 |
The most important distinction is SharePoint Online versus SharePoint Server on-premises.
Microsoft retired SharePoint 2010 workflows from SharePoint Online in 2020. For on-premises SharePoint, Microsoft maintained its previous support posture for SharePoint 2010 and SharePoint 2013 workflows on SharePoint Server 2016 and SharePoint Server 2019 through 2026.
Microsoft’s current documentation for SharePoint Server Subscription Edition states that SharePoint 2010 workflows were deprecated but remained supported through July 14, 2026. After that date, they are no longer supported.
Is SharePoint 2010 Workflow Retired On-Premises?
Yes, SharePoint 2010 workflows are now beyond their supported lifecycle for on-premises SharePoint environments that have reached the applicable Microsoft support deadline.
However, “retired” needs to be understood in context.
Microsoft’s 2020 SharePoint 2010 workflow retirement announcement applied to SharePoint in Microsoft 365. Microsoft turned off SharePoint 2010 workflows for new Microsoft 365 tenants on August 1, 2020, and removed the SharePoint 2010 workflow services from existing tenants on November 1, 2020.
On-premises SharePoint followed a different support model.
Microsoft stated that SharePoint 2010 and SharePoint 2013 workflows would continue to be supported on SharePoint Server 2016 and SharePoint Server 2019 through 2026.
For SharePoint Server Subscription Edition, Microsoft specifically stated that SharePoint 2010 workflows would remain supported until July 14, 2026. After that date, Microsoft no longer supports SharePoint 2010 workflows on Subscription Edition.
Therefore, organizations still running SharePoint 2010 workflows on-premises should treat those workflows as legacy technology and begin or continue a modernization strategy.
When Was SharePoint 2010 Workflow Retired?
The SharePoint 2010 workflow retirement date depends on whether you are using SharePoint Online or SharePoint Server.
SharePoint Online
Microsoft’s SharePoint 2010 workflow retirement occurred in two stages:
- August 1, 2020: SharePoint 2010 workflows were turned off for newly created Microsoft 365 tenants.
- November 1, 2020: SharePoint 2010 workflow services were removed from existing Microsoft 365 tenants.
After November 1, 2020, existing SharePoint 2010 workflows could no longer run in SharePoint Online.
SharePoint Server On-Premises
The on-premises timeline was different.
SharePoint 2010 workflows continued to be supported on SharePoint Server 2016 and SharePoint Server 2019 through the applicable SharePoint Server lifecycle.
SharePoint Server 2016 reached the end of its extended support period on July 14, 2026, while SharePoint Server 2019 reached the end of its extended support period on July 14, 2026.
For SharePoint Server Subscription Edition, Microsoft explicitly set July 14, 2026 as the end of support for SharePoint 2010 workflows.
SharePoint 2010 Workflow Retirement Timeline
The following timeline summarizes the major milestones.
| Date | Event |
|---|---|
| August 1, 2020 | SharePoint 2010 workflows turned off for new Microsoft 365 tenants |
| November 1, 2020 | SharePoint 2010 workflow services removed from existing Microsoft 365 tenants |
| July 14, 2026 | SharePoint Server 2016 and SharePoint Server 2019 reached the end of extended support |
| July 14, 2026 | SharePoint Server Subscription Edition support for SharePoint 2010 workflows ended |
| 2026 and beyond | Organizations using legacy SharePoint 2010 workflows should plan migration or replacement |
Microsoft recommends migrating SharePoint 2010 workflows to Power Automate or another supported solution in Microsoft 365.
What About SharePoint 2013 Workflow Retirement?
SharePoint 2013 workflows followed a later retirement schedule in Microsoft 365.
Microsoft announced that SharePoint 2013 workflows would be turned off for new Microsoft 365 tenants beginning April 2, 2024. They were then removed from existing tenants and fully retired on April 2, 2026.
This means both classic SharePoint workflow platforms have now reached the end of their Microsoft 365 lifecycle:
- SharePoint 2010 workflows: Retired from Microsoft 365 in 2020
- SharePoint 2013 workflows: Fully retired from Microsoft 365 April 2, 2026
Microsoft recommends migrating SharePoint 2013 workflows to Power Automate or another supported workflow orchestration solution.
SharePoint 2010 vs. SharePoint 2013 Workflow Retirement
The two workflow platforms are often confused because both are referred to as “SharePoint workflows.”
They are separate workflow systems.
| SharePoint 2010 Workflow | SharePoint 2013 Workflow | |
|---|---|---|
| Introduced with | SharePoint Server 2010 | SharePoint Server 2013 |
| Microsoft 365 retirement | November 1, 2020 | April 2, 2026 |
| New Microsoft 365 tenants | Turned off August 1, 2020 | Turned off April 2, 2024 |
| On-premises history | Supported on applicable SharePoint Server versions | Supported on applicable SharePoint Server versions |
| Modern replacement | Power Automate or another supported platform | Power Automate or another supported platform |
The key point is that Microsoft 365 retirement dates should not automatically be applied to on-premises SharePoint Server environments. The server version and its support lifecycle also matter.
Are SharePoint 2010 Workflows Still Supported On-Premises?
For organizations asking whether they can continue using SharePoint 2010 workflows on-premises, the answer depends on the SharePoint Server version.
SharePoint 2010 workflows were supported on SharePoint Server 2016 and SharePoint Server 2019 through the applicable product support lifecycle. Microsoft also explicitly stated that SharePoint Server Subscription Edition would support SharePoint 2010 workflows until July 14, 2026.
As of July 14, 2026, organizations should not consider SharePoint 2010 workflows a supported long-term workflow platform.
An existing workflow may still function in a particular environment. That does not mean the workflow technology remains supported or that it is a good foundation for new business processes.
This distinction is especially important for organizations with workflows that support:
- IT service requests
- Employee onboarding
- Purchasing
- Document approvals
- Contract approvals
- Compliance processes
- HR requests
- Financial approvals
- Records management
- Government processes
- Manufacturing processes
- Healthcare workflows
If a workflow is business-critical, relying on legacy technology indefinitely creates unnecessary operational risk.
What Happens to Existing SharePoint 2010 Workflows?
Retirement does not necessarily mean that every existing on-premises workflow immediately disappears.
Instead, organizations need to consider the support status of the underlying SharePoint Server environment and workflow platform.
A legacy workflow may continue to execute in a particular environment even though the technology is no longer a supported long-term platform.
That creates several concerns.
Unsupported technology
Once a workflow technology reaches the end of its supported lifecycle, organizations should not assume Microsoft will continue to provide support for workflow-specific issues.
Business continuity risk
A workflow may automate a process that employees rely on every day. If the workflow fails, the organization may have to perform the process manually.
Security and compliance concerns
Legacy technology can create additional concerns for organizations subject to security and compliance requirements.
This is particularly important for organizations in government, healthcare, financial services, defense, and other regulated industries.
Knowledge loss
Many SharePoint 2010 workflows were created years ago using SharePoint Designer or custom development.
The people who originally created or maintained those workflows may no longer be available.
Migration complexity
Some legacy workflows are simple approvals. Others contain complex business logic, custom actions, forms, notifications, and integrations.
The more complex the workflow, the more important it is to start migration before it becomes an emergency.
How to Find SharePoint 2010 Workflows in Your Environment
Before replacing workflows, create an inventory.
For every workflow, identify:
- SharePoint site
- List or library
- Workflow name
- Workflow type
- Business owner
- Business purpose
- Number of users
- Frequency of execution
- External integrations
- Custom actions
- Associated forms
- Business criticality
- Compliance requirements
- Replacement platform
Do not automatically migrate every workflow.
Some organizations have accumulated hundreds of workflows over many years. Some are no longer used.
Classify them into three categories:
Retire
The process is obsolete or no longer used.
Replace
The process is still needed but the existing workflow should be rebuilt using a supported platform.
Maintain temporarily
The workflow is still required but needs additional analysis before migration.
This approach prevents organizations from spending time and money rebuilding processes that no longer provide value.
What Replaces SharePoint 2010 Workflows?
There is no single replacement that fits every organization.
The right option depends on your SharePoint environment, workflow complexity, security requirements, deployment model, and Microsoft 365 strategy.
Power Automate
Microsoft recommends Power Automate as a modern workflow solution for Microsoft 365.
Power Automate can connect SharePoint with Microsoft 365 services and many external applications.
It is often a strong choice for organizations that are moving business processes into the Microsoft cloud.
However, Power Automate is not automatically the right answer for every organization.
Organizations with strict on-premises requirements, isolated networks, air-gapped environments, or other deployment restrictions may need a different approach.
Microsoft 365 and SharePoint automation
Simple workflows may be rebuilt using a combination of SharePoint, Microsoft Lists, Power Automate, Power Apps, and Microsoft 365 approvals.
This can work well when the process is relatively straightforward and fits naturally into Microsoft’s cloud ecosystem.
Third-party workflow platforms
A third-party SharePoint workflow platform may make sense when organizations have complex legacy workflows or need deployment options beyond standard cloud automation.
For example, NITRO Studio provides forms and workflow automation for SharePoint and Microsoft 365 and supports environments where organizations need greater control over deployment and infrastructure.
For organizations with on-premises, dedicated, or isolated SharePoint requirements, evaluate whether a replacement platform can support the actual environment in which your workflows must run.
SharePoint 2010 Workflow Replacement for On-Premises Environments
Replacing a SharePoint 2010 workflow on-premises is not necessarily as simple as recreating the same process in Power Automate.
Organizations should first determine where the replacement workflow needs to run.
Ask:
- Must the workflow remain on-premises?
- Can the data be processed in Microsoft 365?
- Is internet connectivity available?
- Does the organization operate a disconnected or air-gapped environment?
- Are there government or defense requirements?
- Are there restrictions on moving business data to the cloud?
- Does the workflow integrate with on-premises applications?
- Does the organization need to preserve existing SharePoint Server infrastructure?
These requirements can significantly affect the appropriate replacement strategy.
For organizations that need SharePoint workflow automation without relying exclusively on Microsoft cloud services, a SharePoint-native or SharePoint-compatible workflow platform may be worth evaluating.
How to Migrate SharePoint 2010 Workflows
A successful migration starts with understanding the existing business process rather than simply copying the old workflow.
1. Inventory the workflows
Identify all SharePoint 2010 and SharePoint 2013 workflows.
2. Identify the business owner
Find the person responsible for the process.
This person should confirm what the workflow actually does and whether the process has changed since the workflow was created.
3. Document the process
Document:
- Trigger conditions
- Approval steps
- Notifications
- Business rules
- Data fields
- Forms
- Escalations
- Integrations
- Exception handling
4. Eliminate obsolete workflows
If the organization no longer uses a workflow, retire it instead of rebuilding it.
5. Choose the replacement platform
Evaluate Power Automate, Microsoft 365 capabilities, or a third-party workflow platform based on your actual requirements.
6. Rebuild the workflow
Recreate the business process using supported technology.
Do not assume that an old workflow should be recreated step-for-step.
The migration is an opportunity to simplify the process.
7. Test with business users
Test both normal and exception scenarios.
A workflow that works technically but does not match the way employees actually perform the process is not a successful migration.
8. Document the new workflow
Document the new architecture, business owner, dependencies, and maintenance requirements.
9. Retire the legacy workflow
Once the replacement has been validated, formally retire the old SharePoint workflow.
What About SharePoint Designer 2013?
SharePoint Designer is another important consideration when modernizing legacy SharePoint workflows.
SharePoint Designer 2013 was commonly used to create and manage SharePoint 2010 and SharePoint 2013 workflows.
Microsoft states that SharePoint Designer 2013 was deprecated but remained supported with SharePoint Server Subscription Edition until July 14, 2026. After that date, it is no longer supported.
That means organizations should not build a new long-term workflow strategy around SharePoint Designer 2013.
Instead, use the workflow retirement as an opportunity to move to a supported automation platform.
What Should Organizations With On-Premises SharePoint Do Now?
If you still have SharePoint 2010 or SharePoint 2013 workflows, take these steps:
Step 1: Identify your SharePoint Server version
Determine whether you are running SharePoint Server 2016, 2019, Subscription Edition, or another version.
Step 2: Inventory your workflows
Find every SharePoint 2010 and SharePoint 2013 workflow.
Step 3: Identify business-critical processes
Prioritize workflows that support important business operations.
Step 4: Identify dependencies
Document forms, custom code, integrations, notifications, third-party products, and other dependencies.
Step 5: Decide what can be retired
Do not migrate workflows that no longer provide business value.
Step 6: Select a supported replacement
Evaluate Power Automate and other supported workflow platforms based on your deployment and security requirements.
Step 7: Build a migration roadmap
Start with the highest-risk and highest-value workflows.
Step 8: Test and validate
Have business users validate the replacement before retiring the old process.
Frequently Asked Questions About SharePoint Workflow Retirement
Is SharePoint 2010 workflow retired?
Yes. SharePoint 2010 workflows were retired from SharePoint Online in 2020. For on-premises SharePoint, support continued according to the applicable SharePoint Server lifecycle. SharePoint Server Subscription Edition supported SharePoint 2010 workflows until July 14, 2026.
When was SharePoint 2010 workflow retired?
SharePoint 2010 workflows were turned off for new Microsoft 365 tenants on August 1, 2020 and removed from existing Microsoft 365 tenants on November 1, 2020.
Are SharePoint 2010 workflows retired on-premises?
The Microsoft 365 retirement did not automatically retire SharePoint 2010 workflows from every on-premises environment. Microsoft continued supporting them on applicable SharePoint Server platforms through their product lifecycles. For SharePoint Server Subscription Edition, support ended July 14, 2026.
What is the SharePoint 2010 workflow end-of-life date?
There is not one universal on-premises end-of-life date that applies to every SharePoint Server version. For SharePoint Server Subscription Edition, Microsoft specifies July 14, 2026 as the end of support for SharePoint 2010 workflows. SharePoint Server 2016 and 2019 also reached the end of their extended support lifecycle in July 2026.
Can SharePoint 2010 workflows still run?
An existing workflow may continue to function in an on-premises environment depending on the SharePoint Server version and configuration. However, organizations should distinguish between a workflow continuing to run and the workflow technology remaining supported. SharePoint 2010 workflows should be treated as legacy technology rather than a long-term platform for new automation.
When did SharePoint 2013 workflows retire?
SharePoint 2013 workflows were turned off for new Microsoft 365 tenants on April 2, 2024 and fully retired from existing Microsoft 365 tenants on April 2, 2026.
Are SharePoint 2013 workflows retired on-premises?
The April 2, 2026 retirement date applies to SharePoint 2013 workflows in Microsoft 365. On-premises SharePoint Server environments follow their applicable server support lifecycle and workflow infrastructure requirements.
What replaces SharePoint 2010 workflows?
Microsoft recommends Power Automate or other supported workflow solutions. Depending on an organization’s requirements, options may include Power Automate, Microsoft 365 automation capabilities, or third-party SharePoint workflow platforms.
Can I use SharePoint Designer 2013 for new workflows?
SharePoint Designer 2013 is legacy technology and should not be the foundation for a new long-term workflow strategy. Microsoft states that SharePoint Designer 2013 support with SharePoint Server Subscription Edition ended July 14, 2026.
How do I find my SharePoint 2010 workflows?
Start by inventorying workflows associated with SharePoint sites, lists, and libraries. Microsoft has also provided workflow assessment and modernization guidance for identifying legacy SharePoint workflows and planning migration.
Modernize Your SharePoint Workflows
SharePoint 2010 and 2013 workflows were built for an earlier generation of SharePoint automation.
For organizations still depending on these workflows, retirement is an opportunity to evaluate which processes are still important, eliminate obsolete workflows, and rebuild critical processes using supported technology.
For Microsoft 365 environments, Power Automate is Microsoft’s recommended modernization path.
For organizations that need more control over deployment, infrastructure, forms, or SharePoint-based business processes, a dedicated SharePoint workflow platform may be a better fit.
NITRO Studio provides forms and workflow automation for SharePoint and Microsoft 365, helping organizations modernize legacy SharePoint processes while supporting a range of deployment requirements.
Learn more about NITRO Studio →
Key Takeaways
- SharePoint 2010 workflows were retired from Microsoft 365 in 2020.
- SharePoint 2013 workflows were fully retired from Microsoft 365 on April 2, 2026.
- The Microsoft 365 retirement dates are different from the on-premises SharePoint Server lifecycle.
- SharePoint 2010 workflows on SharePoint Server Subscription Edition were supported until July 14, 2026.
- SharePoint Server 2016 and SharePoint Server 2019 reached the end of extended support in July 2026.
- Organizations still using legacy workflows should inventory them and prioritize migration or replacement.
- Power Automate is Microsoft’s recommended workflow modernization option for Microsoft 365.
- Organizations with on-premises, isolated, or specialized deployment requirements should evaluate replacement platforms based on their specific environment.
The goal should not simply be to replace an old workflow with a new one. The goal is to build a supported, maintainable business process that fits your organization’s current technology and security requirements.
