Symptoms
When copying Nintex workflows from Microsoft 365 to SharePoint on-premises, the app displays an error message that says the action is not possible. For example:
Some on-premises Nintex Workflow actions cannot be migrated to on-premises
Index
Details
This article lists Nintex Workflow actions that are supported when migrating from Microsoft 365, if you are looking for the list of supported actions when migrating from on-premises, see this article.
Supported actions
The following Microsoft 365 actions are supported by the app when migrating to on-premises:
Libraries and lists
Create List Item
Check Out Item
Check In
Discard Check Out Item
Query List
Set Field in Current Item
Update list item
Delete Item
Logic and flow
Conditional Branch
Build String
For Each
Filter
Loop with Condition
Parallel Block
Run If
Set Next State
State Machine
Switch
Terminate Current Workflow
Operation
Add Time to Date
Convert value
Do Calculation
Log to History List
Set Workflow Status
Set Workflow Variable
Pause until Date
Pause for Duration
User interaction
Start a task process
Send an email
Nintex Live
Tweeter Tweet
Yammer Message
Utility
Regular Expression
Not supported
The following Microsoft 365 actions are not yet supported:
Integration
Bing get directions
Bing language detection
Bing text to speech
Bing translation
Call HTTP Web Service
Execute SQL
Query XML
Start workflow
Update XML
Libraries and lists
Copy Document
Microsoft 365 add user to group
Microsoft 365 check in items
Microsoft 365 check out items
Microsoft 365 create list item
Microsoft 365 create navigation
Microsoft 365 delete drafts
Microsoft 365 delete items
Microsoft 365 delete previous versions
Microsoft 365 discard check out
Microsoft 365 download file
Microsoft 365 new blog post
Microsoft 365 query list
Microsoft 365 Query User Profile
Microsoft 365 search query
Microsoft 365 send document set to repository
Microsoft 365 send document to repository
Microsoft 365 set approval status
Microsoft 365 set document set approval status
Microsoft 365 update item permissions
Microsoft 365 update items
Microsoft 365 upload file
Terminate workflow instances
Translate document
Wait for Event in List Item
Wait for Field Change in Current Item
Web Request
Logic and flow
App Step
Loop N Times
Operations
Build Dictionary
Count Items in a Dictionary
Get an Item from a Dictionary
Set Time Portion of Date/Time Field
Provisioning
Amazon EC2 create instance
Amazon EC2 instance management
Microsoft Azure create affinity group
Microsoft Azure create virtual machine
Microsoft Azure delete affinity group
Microsoft Azure download RDP file
Microsoft Azure retrieve affinity group
Microsoft Azure retrieve affinity group properties
Microsoft Azure retrieve image
Microsoft Azure retrieve location
Microsoft Azure state management
Microsoft 365 add user to security group
Microsoft 365 assign license
Microsoft 365 create site
Microsoft 365 create user
Microsoft 365 delete site
Microsoft 365 remove user from security group
Microsoft 365 reset password
Microsoft 365 retrieve license plans
Microsoft 365 user access management
Rackspace change password
Rackspace create server
Rackspace rebuild server
Rackspace resize server
Rackspace state management
Yammer create group
Yammer create new account
Yammer remove account
Yammer update group
Yammer update user profile
Social
Yammer retrieve messages
Yammer retrieve user profile
Yammer send invitation
User interaction
Assign a task
Utility
Extract Substring from End of String
Extract Substring from Index of String
Extract Substring from Start of String
Extract Substring of String from Index with Length
Find Interval Between Dates
Find Substring in String
Replace Substring in String
Trim String
Solution
There are 3 scenarios that would explain why the action is not supported:
There is no equivalent Nintex action on-premises.
There is no appropriate conversion for the action. That is, there is no way to convert the action while preserving the business logic.
The action is not yet supported by ShareGate.
Since the elements that give errors may not be supported by the app, the best workaround is to either remove the action from the source workflow and then rebuild it at the destination, or to manually create the workflow at the destination.