Symptoms
When copying Nintex workflows from SharePoint on-premises to Microsoft 365, ShareGate Migrate displays one of the following messages:
Reusable workflows cannot be copied to Microsoft 365 because Nintex Workflow for Microsoft 365 doesn't support them.
The workflow form will not be copied because Nintex Workflow for Microsoft 365 doesn't support custom workflow forms. The workflow will be using the default form at the destination.
The auto-start conditions used by the workflow will be removed at the destination because Nintex Workflow for Microsoft 365 doesn't support them.
Association columns will be removed from the workflow because Nintex Workflow for Microsoft 365 doesn't support them.
The expected duration setting will not be preserved because Nintex Workflow for Microsoft 365 doesn't support this.
The workflow setting 'Require manage rights' will not be preserved because Nintex Workflow for Microsoft 365 doesn't support this.
The option to start the workflow from the menu will not be preserved because Nintex Workflow for Microsoft 365 doesn't support this.
Nintex Workflow for Microsoft 365 does not allow specific dates as default values for Date/Time variables. The default value of the following variables will be lost: My first variable, My second variable.
βThe parameter (...) contains a Profile Lookup that isn't supported on Microsoft 365.
βThe parameter (...) contains a Workflow Constant that isn't supported by Nintex Workflow for Microsoft 365.
βThe parameter (...) contains an Inline Function that isn't supported by Nintex Workflow for Microsoft 365.
Error code
|
Any error code ending with: -189 |
Details
This error occurs because the source workflow that was built with Nintex Workflow on-premises contains parameters that are not available with Nintex Workflow for Microsoft 365. If you receive a warning message, the workflow will be copied, but without the unsupported settings. If you receive an error message, the workflow will not be copied.
Solution
Since the elements that give you errors or warnings are simply not supported by Nintex Workflow for Microsoft 365, it is not possible to get the exact same workflow as you have on-premises. The best workaround is to look at the reason why the workflow has those parameters and see if the same behavior can be obtained through other features that are offered by Nintex Workflow for Microsoft 365.