If you run Nintex K2, three of the technologies it depends on reach end of support during 2026. That sounds more dramatic than it is. Nintex has published a remediation path for each one, is releasing fix packs for all supported K2 versions, and every date is months away. This is a short guide to what is changing, when, and how to stay ahead of it without any last-minute pressure.
This is not about K2 itself. All three changes are external third-party dependencies, from Microsoft and Google, reaching their own end of support. K2 simply uses them, and Nintex has already published a remediation path for each, so no environment is left without an option. Nintex is also contacting affected customers directly as the dates approach, so this is a coordinated, planned piece of maintenance rather than anything that arrives by surprise.
If your K2 workflows use Exchange Online for email, this affects sending and receiving mail, calendar and appointment actions, and any forms or workflows that call Exchange Online SmartObjects. It currently relies on Exchange Web Services, which Microsoft is retiring on 1 October 2026. This affects Exchange Online only, not Exchange on-premises. K2 has supported the replacement, the Microsoft Graph API, since version 5.8.1, and Nintex provides a step-by-step migration guide.
One point to plan for: moving from EWS to Graph is a behavioural change, not only a version upgrade. Graph applies stricter permissions and handles some mail properties, filtering and “send on behalf” behaviour differently, so affected workflows and forms should be revalidated and, in a few cases, adjusted rather than simply switched over.
What this means for you: of the three, this is the date to act on first, and the one that needs the most hands-on time. Confirm you are on version 5.8.1 or later, run the guided migration, and test your Exchange-related workflows and forms well before October so email and calendar actions continue without interruption.
.NET is the underlying framework for several K2 server components, so this change affects ongoing patching and security support rather than a single feature. Microsoft ends support for .NET 8 on 10 November 2026, and Nintex is releasing fix packs that move supported versions from .NET 8 to .NET 10.
What this means for you: the point to check is your K2 version. Only recent releases support .NET 8 in the first place, so if you are on an older version this is a planned upgrade rather than a quick fix pack. Confirming your version now is the sensible first step.
Chrome and Edge are removing a browser feature called client-side XSLT, which K2 uses to render certain forms and reports. The change takes effect on 17 November 2026. Nintex is releasing fix packs for supported versions, and all K2 releases from 5.10 onward already include the fix.
What this means for you: this is the one with the least pressure, because interim options exist if an upgrade cannot happen in time. Using standard Chrome and Edge enterprise settings you can keep the affected forms working while the upgrade is scheduled:
Across all three, the deciding factor is which K2 version you are on. The fix packs apply to supported versions. If your environment is on an older release, the sensible first move is to confirm your version and map an upgrade path, which takes a little more time than applying a fix pack. Knowing where you stand is most of the work, and it removes any guesswork later in the year.
As a Nintex Premier Partner, AMO helps K2 customers plan and carry out these upgrades with no disruption to live environments. If you would like a clear view of how these dates affect your specific setup, and a plan mapped to it, speak to the AMO team.
None of these dates is cause for concern on its own. They are routine end-of-support milestones for technologies K2 happens to use, each with a clear remediation path already published. The organisations that handle them well are simply the ones that map their environment early and schedule the work in good time. Start with the October Exchange date, confirm your K2 version, and the rest follows comfortably from there.
We gather information about your needs and objectives of your apps. Unsure about the app you need? We will carefully assess your top challenges and provide expert guidance on the perfect solution tailored to your success.
We create wireframes and an interactive prototype to visualise the app flow and make changes as per your feedback.
Estimation of the project deliverables including the resources, time, and costs involved.
Showcasing POC to relevant stakeholders illustrating the functionalities and potential of the app to meet business objectives.
