Of note:

Starting in November 2020, SharePoint 2013 workflows will be turned off by default for new tenants. Microsoft will provide a PowerShell script to let customers to activate the SharePoint 2013-based workflow engine for tenant as needed.

SharePoint 2010 and SharePoint 2013-based workflows will continue to be supported for on-premises SharePoint 2016 and SharePoint 2019 Server platforms until 2026.

Note that Nintex Workflow for Office 365 uses SharePoint 2013 workflows.

The deprecation of SharePoint 2010 workflow has no impact to Nintex Workflow for Office 365. Please see article - Nintex Workflow for Office 365 not impacted by SharePoint 2010 workflow deprecation.

With regards to SharePoint 2013 workflow

• Existing customers will not be impacted



• Office 365 Tenants provisioned before 1^st November 2020 will not be impacted



• Office 365 Tenants provisioned after 1^st November 2020 will need to activate SharePoint 2013-based workflow engine via a PowerShell script before they can use Nintex Workflow for Office 365 (we are exploring options to see if there are alternatives to the PowerShell script)

I want to know as well. 

Thanks for the follow up question and apologies for the late reply. 

Just to set the context here, I'm part of the product management team and work closely with the teams on NWC and O365 for both forms and workflow.

There's no immediate action needed to migrate from Office 365 to NWC. Customers who have Nintex Workflow subscription are entitled to use NWC.

Have an NWC first approach. If you're building a brand new workflow, build it on NWC. We're rapidly innovating on NWC, ensuring that we can solve for the same scenarios and use cases, this is evident in our recent update to the SharePoint connector (new events and actions) in NWC. We have a few other key features currently in dev - i.e. Forms repeating section and tasks multi assignee in NWC.

There will be an transition path, we definitely will not leave customers stranded or would want you to rebuild your workflows from scratch. We are currently exploring and planning on transitioning workflows from O365 to NWC. We plan on providing an easy way to transition these workflows with the right tooling and supporting resources to help transition when the time comes. Note: If you've come across the SharePoint 2010/2013 convertor, that is not the tool or the experience we would end up with. That tool was created to help customers that may have any SharePoint 2010 workflows transition to SharePoint 2013 workflow vs. having no path. If anything - hopefully that gives you an idea that the workflows can be transitioned.

We continue to support Nintex Workflow for Office 365 (as long as SharePoint 2013 workflow is supported by Microsoft) and make incremental updates - improvements to tasks, actionable emails and a copy item action.

If folks have any questions, please reach out to your Nintex representatives.

@joshua_tan you mentioned in that reply:

“We continue to support Nintex Workflow for Office 365 (as long as SharePoint 2013 workflow is supported by Microsoft)”

How much longer does Microsot plan to support SharePoint 2013 workflow? Can’t find a definitive answer anywhere on the internet.