Nintex for Office 365 Stopped Working on April 2. Here’s What to Do Now.

If you woke up on April 2 and your Nintex for Office 365 workflows and forms were not running, you are not alone.

Microsoft retired the SharePoint 2013 workflow engine on April 2, 2026. On the same day, it retired the SharePoint Add-In app model. Both of these were the infrastructure Nintex for Office 365 was built on. When that infrastructure went away, so did Nintex for Office 365.

Nintex flagged this as end of life back in December 2023. Support ended on December 31, 2025. Execution ended on April 2, 2026. There is no patch. There is no recourse. Any approval flow, notification, form, or routing rule that depended on Nintex for Office 365 stopped working that day.

This blog covers what happened, why it caught so many teams off guard, and the three migration paths that actually work.

What exactly ended on April 2

Two Nintex products were affected:

•       Nintex Workflow for Office 365
•       Nintex Forms for Office 365

Both stopped functioning when Microsoft disabled the SharePoint 2013 workflow engine and the SharePoint Add-In model. Nintex’s official guidance confirms there is no workaround and no fallback. Workflows that were in-flight mid-approval did not resume. Forms that were published through the Add-In no longer open.

How to confirm you are affected: open your SharePoint Online tenant and check whether any list or library still shows a Nintex Workflow or Nintex Forms Add-In. If it does, and you were a Nintex for Office 365 customer, your automation is down.

What stopped working on April 2

The scope depends on how your organization used Nintex for Office 365, but the common failures across customers include:

•       Approval workflows, including purchase requests, leave requests, and document sign-offs
•       Notification emails triggered by SharePoint list or library changes
•       Multi-stage routing workflows that moved tickets or tasks between teams
•       Form-to-workflow pipelines where a submitted Nintex Form kicked off an automated process
•       Scheduled workflows that ran on a timer or calendar trigger
•       Any Nintex Forms that were published through the SharePoint Add-In model

If these processes support business-critical operations, IT ticket routing, HR onboarding, financial approvals, then the impact extends well beyond an IT inconvenience.

Regulated industries face an extra layer of risk. If your approval workflows are part of your compliance documentation trail, a workflow failure on April 2 breaks that trail. Auditors and compliance teams need to know where the gap sits, and what remediation is in place.

Why this caught so many teams off guard

Nintex published end-of-life notices as early as December 2023. A reasonable question, then, is why so many organizations are only dealing with this now, in April 2026.

Three reasons keep showing up in customer conversations.

The messaging was inconsistent.

Over the past two years, Nintex announcements moved around. End of support was December 31, 2025. Execution stopped on April 2, 2026. Different dates, different products, different migration paths. Customers trying to plan had to stitch the timeline together from multiple community posts.

The recommended migration paths kept shifting.

Nintex initially pointed customers toward Nintex Automation Cloud, then introduced Nintex Automation K2 as the on-prem path, then both under a single Modernization Program. Teams that started evaluating options in 2024 often found the guidance had changed by the time they were ready to commit.

The cost of the recommended migrations surprised buyers.

Both Nintex Automation K2 and Nintex Automation CE use different licensing models than Nintex for Office 365 did. Many customers report the new pricing is three to ten times their legacy Nintex for Office 365 cost. That pricing shock sent a lot of teams back to the evaluation stage to look at alternatives, which pushed the decision dangerously close to the April 2 deadline.

If any of that describes your situation, the priority now is straightforward. Audit what has stopped running, scope the migration, and pick a replacement path that fits both your budget and your SharePoint environment.

What are your migration options?

There are three realistic paths.

Option 1: Nintex Automation K2

K2 is Nintex’s enterprise-grade successor, designed for complex, regulated workflows and self-hosted deployments. It is the path Nintex steers larger customers toward.

It works. But customers evaluating K2 consistently flag two issues.

The first is cost. One long-tenured Nintex customer in Canadian healthcare, a 17-year Nintex account, evaluated K2 when Nintex ended grandfathering on their legacy licensing. Their finding: the K2 model was roughly ten times what they had been paying on Nintex for Office 365, and Nintex was not open to negotiation. That ratio is not universal, but it is not an outlier either.

The second is complexity. K2’s architecture is meaningfully different from Nintex for Office 3 65. Existing workflows cannot be migrated directly. Everything has to be rebuilt, and the rebuild requires either trained K2 developers or paid professional services.

Good fit for: large enterprises with complex regulated workflows, dedicated internal automation teams, and budget for both the platform and the rebuild.

Option 2: Microsoft Power Automate

Power Automate is Microsoft’s native automation tool and is included in many Microsoft 365 plans. It handles simple workflows reliably and integrates across the Microsoft ecosystem.

The limits are real. Licensing gets complicated once premium connectors are involved. Complex approval chains that were routine in Nintex for Office 365 often require significant rework in Power Automate, sometimes stitched together with Power Apps on top. Teams that do not already have Power Platform skills face a real learning curve.

The same Canadian healthcare customer mentioned above also looked at Power Apps during their evaluation. Their summary: the licensing was attainable because it overlapped with their existing Microsoft 365 footprint, but the time and skillset investment to rebuild their workflow library was difficult and costly.

Good fit for: organizations with primarily simple automations, teams already skilled in the Power Platform, and cloud-first strategies that align with Microsoft’s direction.

Option 3: NITRO Studio by Crow Canyon Software

A third category of tools, purpose-built SharePoint automation platforms, fills the gap between K2’s complexity and Power Automate’s limits. NITRO Studio is built natively for SharePoint Online and Microsoft Teams. It runs inside your Microsoft 365 tenant, which means your data never leaves your organization’s environment.

What NITRO Studio is:

• A no-code forms and workflow platform, native to SharePoint and Microsoft Teams
• Flat annual pricing, unlimited workflows and forms, no per-flow or per-connector surprises
• From Crow Canyon Software, a Microsoft partner of 27-plus years with 1,000-plus organizations running on NITRO
• Ready-to-use business applications for IT help desk, HR, purchase requests, and asset management, all built on NITRO Studio
• Trusted across Government, Healthcare, and Banking, where data residency is non-negotiable

A real migration example.

A long-tenured Nintex customer, a Canadian community hospital that had been on Nintex since 2008, signed with Crow Canyon in November 2025 and went live on NITRO Studio in early March 2026. That is five months of total project time, including 1,800 in-flight cases migrated to the new platform without breaking running processes.

Their SharePoint administrator, a 13-year Nintex veteran, said the biggest difference was the support model: issues submitted to Crow Canyon came back with solutions the same morning, instead of waiting three or four days for a response. Their IT consultant, with 30-plus years in healthcare IT, said the knowledge transfer to their internal team worked better than any they had seen with previous vendors.

Good fit for: SharePoint-heavy organizations, regulated industries needing data residency controls, teams that want flat-rate predictable pricing, and organizations where the migration needs to move faster than a traditional rebuild cycle.

Side-by-side comparison

What should you do this week?

If your workflows and forms are down, or if you are still on Nintex for Office 365 and watching processes fail intermittently, here are the three things worth doing immediately.

1. Audit what has stopped. Pull a list of every Nintex for Office 365 workflow and form that was active before April 2. Note the business owner, the frequency, and the impact of each one being down. This is the data any migration path will ask for.
2. Identify the processes that need to come back first. Some workflows are nice to have. Others are blocking approvals, stopping invoices, or breaking compliance trails. Rank them. The first 20 percent of your migration effort will cover 80 percent of the business impact.
3. Book a migration scoping call. Most platforms, including Crow Canyon Software, offer a free session to map your current environment and estimate a realistic timeline. Use it. The goal is a scoped plan before committing to a platform.

Frequently Asked Questions