Microsoft has announced in KB5002945 that SharePoint 2010 workflows will be removed from SharePoint Server Subscription Edition with the July 13, 2027 public update.
We know many Nintex customers like you rely on these workflows to support important day-to-day business processes. We want to make sure you understand what is changing, how it may affect your Nintex environment, and the steps you can take now to prepare.
What Microsoft has announced
- Microsoft ended support for SharePoint 2010 workflows on July 14, 2026.
- Since the September 2026 public update, SharePoint 2010 workflows have been disabled by default in SharePoint Server Subscription Edition.
- With the July 13, 2027 public update, Microsoft will permanently remove SharePoint 2010 workflows from SharePoint Server Subscription Edition.
What this means for Nintex customers
Microsoft’s change applies only to SharePoint Server Subscription Edition. It affects all SharePoint 2010 workflows on that platform, including Nintex Workflow for SharePoint Subscription Edition and Nintex Task Forms, which rely on the workflow to run. Once you install Microsoft’s July 2027 update, or any later update, these will stop working. Other Nintex Forms for SharePoint Subscription Edition are not affected by this change.
What you should do now
You don't need to navigate this transition alone.
We recommend beginning your planning now so your organization has time to understand its current environment, evaluate the right modernization path, and complete migration and testing before Microsoft releases its July 2027 update.
Begin assessing your environment and planning your migration now. Migrations take time, so allow for implementation, testing and business readiness before Microsoft releases its July 2027 update. Nintex Automation Cloud and Nintex Automation K2 offer potential migration paths. Your account team can help you determine the right approach.
Your Nintex account team or implementation partner can work with you to:
- Identify affected workflows, task forms and business processes.
- Assess migration options, including Nintex Automation K2 and Nintex Automation Cloud, against your technical, security and deployment requirements.
- Develop a migration plan that prioritizes business continuity.
What’s next
We’ll share more information soon. In the meantime, contact your Nintex account team or partner to begin planning your next steps.
We're here to help
Every customer's environment is different, and the right migration approach will depend on your workflows, integrations, infrastructure, and business requirements.
We encourage you to contact your Nintex Account Manager, Customer Success Manager, or implementation partner to begin discussing your environment and next steps.
We'll continue to share additional information, guidance, and resources here on Nintex Community as they become available.
We're here to help you plan your transition.
