The following list describes some requirements and limitations to be considered when migrating workflows. Note that this list may not exhaustively cover every migration scenario.
·For a migration at the site level or higher:
§The source connection can be Database (SharePoint 2010, 2013, or 2016); Object Model (OM) or Metalogix SharePoint Extensions Web Service (SharePoint 2013 or later); or Office 365 Tenant. However, for a SharePoint 2013 or Office 365 source, the only supported target is another SharePoint 2013 or Office 365 connection.
§The target connection must be OM, MEWS, CSOM, SharePoint 2013 or later, or Office 365 Tenant.
·For a migration at the list level (OOB and SPD workflows):
§The source connection can be SharePoint on premises Object Model (OM) or Metalogix SharePoint Extensions Web Service (MEWS).
§The target can be SharePoint Online.
·When migrating from a SharePoint 2010 DB source to a SharePoint 2013 or later CSOM or O365 Tenant target, Metalogix Content Matrix is unable to distinguish between SPD and Nintex workflows, so it will attempt to migrate all SPD/Nintex workflows that are found. As a result, a warning message will be displayed (if the Nintex workflow feature has been enabled) indicating that any Nintex workflows that are migrated through these connections will result in errors for the Nintex workflow after migration.
·Metalogix Content Matrix does not currently support migrating SharePoint Designer 2013 read-only style workflows from SharePoint 2013 or later source environments over MEWS or CSOM connections. Workflows will be skipped; only lists and libraries will be migrated under these conditions.
·When migrating SPD 2013 platform workflows, the SuppressEvents property must be set to False in order for workflows to be published after migration. For more information, please see Modifying the SuppressEvents Property.
·If you initiate a list-level migration and you want to migrate workflows for the lists, all of the site-level dependencies must already exist at the target. See also Pre-Workflow Migration Considerations.
·Metalogix Content Matrix does not support the migration of workflows at the item level because the item level scope of the migration cannot properly fetch all of the necessary data, as this data is usually stored at the site or list level (this includes actions that reference other lists, site level content types, and so on).
· List-level migrations are not currently supported for Nintex workflows.
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 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 menu 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 .
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.