Quick Launch settings, also known as the top-bar navigation, can be changed after a migration, at either the site collection or site level.
This option is only available when Advanced Mode is enabled.
To change Quick Launch settings after a migration:
1.In the Explorer View, select the site or site collection for which you want to change the global navigation.
2.Right-click and choose Change Site (or Site Collection) Settings > Quick Launch Settings.
3.If you want any changes you make to Quick Launch settings to be applied to any parent sites, check the Push changes to parent site box.
4.If you want any changes you make to Quick Launch settings to be applied to any child sites, check the Push changes to subsites box.
5.If you want Quick Launch Enabled on the site, make sure this box is checked.
6.If you want Tree View Enabled on the site, make sure this box is checked.
7.Select the appropriate Current Navigation option. Use the information in the following table for guidance.
If you want ...
to allow the Quick Launch to display the same Quick Launch items that are displayed in the parent site
Display the same navigation items as the parent site.
the Quick Launch navigation to display navigation items that exist in both existing sub-sites and sibling sub-sites
Display the current site, the navigation items below the current site, and the current site's sibling sites.
the Quick Launch navigation to only display navigation items for its existing sub sites
Display only the navigation items below the current site.
preserve the current quick launch navigation display settings
Do not change current navigation display mode.
8.If you want sub-sites to be shown in the Quick Launch, check the Show Subsites box.
9.If you want Publishing pages to be shown in the Quick Launch, check the Show Publishing Pages box.
10.If you migrated to a SharePoint 2010 target and you want to set the number of dynamic items that can be displayed within that level of the Quick Launch:
§Check the Maximum number of dynamic items to show within this level of navigation (SharePoint 2010) box.
§Select the applicable number.
NOTE: This option is disabled for all versions of SharePoint except 2010.
11.Complete the appropriate options on the Sorting tab, as you would if you were Changing Global Navigation Settings After a Migration.
NOTE: Any sorting options that you specify will apply to both Global and Quick Launch navigation.
After migrating from a classic site to a modern site, you can use a solution provided by Microsoft and PnP Community to convert classic pages within the migrated site to modern pages via the Content Matrix Console.
IMPORTANT: The assemblies required to run this action are not shipped with Content Matrix and must be obtained from the PnP Community. If you initiate a Convert Classic Pages to Modern Pages action and the assemblies are missing, a pop-up message will display which includes a link to a Knowledge Base article with step-by-step instructions. Quest does not provide support for this solution, as Content Matrix only provides users with the capability to run it.
The Convert Classic Pages to Modern Pages action converts all applicable classic pages and their web parts to modern pages. It is available for the following objects:
· Team Site with no Office 365 group (STS#3)
· Team Site with Office 365 group (GROUP#0)
NOTE: Currently, Content Matrix does not support migrations to this site type.
·Communication Site (SITEPAGEPUBLISHING#0)[
Note that site root pages will also be converted
Document libraries within a supported site type.
Classic pages in a document library within a supported site type.
Converted Page Naming Conventions
Converted modern pages are saved in Site Pages library, along with the original classic pages. By default, the converted page uses the same name as the classic page and the classic page is renamed Previous_<original_page_name>.aspx. If you want classic pages to retain the original name (and continue to display using the existing url), you must change the value of the configuration variable TargetModernPageTakesSourcePageName in the Application Settings.xml file to False. The modern page will then be named "Migrated_<original_page_name>.aspx; however, the content approval status of the classic page will be changed from Draft to Pending, and a new version of that page will be created.
To convert classic pages to modern pages:
1.Select the object whose pages you want to convert.
2.Right-click and choose Convert Classic Pages to Modern Pages.
NOTE: This menu option is available only for supported objects.
You can monitor the progress of the action in the Job List.
Current Limitations and Known Issues
·This action is not supported for use with PowerShell or Distributed Migration.
·Conversion of classic publishing pages is not supported.
·If the Site Pages library requires checkout, target pages are checked out as unpublished.
·If a classic page is checked out by another user during migration, there may be issues in converting the page.
·Approval status is not preserved.
·Metadata except "CreatedBy, Created, Modified" are not preserved on the target page.
·The Modified by field on the target page is set to the connecting user.
·If Content Matrix is uninstalled, DLLs and files deployed for this action are not be removed automatically and will need to be removed manually.
After an initial migration is run, an incremental copy (also known as a delta migration) will copy any new and updated data from the source to the target.
There are three different methods to run an incremental copy from Metalogix Content Matrix:
·Incremental Copy Mode - Update Existing Objects option on the Migration Mode tab
The incremental copying option enables migrations that can preserve and update objects on the target of the migration. This mode is used when you just want to make sure nothing on the target gets overwritten. Only new objects that do not yet exist on the target are copied.
EXCEPTION: For lists and libraries with versioning enabled, any new versions that have been created since the initial migration will be copied to the target.
When this option is selected there are two options that are toggled. The first is the Preserve Item IDs option is enabled. The second is that the workflow copy options are turned off. This is because Incremental copies cannot be run on workflows.
·The Custom Copy option on the Migration Mode tab
The custom copy option allows you to run incremental copies for selected content. This option allows you to configure a mix of the Overwrite and the Incremental modes, meaning that incremental copies can be performed on select content in a migration, while allowing other content to be overwritten.
IMPORTANT: Preserving IDs on items/folders in Lists
When running an incremental copy the Preserve IDs on items/folders in Lists option must have been enabled in the original copy. This is so Metalogix Content Matrix can reference the item ID when looking to see if the items already exists on the target side. If this option was not selected, the incremental copy for SharePoint lists can return some strange results. Generally, in cases where this option was not selected, an incremental copy will create some duplicate content on the target for items it thinks are not in the list, even though they may be (but use a different item ID). The other possible consequence is that some data may be missing, because Metalogix Content Matrix may think that some data exists on the target, even though it may not (but the IDs may be in use). For more information on incremental copying and preserving IDs for SharePoint list items please see Preserving SharePoint List IDs with a CSOM Connection Type .
The preservation of Document ID/s is not an issue for incremental copying of SharePoint documents. Incremental copying for documents is referenced by the folder path/filename of the document instead of the item ID. Metalogix Content Matrix will look for the URL path of the document, and if found, will then compare the modified date between the original target document and the source document to see if any modifications have been made to the file. If any modifications are found, as compared to the target, these will be migrated to the target. If no file was found when looking back to the source/target URL path, then that document/folder will be added.
To perform an incremental copy using Migration mode:
2.On the Migration Mode tab, select Incremental copy.
When this option is selected:
§the Preserve Item IDs option is enabled, and
§the Workflow Copy Options is disabled. (Incremental copies cannot be run on workflows.)
REMINDER: When running an incremental copy the Preserve IDs on items/folders in Lists option must be enabled so that Metalogix Content Matrix can determine if the item already exists or if it has been updated. (When copying documents the folder path and document name are used instead.)
To perform an incremental migration job from an existing job:
1.In the Job List, select the job(s) for which you want to perform an incremental migration. (Use [Ctr] click to select multiple jobs.)
2.Right-click and choose Create incremental job.
NOTE: The new job will use the same name as the initial job with " Incrementally" appended to the end of the name