Content Matrix can migrate Nintex Classic and Responsive forms.
|
|
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 Microsoft 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
From the Content Matrix Explorer View, you can "copy" an object from the source connection then "paste" it to the appropriate location on the target connection. You will then be prompted to configure Copy Options.
Before you initiate a migration, it is strongly recommended that you review How Content Matrix Handles Various SharePoint Components.
You can also perform bulk migrations using a single CSV file. For more information, see Migrating in Bulk Using a CSV File.
Content Matrix can migrate SharePoint Site Collections and promote sub-sites into Site Collections. These migrations can be made within the same SharePoint instance, or can be performed between two separate SharePoint instances. Any site can be promoted into a Site Collection in the same way any Site Collection can be copied to become a sub-site. The location in the hierarchy of the target node is what determines if a site will copy as a Site Collection or as a sub-site.
|
|
·For migrations to an on premises SharePoint target, an Object Model (OM) level connection must be made with the target environment. NOTE: Due to some User authentication changes that have been made starting with SharePoint 2013, which inadvertently restrict the creation of Site Collections using the SharePoint OM remotely, Content Matrix will use a set of elevated permissions to create Site Collections, which means the migrating user account must explicitly (by name) have "Full Control" permissions on the Web Application that the Site Collection is being created on. A preliminary check will be made before elevation occurs to ensure the migrating user has enough permissions initially to be able to use the elevated Site Collection creation. Creating Site Collections for a SharePoint on premises target with the Local OM connection type does not have this same restriction, but the same permissions are recommended in case elevated permissions are needed. ·For migration to a Microsoft 365 tenant, a Microsoft 365 Tenant connection must be used. |
|---|
To initiate a Site Collection migration:
1.In Explorer View, select the source site collection or site that you want to migrate.
2.Right-click and choose Copy Site.
3.Select the target node under which you want to create the site collection.
4.Right-click and choose Paste Site Collection.
The Configure Site Collection Copying Options dialog displays.
Continue with Configuring Copying Options.
Before you initiate a MySites migration, it is recommended that you review the information in the section MySites Migration.
To initiate a MySites migration:
1.In Explorer View, navigate to the (Farm" or "Web app) node from which you want to copy MySites.
2.Right-click and choose Copy MySites.
3.Select the target node.
4.Right-click and choose Paste MySites.
Continue with Configuring Copying Options.
