In relation to the announcement made by Microsoft regarding SharePoint 2010 workflow retirement for Microsoft 365, Nintex Workflow for Office 365 is not impacted by the SharePoint 2010 workflow retirement.
For more information or assistance, please reach out to Nintex Support.
Solved! Go to Solution.
I appears Nintex does user SharePoint 2013 workflow engine which is being deprecated. What is in place to deal with this issue?
Thanks for your query, looking at MSFT link : SharePoint 2010 workflow retirement for this:
"After August 1, 2020, new Microsoft 365 customers can use SharePoint 2013 workflows or Power Automate. However, SharePoint 2013 workflows will follow a similar retirement path in the future, so it's highly recommended to use Power Automate or other supported solutions. You won't lose any content during the transition. However, all migration of workflows is a manual process."
so MSFT say that SP 2013 workflow manager is still valid.
do you have a On-Prem or O365 of Nintex workflow platform?
Hope that help
we are using the O365 Nintex Platform which appears to be using the SP 2013 workflow manager, however, SharePoint 2013 workflows will follow a similar retirement path in the future.
What is Nintex doing to prepare for the retirement of the SP 2013 workflow manager?
with Nintex suite, workflows can be executed and processed on :
1- On-prem ( SharePoint on Prem using Microsoft workflow engine)
2- O365 ( using Microsoft Workflow Manager)
3- Nintex for Cloud - NWC ( using its own workflow engine)
Im happy to discuss any workflow migration plan. that might help you.
Hope that help,
Sorry but that's not an answer to the question. What will happen to the Nintex for O365 workflows once the 2013 workflow engine is scrapped from Office 365? Will they have to be migrated to NWC?
I think the comments concerning SP2013 workflows are very valid. As of this morning, SP workflow instance pages have a banner pointing to a Microsoft article where they are saying that SP2013 "will follow a similar retirement path in the future, so it's highly recommended to use Power Automate or other supported solutions".
I am assuming Nintex is going to have to change substantially when this does happen. How is Nintex planning on dealing with the change?
I would like to know an answer to this as well. We use nintex for some users but I'm debating if I should go with power automate versus nintex to convert the majority of the workflows.