Additional Considerations for Nintex Forms
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.
·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.
·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:
§Change Content Type
Navigation: How Content Matrix Handles Various SharePoint Components >
StoragePoint Content Migration
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.
NOTE: Metalogix StoragePoint does not support SharePoint Server Subscription Edition, and migration options will be disabled.
Prerequisites for Migrating StoragePoint Content
You can use Metalogix Content Matrix to migrate StoragePoint content if Metalogix Content Matrix detects that Metalogix StoragePoint version 5.1 or later is installed on the target.
For content to be externalized:
·An endpoint must be configured on the target.
NOTE: If you do not have an endpoint configured, content will be migrated directly into SharePoint.
·For a SharePoint 2010 source Database connection, an external connection to StoragePoint must be made.
·For a SharePoint 2013 or later source Database connection, an external SharePoint server connection must be made.
NOTE: Content cannot be externalized if the source is SharePoint 2007.
To allow the migration of files larger than 2GB:
·Large File Support must be enabled in StoragePoint.
·An external connection to StoragePoint must be made.
To make an external connection to StoragePoint (to allow Large File Support):
1.Select the site whose StoragePoint content you want to migrate.
2.Right-click and choose Attach External Connections > StoragePoint Connection.
·use the full Address of the site where the StoragePoint content is configured
·if you specified a Host Name when connecting to the database, click [Fill in default URL] to have it auto-populated.
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).
Navigation: How Content Matrix Handles Various SharePoint Components >
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
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:
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."
From the Metalogix 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 Metalogix Content Matrix Handles Various SharePoint Components.