Chat now with support
Chat with Support

Metalogix Content Matrix 9.4 - SharePoint Edition User Guide

Introduction Activating the License Key Selecting the SQL Database You Want to Connect to Content Matrix Console End User Interface Enabling Advanced Mode Connecting and Migrating Account Requirements Multilingual Support Connecting to SharePoint Preparing for a Migration How Content Matrix Handles Various SharePoint Components
How Team Sites are Migrated to Modern Team Sites How SharePoint Sites are Migrated to Modern Communication Sites How MySites are Migrated How "Share With" Metadata is Migrated to SharePoint Online Using the Import Pipeline How Records Centers are Migrated to SharePoint Online Using the Import Pipeline How Master Pages are Migrated How List Template Galleries Are Migrated How Content Types are Migrated Document Version and Checked Out File Limitations How Ghosted and Un-Ghosted Pages are Migrated How Document Sets are Migrated How Navigation is Migrated How Classic Web Parts are Migrated How Site Themes are Preserved How Site Features Are Migrated How Managed Metadata is Migrated How Users and Permissions are Migrated How BCS/BDC Data is Migrated How OneNote Notebooks are Migrated How Customized Form Pages are Migrated How InfoPath Forms are Migrated How SharePoint Workflows are Migrated How Nintex Workflows and Forms are Migrated How Metalogix StoragePoint Content is Migrated How Link Correction Works
Initiating a Migration Configuring Copying Options Saving or Running a Migration Job Copying SharePoint Objects as a Separate Action Converting Classic Pages to Modern Pages After a Migration Configuring Hub Sites Incremental Migration Using PowerShell with Content Matrix
Adding PowerShell Snap-Ins for the Application Framework Content Matrix PowerShell Commandlet List
Metalogix.System.Commands Metalogix.SharePoint.Commands Metalogix.Jobs.Reporting.Commands Metalogix.SharePoint.Migration.Commands
Modifying Content Matrix Configuration and Settings Configuring Content Matrix for Distributed Migration Frequently Asked Questions About Us

Migrating Nintex Workflows to SPO

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.

§NintexCleanupWorkflowsTempStorage: 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).

Supported Actions

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.

Deploying Nintex Apps to SharePoint Online

Before you can migrate  workflows (and forms) to SharePoint online you must deploy them to your SharePoint Online tenant to make it available to specified site collections, as described below.

To deploy Nintex apps to SharePoint Online:

1.Sign into your tenant's SharePoint Admin Center using an account that is a Global Administrator.

2.From the left navigation bar, select More Features.

3.Under Apps, click [Open].

4.Select App Catalog.

NOTE:  If the App Catalog site does not open, select Create a new app catalog site, and then click [OK].  On the Create App Catalog Site Collection page, enter the required info, and then click [OK].

5.If you do not have Nintex Workflows for O365 or Nintex Forms for O365 as part of your Site Contents, then select Add an App and install the application(s).

NOTE:  Make sure you are in classic view in order to perform the deployment, as deployment cannot be done in modern view.

SharePoint Classic View Option

6.On the Site Contents page, Select the ellipses (...) next to the installed Nintex application, and click on Deployment.

7.On the Manage App Deployments page, enter the site collection URL or select one from the list available, select and add the managed paths to deploy to, and select and add the templates to deploy to.

Create App Catalog

8.Click [OK] to apply your selections.

9.When asked whether you trust click Trust It. This will start the actual deployment.

NOTE: Microsoft is now deploying the Nintex app to your tenant. It may take from a minute to hour(s) depending on the complexity of your site collection structure. Please verify your site collection for  apps before starting a migration.

Additional Considerations for Nintex Forms

Content Matrix can migrate Nintex Classic and Responsive forms.

Connection icon

The migration of Nintex forms is supported for Object Model (OM) on premises connections, either local or remote (through the Metalogix Extensions Web Service (MEWS)).  

Even if you elect to Use Import Pipeline to migrate to SPO, Nintex forms will be migrated to the target using CSOM.


·For migrated Nintex forms to be published on a SharePoint on premises target, the SharePoint features Nintex Forms Prerequisites and Nintex Forms for SharePoint List Forms must be activated.

·For Nintex forms to be published on an SPO target, the Nintex Forms for Office 365 app must be deployed.

If prerequisites are not met before migration, the forms will need to be published manually after the features or app is installed on the target.  

Current Limitations

·Nintex forms do not migrate for default content types of Asset Libraries.

·The following Nintex Responsive forms controls in SharePoint on premises are not supported in SharePoint Online and will be replaced with label controls on the target:

§SQL Request

§Web Request

§Change Content Type

How Metalogix StoragePoint Content is Migrated

Navigation:  How Content Matrix Handles Various SharePoint Components >

How Metalogix StoragePoint Content is Migrated

There are a number of different behaviors to expect when migrating to a target SharePoint environment that has Metalogix StoragePoint installed. The different results you will see depend on which option is selected in the StoragePoint Options tab.

Prerequisites for Migrating StoragePoint Content

You can use Metalogix Content Matrix to migrate StoragePoint data only as the following conditions are met:

·Metalogix Content Matrix detects that Metalogix StoragePoint version 5.1 or later is installed on the target.

·An endpoint is configured on the target (if you want the content to be externalized).

NOTE:  If you do not want the content to be externalized, it will be migrated directly into SharePoint.

·A SharePoint 2013 or 2016 database connection is not used.

IMPORTANT: When a SharePoint 2013 or 2016 Database connection is used on the source, StoragePoint Options can be selected, but the migration of StoragePoint data will fail. This is currently a known issue.

·The target environment does not use a CSOM connection type.

·The target is not SharePoint 2019.

The following is a breakdown of expected results.

StoragePoint Options - Successful Outcome

·Add documents to StoragePoint if an endpoint is configured - This option is for when content from a non-externalized environment (a source environment that does not have StoragePoint installed) is being migrated into an externalized SharePoint target. In this case, any of the files or documents that are included in the migration will be externalized, meaning that those files and documents will call StoragePoint as they are being migrated, and will be externalized directly with the reference link left behind in the file or document's place (in the target SharePoint environment). Once the migration is complete, users can navigate to one of the migrated documents in Metalogix Content Matrix, switch to the Items View, right-click the document, and then select StoragePoint Details. Here, users should be able to see the StoragePoint endpoint folder location for the externalized content, as well as the externalized file name. If the document is opened through SharePoint directly, it will open as expected.

·None - This option is for cases where users do not want to use StoragePoint as part of the migration process. When this option is selected, content will be migrated directly into SharePoint with all StoragePoint-related features ignored. However, if the target environment is configured to be externalized with StoragePoint, it is possible that the content will be migrated into the SharePoint target as if the StoragePoint options are ignored, but the target SharePoint environment would then externalize the content separately after the migration completes. While the end result would be the externalization of the data, the migration process itself is only migrating content directly into the SharePoint target.

StoragePoint Options - Unsuccessful Outcome

·Add documents to StoragePoint if an endpoint is configured - If this option failed to migrate the documents/files into StoragePoint, then when users go to the StoragePoint Details, there will be nothing set. This indicates that the files were not placed into the StoragePoint EndPoint and were not externalized.

·None - If this option is selected but fails, then the content migration to the target will have failed. This means that the documents/files that are included in the migration action will not exist on the target (externalized or not).

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating