Skip to main content
All CollectionsMigrateLimitationsNintex Limitations
Some on-premises Nintex Workflow actions cannot be migrated to Microsoft 365
Some on-premises Nintex Workflow actions cannot be migrated to Microsoft 365
Updated this week

Symptoms

When copying Nintex Workflows from SharePoint on-premises to Microsoft 365, 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 Microsoft 365

Index

Details

This article lists Nintex Workflow actions that are supported when migrating from on-premises, if you are looking for the list of supported actions when migrating from Microsoft 365, see this article.

Supported actions

The following on-premises actions are supported by the app when migrating to Microsoft 365.

Libraries and lists

  • Create item

  • Check in item

  • Check out item

  • Discard check out

  • Set field value

  • Set item permissions

  • Update item

  • Delete item

Logic and flow

  • Action Set

  • Commit pending changes

  • For each

  • Change state

  • Filter

  • Loop

  • Run if

  • Run parallel actions

  • State machine

  • Switch

  • Set a condition

Operations

  • Build string

  • Convert value

  • Calculate date

  • End workflow

  • Log in history list

  • Math operation

  • Regular expression

  • Set variable

  • Set workflow status

  • Pause until ...

  • Pause for ...

User interaction

  • Assign Flexi task

  • Send notification

Nintex Live

  • Yammer Message

  • Tweeter Tweet

Integration

  • Query User Profile

Not supported

The following on-premises actions are not yet supported:

Integration

  • Call web service

  • Create CRM record

  • Delete/Disable CRM record

  • Execute SQL

  • Find user by status

  • Get user status

  • Query BCS

  • Query CRM

  • Query Excel Services

  • Query LDAP

  • Query XML

  • Search query

  • Send / Receive BizTalk

  • Update CRM record

  • Update XML

  • Web Request

Libraries and lists

  • Convert document

  • Copy item

  • Create item in another site

  • Create list

  • Delete multiple items

  • Read document

  • Update document

  • Update multiple items

Logic and flow

  • N/A

Operations

  • Collection operation

  • Retrieve data

  • Start workflow

  • Store data

Provisioning

  • Add user to AD group

  • Compile audience

  • Create AD group

  • Create AD user

  • Create audience

  • Create site

  • Create site collection

  • Decommission AD user

  • Decommission site collection

  • Delete AD group

  • Delete audience

  • Delete site

  • Enable Lunc / OCS

  • Provision user in Exchange

  • Remove user from AD group

  • Update AD user

  • Update user profile

User interaction

  • Assign to-do task

  • Complete workflow task

  • Create appointment

  • Create task

  • Delegate workflow task

  • Get meeting suggestions

  • Request approval

  • Request data

  • Request review

  • Task reminder

Solution

There are 3 scenarios that would explain why the action is not supported:

  • There is no equivalent Nintex action in Microsoft 365.

  • There is no appropriate conversion for the action. That is, there is no way to convert the action while preserving the business logic.

  • Migration of the action is not yet supported by ShareGate.

The app will replace the unsupported actions with a placeholder action. This placeholder is an empty action with the name of the original action. You will be able to migrate the structure of your workflow and simply replace these actions with their corresponding Microsoft 365 counterparts.

For more information, see Nintex placeholder action.

Did this answer your question?