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, 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 Ninte Features on the target then fix any duplicate columns issues manually.
Before you can migrate Nintex forms to SharePoint Online, you must deploy them to your SharePoint Online tenant to make them available to the specified site collections, as described below.
To deploy Nintex Forms app 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 Forms for O365 as part of your Site Contents, then select Add an App and install the application.
NOTE: Make sure you are in classic view in order to perform the deployment, as deployment cannot be done in modern view.
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.
8.Click [OK] to apply your selections.
9.When asked whether you trust forms0365.nintex.com, click Trust It. This will start the actual deployment.
NOTE: Microsoft is now deploying the Nintex Forms 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.
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, 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 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.
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, 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 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 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 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 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. 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 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."
There are a number of different behaviors to expect when migrating to a target SharePoint environment that has Quest® 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 Content Matrix to migrate StoragePoint content if Content Matrix detects that StoragePoint version 5.1 or later (or for SharePoint Server Subscription Edition, StoragePoint version 6.2 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.
To allow the migration of large files:
·Large File Support must be enabled in StoragePoint.
·If a source Database connection is used, a Host Name must be set.
·If migrating to SharePoint Online, the Import Pipeline must be used.
NOTE: Use of the Import Pipeline allows you to migrate files over 2 GB. For migrations to SharePoint on premises, you can migrate files up to 2 GB.
·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.
3.For Host Name when connecting to the StoragePoint 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 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).
