Updated March 2026

The clock is ticking. On April 2, 2026, Microsoft will officially retire SharePoint 2013 workflows, ending support and functionality for any automation tied to this legacy platform. For organizations using Nintex automation on prem, this date isn’t just a calendar milestone—it’s a hard stop that can disrupt business-critical processes.

Many companies are unaware that Nintex workflows running on the SharePoint 2013 engine will stop functioning once the workflow service is disabled. Without a Nintex migration plan, approvals, routing, and automation that support operations risk failure, causing downtime and potential compliance issues.

Why the SharePoint 2013 Workflows Retirement Matters

Microsoft announced the retirement to encourage organizations to move toward modern workflow platforms. Here’s what you need to know:

  • Hard retirement date: April 2, 2026

  • No new workflows: Since April 2024, new SharePoint 2013 workflows cannot be created on Microsoft 365 tenants

  • Automatic workflow termination: Existing workflows will no longer run post-retirement

  • Impact on Nintex automation on prem: All on-premises workflows that depend on the SharePoint 2013 workflow engine will stop working

Bottom line: Organizations still relying on Nintex automation on prem tied to SharePoint 2013 are at risk of workflow failures, delayed approvals, and operational disruption if they don’t act now.

Understanding the Risks of Not Migrating Nintex Workflows

Failing to plan your Nintex migration can have serious consequences:

  • Business disruption: Automated approvals, notifications, and tasks stop functioning

  • Compliance issues: Workflows handling records or approvals may be incomplete or missing

  • Security gaps: Legacy platforms are no longer patched or supported

  • Increased IT costs: Emergency fixes and manual workarounds can be expensive and time-consuming

In short, staying on SharePoint 2013 workflows after April 2026 is not just risky—it’s costly.

How to Prepare for Nintex Migration

Migrating Nintex workflows from SharePoint 2013 requires planning, but a clear roadmap reduces risk. Here’s a practical approach:

  1. Audit your existing workflows: Identify all active SharePoint 2013 workflows

  2. Classify by complexity: Separate simple, repeatable processes from complex multi-step workflows

  3. Choose a target platform: Options include

    • Nintex Automation Cloud

    • NITRO Studio on-prem

    • Hybrid on-prem solutions

    • Microsoft Power Automate (for modern workflow integration)

  4. Plan rebuild and testing: Map workflows to the new platform and test thoroughly

  5. Execute migration and retire legacy workflows: Ensure all critical business processes are operational on the new platform before shutting down the old workflows

Organizations that plan early for Nintex migration avoid operational disruptions and reduce costs associated with last-minute remediation.

Migration Options for Nintex Automation On Prem

While some companies opt to move fully to the cloud, Nintex automation on prem can still be migrated effectively. Key options:

  • Nintex Automation Cloud: Modern platform with full workflow capabilities, analytics, and reduced infrastructure overhead

  • Hybrid Approach: Maintain critical workflows on-prem while moving non-critical workflows to the cloud

  • Power Automate Integration: Ideal for organizations heavily invested in Microsoft 365 seeking modern automation capabilities

Each approach supports continuity and ensures your organization remains compliant and fully operational beyond April 2026.

Frequently Asked Questions (FAQ)

Q: When is SharePoint 2013 workflows retiring?
A: SharePoint 2013 workflows will be retired on April 2, 2026. After this date, workflows tied to the 2013 engine will stop running.

Q: How does this impact Nintex automation on prem?
A: Any Nintex workflows relying on the SharePoint 2013 engine will fail unless migrated to a modern platform.

Q: What is the recommended Nintex migration path?
A: Organizations should audit workflows, classify complexity, choose a target platform (cloud, hybrid, or Power Automate), plan testing, and execute migration before April 2026.

Q: Can I continue running Nintex workflows on SharePoint after retirement?
A: No. Once SharePoint 2013 workflows are retired, the underlying engine will no longer execute any workflows.

Take Action Now

Time is limited. The SharePoint 2013 workflows end of life isn’t a suggestion—it’s a hard deadline. Organizations using Nintex automation on prem should start planning their Nintex migration today to avoid disruptions and maintain business continuity.

Are you ready to migrate your Nintex workflows before the April 2026 deadline?

Request more info here:

Privacy Notice:
By submitting this form, you consent to Crow Canyon Software collecting and processing your personal information to respond to your inquiry. Do not include sensitive health or personal data unless specifically requested.