VENDORiQ: Does Nintex Have a Point About Sharepoint 2013 Workflows End Of Life? Yes.

Nintext announced its transition plan for clients following Microsoft’s decision to retire SharePoint 2013 by 2026. Why should enterprises act early to identify which workflows need to be retained or discarded to avoid accumulating more technical debt?

The Latest

Nintex has created the Nintex Upgrade Program, a transition plan for Nintex Workflow for Office 365 customers following Microsoft’s decision to retire the existing Microsoft SharePoint 2013 workflow engine in Microsoft Office 365. This program will provide tools, services, and support from Nintex process experts to help customers transition smoothly to Nintex Automation Cloud, which is Nintex’s modern, Cloud-based workflow solution.

Why It’s Important

Microsoft’s end-of-life for SharePoint workflows is not unexpected and is aimed at moving clients to its more comprehensive PowerPlatform environment. However, it also opens up opportunities for low-code vendors, such as Nintex to offer not only their own workflow solutions, but also consulting and tooling to make the transition away from SharePoint workflows. 

Migrating workflows can be complex. Many enterprises possess numerous workflows – not all of which were professionally developed. It is not uncommon to find ‘dead’ workflows (unused for years) as well multiple workflows that are highly similar. In short, the workflows within SharePoint 2013 will need to be identified and decisions made as to revamp or decommission each. Having a migration tool is helpful in gaining early visibility on workflows and making decisions on which to migrate, upgrade, merge or discard when moving to a new platform. 

IBRS recommends organisations get started on this early to avoid congestion in migrating workflows, or disruptions in workplace practices.

Consider this as an opportunity to control your organisation’s technical debt that may have accumulated. This will ensure that the transition process is not just about migration but also about streamlining and optimising your organisation’s workflows.

Who’s Impacted

  • Developer teams
  • SharePoint owners
  • Low-code teams

What’s Next?

  • Review the existing SharePoint environment and identity if there are legacy SharePoint 2013 workflows running within the organisations. 
  • If there are, put in place a program to review the workflows and plan a migration to a new low-code platform. 

Related IBRS Advisory

1. VENDORiQ: Nintex Expands Process Templates with New Commercial Enterprise and Government Agencies Use Cases

2. VENDORiQ: Nintex Acquires AI-based RPA Developer Kryon

Trouble viewing this article?

Search