If you manage SharePoint on-premises and your organization runs Nintex workflows, you have a deadline on your calendar. July 14, 2026.
That is when Microsoft ends extended support for SharePoint Server 2016 and 2019. It is also when the SharePoint 2010 workflow engine goes unsupported, InfoPath Forms retires, and SharePoint Designer 2013 retires. Nintex for SharePoint, the on-premises workflow product many organizations rely on, runs on that infrastructure. When the infrastructure loses support, Nintex for SharePoint loses its foundation.
Nintex itself ties its on-premises product’s timeline to Microsoft’s SharePoint Server support window. On its own end-of-support page, Nintex tells customers that with SharePoint Server 2016 and 2019 ending in July 2026, organizations should start planning immediately.
This blog covers what is ending, why on-prem organizations face a harder problem than their cloud peers, and the three migration paths that work for regulated environments.
What is happening on July 14, 2026
Microsoft has announced the end of extended support for SharePoint Server 2016 and SharePoint Server 2019. Both reach the end of life on July 14, 2026. On the same date, the SharePoint 2010 workflow engine, InfoPath Forms, and SharePoint Designer 2013 also reach the end of support.
Nintex for SharePoint is the product most organizations know as “Nintex on-prem.” It supports SharePoint Server 2010, 2013, 2016, 2019, and Subscription Edition. For organizations running it on SharePoint Server 2016 or 2019, the Microsoft-side deadline is the one that matters.
Here is Nintex’s own framing, from their Microsoft end-of-support page: SharePoint Server 2016 and 2019 reach end of support on July 14, 2026, and organizations should plan immediately. Nintex steers customers toward two successor products, Nintex Automation K2 for self-hosted deployments and Nintex Automation CE for cloud.
The full timeline, side by side
Many on-prem admins are tracking more than one deadline at once. Here is how the 2026 timeline actually stacks up.
| Microsoft product or engine | End of support date | Affects which Nintex product |
|---|---|---|
| SharePoint 2013 Workflow Engine in Microsoft 365 | April 2, 2026 (passed) | Nintex for Office 365 |
| SharePoint Add-In model in Microsoft 365 | April 2, 2026 (passed) | Nintex for Office 365 |
| SharePoint Server 2016, extended support | July 14, 2026 | Nintex for SharePoint |
| SharePoint Server 2019, extended support | July 14, 2026 | Nintex for SharePoint |
| SharePoint 2010 Workflow Engine | July 14, 2026 | Nintex for SharePoint |
| InfoPath Forms | July 14, 2026 | Related, if paired with Nintex |
| SharePoint Designer 2013 | July 14, 2026 | Related, if paired with Nintex |
Note on Subscription Edition: Microsoft’s current guidance is that SharePoint Server Subscription Edition will support SharePoint 2010-based workflows until July 14, 2026, and 2013-based workflows beyond that date. The details have shifted over time. Confirm the current position with Microsoft and your Nintex representative before locking in any architectural decision.
Why on-prem customers face a harder problem than O365 customers
On-premises migrations are more complex than cloud migrations for one straightforward reason: the replacement options are fewer.
Most workflow automation platforms launched in the last five years are cloud-first. They are not designed to run on a self-hosted SharePoint server. They need a connection to a vendor cloud to function at all. That creates a real problem for on-prem organizations in government, housing authorities, healthcare, financial services, and defense contracting, where moving workflow data to a vendor-hosted cloud is either prohibited by policy, restricted by regulation, or impossible in an air-gapped environment.
Here is what the on-prem replacement market actually looks like in 2026:
- Nintex Automation CE: cloud-only, no on-premises deployment
- Microsoft Power Automate: cloud-first, with a limited on-prem data gateway for hybrid scenarios
- Most other workflow SaaS tools: cloud-only architectures
- Nintex Automation K2: Nintex’s self-hosted successor runs on-prem, requires a full rebuild of legacy Nintex for SharePoint workflows
- NITRO Studio by Crow Canyon Software: supports on-prem SharePoint, dedicated deployments, GCC, GCC High, and air-gapped environments
For cloud-first organizations without data residency constraints, the replacement market is crowded. For on-prem organizations with regulatory obligations, it narrows to a handful of options.
The compliance exposure most leadership teams are not seeing yet
For regulated organizations, a Nintex for SharePoint end-of-life event is not only an IT problem. It is a compliance risk that needs to reach legal, audit, and compliance teams well before July 14.
Audit trail integrity
Many organizations use Nintex workflows to document and automate approval processes. Purchase authorizations, policy acknowledgments, HR actions, vendor onboarding, and similar records are often captured as part of the workflow itself. When those workflows stop running, the documentation trail breaks. Auditors reviewing records from the break point forward will see a gap.
Running business processes on unpatched software
Continuing to run Nintex for SharePoint on SharePoint Server 2016 or 2019 after July 14, 2026, means running business processes on Microsoft software that no longer receives security updates, under frameworks like FedRAMP, HIPAA, SOC 2, PCI DSS, and CMMC, which creates explicit compliance exposure.
Vendor support obligations
Several compliance frameworks require organizations to use vendor-supported software for systems that handle regulated data. Running Nintex on an unsupported Microsoft infrastructure can trigger findings during an audit. Legal and compliance teams should review this exposure now, not in July.
Your migration options, in plain terms
There are three realistic paths for organizations coming off Nintex for SharePoint. Each has a real use case. None offers a direct lift-and-shift from your existing Nintex workflows.
Option 1: Nintex Automation K2
K2 is Nintex’s enterprise-grade self-hosted successor, designed for complex, regulated workflows. It is the path Nintex officially points larger on-prem customers toward.
K2 works. The reasons organizations pause on it come down to cost and complexity.
One long-tenured Nintex customer, a 17-year Nintex account in Canadian healthcare, evaluated K2 when Nintex ended grandfathering on their legacy licensing. Their finding: the K2 model was roughly ten times their prior spend, and Nintex was not open to negotiation. That ratio is not universal, but it is not an outlier either. Community discussions across the Nintex forum flag similar cost conversations.
K2’s architecture is meaningfully different from Nintex for SharePoint. 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 a budget for both the platform and the rebuild.
Option 2: Microsoft Power Automate
Power Automate is Microsoft’s native automation platform. It is included in many Microsoft 365 plans and integrates cleanly across the Microsoft ecosystem. For simple workflows, it is a reasonable fit.
For on-prem organizations, the limits show up quickly. Power Automate is cloud-first. It offers an on-prem data gateway for hybrid scenarios, but running mission-critical workflows through a gateway back to a cloud flow is not the same as running them inside your own environment. For air-gapped or dedicated-cloud requirements, Power Automate is not the answer.
The same Canadian healthcare customer mentioned above also looked at Power Apps during their evaluation. Their summary: it would be a significant capital outlay, but the licensing blended with what they already had in Microsoft. The harder problem was the time and skillset development required, which they described as difficult, challenging, and costly.
Good fit for: organizations with primarily simple workflows, teams already skilled in the Power Platform, and cloud-first strategies without data residency constraints.
Option 3: NITRO Studio by Crow Canyon Software
A third category, purpose-built SharePoint automation platforms, fills the gap between K2’s complexity and Power Automate’s limits. NITRO Studio by Crow Canyon runs natively inside SharePoint and Microsoft Teams, on both Microsoft 365 and SharePoint Server on-premises. Data stays in your environment.
What NITRO Studio is:
- A no-code forms and workflow platform built natively for SharePoint and Microsoft Teams
- Flat annual pricing, unlimited workflows and forms, no per-form or per-connector surprises
- Supports SharePoint Online, SharePoint Server 2016, 2019, and Subscription Edition, GCC, GCC High, and fully air-gapped deployments
- From Crow Canyon Software, a Microsoft partner of more than 25 years, with 1,000-plus organizations running on NITRO
- 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 roughly four 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 the three-to-four-day response cycles they had come to expect. Their IT consultant, with more than 30 years in healthcare IT, said the knowledge transfer to their internal team worked better than any he had seen with previous vendors.
Good fit for: SharePoint-heavy organizations, regulated industries with data residency requirements, teams that want flat-rate, predictable pricing, and organizations whose migration needs to move faster than a traditional K2 rebuild cycle.
Side-by-side comparison
A factor-by-factor read of the three paths most on-prem organizations are actually evaluating.
| Nintex Automation K2 | Microsoft Power Automate | NITRO Studio | |
|---|---|---|---|
| Self-hosted on-prem | Yes | Cloud-first, limited via on-prem data gateway | Yes, including dedicated and air-gapped |
| Pricing model | Enterprise licensing, reported as a substantial step up from legacy Nintex | Per user plus per premium connector, scales with usage | Flat annual fee, unlimited workflows and forms |
| Runs natively inside SharePoint | Connected, not native | Connected, not native | Yes |
| Migration from Nintex for SharePoint | Full rebuild, different architecture | Full rebuild, different paradigm | Rebuild with SharePoint-native familiarity |
| Data residency | Self-hosted by the customer | Microsoft cloud | Your environment, on-prem or your M365 tenant |
| SharePoint Subscription Edition support | Not applicable, different platform | Not applicable, different platform | Supported (pending Crow Canyon confirmation) |
| GCC / GCC High / air-gapped | Varies by deployment, check with Nintex | Not available in an air-gapped environment | Yes, one of the few options in these environments |
What to do this week
Four actions have the most impact in the time you have left. If you have not yet started your migration assessment, these are the steps that move the needle.
- Run a Nintex for SharePoint workflow audit. Pull a complete list of every active workflow and form on your SharePoint server. Document the business owner, the trigger, the criticality, and any downstream systems each one touches. This is the foundational data for any migration decision.
- Document your data residency requirements. If your organization cannot move workflow data to a vendor cloud because of policy, regulation, or deployment model, write it down. It eliminates cloud-only options from your evaluation immediately and focuses the decision.
- Map your SharePoint Server roadmap in parallel. If you are on SharePoint Server 2016 or 2019, you also need a plan for the platform itself. Most organizations in 2016 or 2019 are evaluating the SharePoint Server Subscription Edition or a move to SharePoint Online. Choose a workflow replacement that supports your target environment.
- Book a migration scoping call. We at Crow Canyon offer a free session to review your existing Nintex inventory and estimate a realistic timeline. Use it. The output is a scoped plan before you commit to any platform.
Start with the Migration Readiness Checklist
Download the Nintex Migration Readiness Checklist. A step-by-step guide to auditing your workflows and forms, evaluating platforms against your on-prem and compliance requirements, and building a realistic migration timeline. Covers workflow inventory, business-impact ranking, platform fit criteria, and a 90-day go-live plan.
Frequently Asked Questions
Microsoft ends extended support for SharePoint Server 2016 and 2019 on July 14, 2026. Nintex for SharePoint runs on those Microsoft platforms. Once the underlying infrastructure goes unsupported, workflows on Nintex for SharePoint face increasing risk of failure, no security patching for the underlying SharePoint Server, and compliance exposure under frameworks that require vendor-supported software. Nintex's own guidance directs customers to start planning immediately.
Microsoft's current position is that SharePoint Server Subscription Edition supports SharePoint 2010-based workflows until July 14, 2026, and 2013-based workflows for longer. That guidance has shifted in the past. If you are evaluating Subscription Edition as a landing spot for Nintex for SharePoint, confirm the current support position with Microsoft and with your Nintex account team before committing. Several organizations in the Nintex community have reported that the practical answer is to plan a replacement rather than rely on Subscription Edition continuity.
It depends on your environment and budget. For large enterprises with complex regulated workflows, Nintex Automation K2 is Nintex's own enterprise path, though community feedback frequently flags cost and complexity. For cloud-first organizations with simple workflow needs, Microsoft Power Automate is a reasonable fit, but it does not serve air-gapped or strict on-prem requirements. For SharePoint-heavy organizations with data residency constraints, NITRO Studio by Crow Canyon Software is the category most Nintex on-prem customers are moving to.
Start with a workflow and forms audit to identify what needs to come back first, ranked by business impact. Pick a replacement that fits your SharePoint environment and data residency constraints. Rebuild and test the highest-impact workflows in parallel with the old ones, then cut over once the rebuild is verified. Most on-prem organizations with mid-sized workflow inventories can complete a migration in 8 to 16 weeks, depending on complexity and how quickly decisions are made.
Technically, the software will not stop running on its own. Practically, you will be running business-critical workflows on Microsoft infrastructure that no longer receives security updates. For regulated organizations, that position is difficult to defend in an audit. Most organizations treat July 14, 2026, as the date by which a replacement must be live, not the date they start planning.
Yes. NITRO Studio supports SharePoint Server 2016, 2019, and Subscription Edition on-premises, in addition to SharePoint Online, GCC, GCC High, and fully air-gapped deployments. It is one of the few workflow platforms that explicitly covers all of these environments under a single product.
