Articles in this section

Nintex FAQ

Updated
Follow

In this article, you can find the answers to frequently asked questions for Nintex, Nintex support, and Nintex migrations.

Note: A the ShareGate migration tool Nintex license is required for any feature to work on your Nintex Workflows and Forms.

Questions index

What is currently supported?

  • The migration of Nintex Workflows and Nintex Forms, from on-premises to on-premises, versions 2007, 2010, 2013, 2016, and 2019.
    • When migrating Nintex Workflows, the app will migrate dependencies such as list sites, content types, and reusable workflows for on-premises versions 2007-2019; Default and InfoPath forms; User Defined Actions for on-premises versions 2007-2019; Workflow constants; and Nintex Live actions.  
  • The migration of Nintex Workflows and Nintex Forms, from on-premises 2007-2019 to Microsoft 365.
  • The migration of Nintex Workflows and Nintex Forms, from Microsoft 365 to on-premises 2010-2019.
  • The migration of Nintex Workflows and Nintex Forms, from Microsoft 365 to Microsoft 365 for all actions that are available.
  • The migration of Nintex Workflow history from on-premises to on-premises.
  • Reporting on Nintex Workflows (look for Platform type in your workflow reports).
  • New Responsive Forms.

Note: As of November 2021, the ShareGate migration tool is no longer able to provide full support for SharePoint Server 2003 and 2007, which are past the end of their Microsoft support lifetime. For more information, see Contacting our technical support team.

What is not supported?

At the moment, we do not support:

  • Workflow status. For more on viewing your workflow, see Nintex Workflows only visible in View Workflow History.
  • Workflow scheduler.
  • Start conditions are not supported when going to Microsoft 365.
  • Nintex Site Collection Reusable Workflows, since they are linked to Globally Reusable Workflows.
  • The ShareGate migration tool does not transform SharePoint Designer and InfoPath forms to Nintex Forms.
  • Custom ASPX forms.
  • The following settings - Workflow error notification settings, Message Template settings, Lazy Approval settings, and Workflow change approval settings.  
  • Allowed Workflow actions and Allowed Workflow designers.
  • Workflow templates
  • Workflow statistics and snippets
  • Nintex web parts for Workflows and Forms.
  • Custom Workflow actions (for example, built with Visual Studio).

When migrating Nintex Workflows, will any task content types migrate?

Yes. We migrate site reusable content types and list Workflows.

Does the ShareGate migration tool migrate unpublished workflows?

No. The ShareGate migration tool assumes drafts or unpublished workflows are unused, and will not migrate them.

When migrating from on-prem to the cloud, will we need to republish when changing to claims auth, or will the ShareGate migration tool do that magic for us?

The ShareGate migration tool takes care of the publishing of the workflow under your name.

Can the ShareGate migration tool migrate the Nintex Workflow history?

Yes. The ShareGate migration tool can migrate the Nintex Workflow history from on-premises to on-premises. You need the Server Extension in order to do this. This feature is not supported in Microsoft 365 at the moment.

Note: If the workflow is updated, you will lose the history. 

Will the ShareGate migration tool migrate Nintex history lists?

Yes. The ShareGate migration tool will migrate the history lists from on-premises to on-premises. You need the Server Extension in order to do this. This feature is not supported in Microsoft 365 at the moment.

Will the migrated Nintex Workflows include task forms custom with either InfoPath or Nintex Forms?

Yes. The ShareGate migration tool will include them when migrating to on-premises. However, this feature is not supported in Microsoft 365 at the moment.

Is it possible to migrate the User Defined Actions?

Yes. All levels will be migrated. To perform the migration, you will need the correct level of permissions.

Note: User Defined Actions do not exist in Microsoft 365 so you cannot migrate them when your destination is Microsoft 365.

After Nintex Workflow migration, do we have to reconfigure some tasks or it will be automatic if we migrate the list involved?

The Task list associated with the workflow will be migrated automatically.

When we manually export/import Nintex Workflows, we have to reconfigure some actions in the site where workflow was imported, will the ShareGate migration tool do that for us?

Yes. The ShareGate migration tool doesn't simply migrate the workflow, it also migrates all the dependencies of the workflow and corrects any values to point to the new locations

Can the ShareGate migration tool also support site and/or list/library template mapping?

Only site template mapping is supported at the moment.

Will the ShareGate migration tool migrate Nintex databases - either on-premises or Microsoft 365-dedicated?

The ShareGate migration tool is a client-side software, which means we only use the SharePoint and Nintex public APIs to perform the migration. At no time will we interact directly with the database.

Nintex Workflows for Microsoft 365 has a different feature set than what's on-premises. How will it handle migrating workflows from on-premises to Microsoft 365?

Indeed, the feature set between on-premises and Microsoft 365 is a bit different. At the moment, we are working closely with the Nintex team to make sure there's a migration path for all features. We'll support them on further releases this year.

Does it migrate running workflows too?

Unfortunately, migrating running workflows is not supported. The behavior of a workflow is determined by the sequence of its actions, but some actions may be available at the source that isn't available at the destination. Even when an action has an equivalent at the destination, the parameters may have different names or not contain the same information.

Since this is a client-side install only, does all the migration data need to flow through the client machine?

You can install the ShareGate migration tool on the SharePoint server so that it will not go through the client machine.

Some users don't have access to my Nintex Live Forms after the migration, why does this happen?

When publishing a form to Nintex Live, access to the form becomes restricted based on the users' email addresses. If you have added SharePoint users in the form's Live Settings to give them access to the form, they must have an email address set in their profile in the destination SharePoint environment in order for Nintex to allow them access to the form. The easiest way to verify this is to click on the address book button and search for a user that you're adding, then see if it shows a value under the email column.

What are the supported actions for the migration to Microsoft 365?

Action name on-premises Mapped action in Microsoft 365
Action set Action set
Assign Flexi task Start a Task Process
Build String Build String
Calculate date Add Time to Date
Change state Change State
Check in item Check In Item 
Check out item Check Out Item
Commit Pending Changes  
Convert Value Convert Value
Create item Create List Item
Delete item Delete Item WM Action
Discard check out Discard Check Out Item
End workflow Terminate Current Workflow
Filter Filter
For Each For Each
Log in history list Log to History List
Loop Loop with Condition
Math operation Do Calculation
Pause for... Pause For Duration
Pause until... Pause Until
Query List Query List
Regular expression Regular Expression
Run if Run If
Run parallel actions Parallel Block
Send notification Send an email
Set a condition Conditional Branch
Set field value Set field in current item
Set variable Set Workflow Variable
Set workflow status Set Workflow Status
State machine State Machine
Switch Switch
Twitter Tweet Twitter Tweet 
Update item Update List Item
Yammer message Yammer Message

Related articles