Chat now with support
Chat with Support

Metalogix Content Matrix 9.3 - SharePoint Edition User Guide

Introduction Entering the License Key Content Matrix Console End User Interface Enabling Advanced Mode Connecting and Migrating Account Requirements Connecting to SharePoint Preparing for a Migration How Content Matrix Handles Various SharePoint Components
How Team Sites are Migrated to Modern Team Sites How Publishing Sites are Migrated to Communication Sites How MySites are Migrated 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 "Share With" Metadata is Migrated to SharePoint Online Using the Import Pipeline How Web Parts are Migrated How Site Themes are Preserved How Site Features Are Migrated How Managed Metadata, Terms, and Term Stores are 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 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 Incremental Migration Using PowerShell with Content Matrix
Configuring PowerShell for Use with Content Matrix Creating and Running a PowerShell Script 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
DB_Owner Permission Keyboard Shortcuts License Key Troubleshooting Determining the Status of a Migration Running in the Background MySite and User Profile Migration Issues Optimal Setup for Best Performance Migrating SharePoint On Premises Using Proxies, Load Balancing or Alternate Access Mappings Troubleshooting the Extensions Web Service Installing the Extensions Web Service on Specific Systems Extensions Web Service Installation Files Using Older Versions of the Extensions Web Service Migrating JavaScript Migrating Site Variations Migrating with SharePoint Document IDs Changing a Job Configuration for Multiple Files SharePoint 2013 and Later Site Collection Creation Issue Job List Database fails to Load After Upgrade Customized Wiki Page Web Part Zones Not Being Migrated Preserving SharePoint List Item IDs with a CSOM Connection Type Retrying Failed Document Copies to O365 CSOM Connections Migrating Content When the Source Custom List Template is Missing Are SharePoint Online Migrations Throttled? What to Expect when Migrating with StoragePoint How Do I Identify and Remove Containers and Queues from My Azure Private Storage Account? Import Pipeline Batches Getting Stuck "Error, the batch will be resubmitted" Message Displays When Using the Import Pipeline Item Count at Target is Increased When Migrating Using the Import Pipeline Custom Lists with Versioning Enabled Not Being Migrated When Using the Import Pipeline Supported Nintex Actions for SPO Migration Support for GCC High Tenants
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.

Prerequisites

·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 workflow0365.nintex.com 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

Nintex Classic forms can be migrated:

·from SharePoint 2010 to SharePoint 2016, 2019, or SharePoint Online

·from SharePoint 2013 to SharePoint 2013, 2016, 2019, or SharePoint Online

·from SharePoint 2016 to SharePoint 2016, 2019, or SharePoint Online

Nintex Responsive forms can be migrated from SharePoint 2016 to SharePoint Online.

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.

Prerequisites

·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 cannot be migrated from a SharePoint 2019 source, even if the target is also SharePoint 2019.

·Nintex forms with Managed Metadata controls cannot be migrated to a SharePoint on premises target.

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

·The following Nintex Responsive forms controls in SharePoint 2016 are not supported in SharePoint Online:

§SQL Request

§Web Request

§Change Content Type

How Link Correction Works

Metalogix Content Matrix can correct links as a part of a migration. Link correction can only be done at the time of migration, and links will only be corrected for sites, lists, pages, and web parts within the scope of the migration. Any links within documents or files will not be corrected.

If the link that is being corrected is a relative link, Metalogix Content Matrix will try to correct it as a relative link, and if it is an absolute link, then it will be corrected as an absolute link.

Each time a copy operation runs a central repository is created for link correction, and is populated with a list of link mappings. These mappings are found and determined based on the actions that are performed. If a site copy is performed, link mappings relevant to that site copy will be created and placed into the repository. If lists are included in this copy, then Metalogix Content Matrix will also include list link mappings in the repository. Links will be identified on a case by case basis.

Any link correction that is done will access this repository set of link mappings, when correcting URL or HTML links.

Metalogix Content Matrix gathers the link mappings at the start of each migration (copy) action, as soon as we know they might be needed. It then adds them to the central repository. For example, if a site is copied, then the link mappings for the site are added to the repository. Then when a list or web part is copied the link mappings specific for the copying of that object are added to the repository as well.

When a link is corrected, Metalogix Content Matrix will check to see if that link is in the list of mappings in the central repository. If the link is found it will be corrected according to the mapping that exists for it. If the link is not found the last element of the link will be cut off to see if the shorter link address is in the mappings. This will continue on until all of the link's elements have been removed. Any time a link element is removed the Metalogix Content Matrix will keep track of it, and then append all the removed elements on to the end of a link once a suitable mapping from the repository is found. If one of these higher level mappings is found, then use that mapping, and append all of the cut elements on to the end. If the last element is cut off and no mapping has been found, the link correction will stop, and fail.

Link Correction Examples

Example 1

If a link reads as Sales/FactsAndFigures/Output/default.aspx, and Metalogix Content Matrix cannot find this link in the central repository, then it will cut off the last portion of the URL and try again. If the remaining portion of the URL doesn't work Metalogix Content Matrix will try cutting off another element, and will continue to try until all the elements of the link have been cut off. So link correction will step though the link URL in the following steps:

Sales/FactsAndFigures/Output/default.aspx

Sales/FactsAndFigures/Output

Sales/FactsAndFigures

Sales

Stop

Example 2

A link on the source side is pointing to "TargetSales/Figures/Output/default.aspx" and this link is on a page that is being migrated to "Sales/FactsAndFigures/Output/default.aspx," and Metalogix Content Matrix only has a mapping in the link mapping repository for "TargetSales/Figures" mapped to "Sales/FactsAndFigures." When link correction is run it will look for a mapping for "TargetSales/Figures/Output/default.aspx" to be mapped to "Sales/FactsAndFigures/Output/default.aspx" but will not find any mapping. Metalogix Content Matrix will then cut off "default.aspx" and look for a mapping to "Sales/FactsAndFigures/Output/." Again, no mapping for this exists, so the next element ("Output") will be cut off and "Sales/FactsAndFigures" will be looked for. This time a mapping will be found, and the link will update with this URL. Because Metalogix Content Matrix keeps track of the elements that it cuts off, it can then append these to the end. So "Sales/FactsAndFigures" will have the cut elements "/Output/default.aspx" appended to the end, for a final corrected link of "Sales/FactsAndFigures/Output/default.aspx."

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating