A workflow migration is an investment in how your business will operate for years. If you are reviewing legacy Nintex for SharePoint workflows, SharePoint Designer workflows or InfoPath forms, use that investment to examine the process as well as its replacement technology.
Microsoft support ended for SharePoint Designer 2013, InfoPath 2013 and SharePoint Server 2016 and 2019 on July 14, 2026. The implications for an individual workflow depend on the products and components it uses.
Identify the dependency before choosing the replacement
| Product or component | Relevant milestone |
| SharePoint Designer 2013 and InfoPath 2013 | Microsoft support ended July 14, 2026. |
| SharePoint Server 2016 and 2019 | Microsoft support ended July 14, 2026. |
| SharePoint 2013 workflows in SharePoint Online | Retired April 2, 2026. |
| SharePoint 2010 workflows and InfoPath Forms Services in Subscription Edition | Microsoft support ended July 14, 2026. Subscription Edition itself is not retired. |
| SharePoint 2013 workflows in Subscription Edition | Remain supported beyond July 2026 through the relevant supported configuration. |
Nintex product support and Microsoft component support are separate questions. Nintex lists several SharePoint editions as supported, but that does not extend Microsoft’s support for a retired dependency. Start by documenting the version, workflow engine and forms technology used by each critical process.
Discuss your workflow replacement options
Continued operation does not resolve a support gap
An on-premises workflow may keep running after a support deadline. That does not restore regular security updates for an unsupported component. The organization needs a plan for reducing that exposure while protecting the work the process handles.
The dependencies can also affect maintenance. Nintex’s August 2026 notice explained that the September SharePoint Subscription Edition update would disable the legacy SharePoint 2010 workflow engine by default, affecting its on-premises workflows unless the engine was re-enabled. Keeping a workflow running and moving it onto a supported foundation are separate tasks.
Use the transition to improve the process
Nintex provides upgrade tools, and its modern cloud platform can connect to systems beyond SharePoint. Its documentation identifies actions that need review, reconfiguration or replacement after migration. A complete rebuild is not inevitable. Moving to a different platform also takes configuration and testing, so compare the transition effort alongside ongoing operating needs.
If your team is already examining rules, forms and integrations, that review creates an opportunity to revisit decisions made when the process was first built. Which approvals still serve a purpose? Where does work sit waiting? Which exceptions still disappear into email?
We worked with a customer whose vendor onboarding process had these same gaps. Forms moved between departments, but missing documents were chased down outside the workflow, and managers had to compile status updates manually. We helped them redesign the process to address those problems and make the work easier to manage. Simply recreating the existing routing rules would have carried those same frustrations into the new system.
A redesign could make missing information visible within the request, assign an owner to each review stage and give managers a shared view of stalled work. The business can then measure whether the new process reduces follow-up and improves completion time. Those outcomes give the team clear criteria for evaluating the replacement.
Decide where the workflow should live
Your organization may still want SharePoint for documents and collaboration. The evaluation should ask whether the business process also needs to depend on its workflow components, particularly when the work spans departments and other systems.
HighGear provides a dedicated platform for configuring forms, assigning work and reporting on progress. It offers cloud and on-premises deployment options and integrations with other business systems, including SharePoint. Integration requirements and their maintenance should be part of the solution design.
For the replacement, evaluate the controls and visibility the process requires: who can change its rules, how exceptions are handled, what history must be retained, and how managers will see the work in progress. Ask the same questions of every platform on the shortlist.
Begin with one representative workflow
Choose a process that matters to the business and contains the kinds of integrations, approvals and exceptions the wider migration must handle. Document its current behavior and agree on what should improve.
Then plan how to preserve required records, handle work already in progress, test permissions and integrations, and move users onto the replacement. A phased transition gives the team a practical way to evaluate the design before expanding it.
If your team is reassessing legacy Nintex, SharePoint Designer or InfoPath solutions, bring one workflow to a conversation with HighGear. We can discuss its requirements and whether a dedicated workflow platform fits the way your team needs to operate.