When migrating Nintex workflows, additional considerations include:
·adding external connections to preserve Nintex Workflow database entries
·determining whether Nintex Features are activated before migrating to a SharePoint on premises target
·configuring a temporary storage location and deploying the Nintex Workflow app when migrating to SharePoint Online (SPO).
In Metalogix Content Matrix it is possible to add a connection to an external database to help with migration actions, such as migrating workflows. Currently this option is only available for Nintex Workflows databases, and is needed when preserving Nintex Workflow database entries, when migrating workflows. Normal SharePoint database connections are still made through the Connect to SharePoint Database connection option. After an External Database connection has been made, it can then be attached to a SharePoint site node in Metalogix Content Matrix.
To add an external database connection when migrating Nintex workflows:
1.In the ribbon toolbar choose Settings > Manage Nintex Workflow databases.
The Manage Nintex Workflow databases lists any existing external database.
2.To add a new connection:
b)Complete the Connect to SQL Server dialog as you would if you were Connecting to a SharePoint Database.
3.This opens a new Connect to SQL Server window. This connection is very similar to the Connect to SharePoint Database connection process. Enter the desired connection information.
When migrating Nintex Workflows between SharePoint on premises site collections and sites, if Nintex Features are not activated on the target site collection, duplicate site columns may be created. Therefore, when an option that includes the migration of Nintex workflows is enabled on the Configure Copying Options - Workflow Options tab, Metalogix Content Matrix will check to ensure that Nintex Features are activated on the target site collection(s). If they are not activated, a warning message will display. You have the following options:
·Activate the Nintex Features on the target before the migration.
·Exclude Nintex workflows from the migration.
·Proceed with the migration of Nintex workflows without the features activated on the target.
NOTE: If you chose this option, after migration you will need to activate Nintex Features on the target then fix any duplicate columns issues manually.
Metalogix Content Matrix can facilitate the migration of Nintex sites and lists workflows to SharePoint Online. Individual sites and site content can be pasted with ease.
NOTE: Currently, Metalogix Content Matrix does not support Nintex workflow migration if the migration was initiated at the list level.
·Two configuration keys in ApplicationSettings.xml relate to Nintex workflow migration to SharePoint Online, namely:
§NintexWorkflowsTempStorage: The temporary local path where Nintex workflow-related files will be stored prior to being migrated to SharePoint Online. If the value of this key is not modified, the files will be stored in the default temp folder on the system.
§CleanupNintexWorkflowsTempStorage: The value of this key determines whether or not the temporary storage folder described above will be cleaned after the migration completes. The default setting for this key is True.
·The Nintex Workflows for O365 app must be deployed to target site collections prior to migration.
IMPORTANT: Because this app is deployed at the site collection level and must be present before workflows are migrated, it will be necessary to create first create the site collection on the target, deploy the Nintex app(s), then migrate the content (using the Paste Site Content option).
For a list of supported Nintex actions available when migrating from SharePoint On-Premises to SharePoint Online, refer to Supported Nintex Actions for SPO Migration.
NOTE: If the workflow contains an action that is not supported, this unsupported action will be created as a comment in the migrated workflow. The comment will contain the name of this unsupported action.