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.

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.  

Supported Objects

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:

Site Level:

· 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

List level:

Document libraries within a supported site type.

Item level:

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.

Hub sites in SharePoint Online provide a way to connect modern team sites and communication sites so that they share the following experiences without the constraints of a site/subsite relationship:

·Common navigation

·News roll up

·Search within a hub

You can register/unregister a hub, associate sites with the hub and change hub associations, and edit hub site settings either from the Content Matrix Console or using PowerShell.

Requirements and Restrictions

·A tenant-level connection is required to perform hub site actions.

·You cannot perform hub site actions on a site that uses a read-only connection.

·Hub site actions are supported for modern team site and communication site templates only.

·Hub site actions can only be performed on one site at a time.

From the Content Matrix Console right-click menu, you can:

·register/unregister a modern team or communication site as a hub site

·edit hub site settings

·associate a site with a hub site

·change hub site associations

To register a site as a hub site:

1.Select the modern team or communication site that you want to register as a hub site.

2.Right-click and choose Register as a Hub Site.

3.Complete the Register as a Hub Site Dialog with the following information:

a)If different than the default (the Title of the site), enter a Hub Name.

b)For Authorized People, enter either the Display Name or email address of the user(s) or security group(s) authorized to you want to allow to associate sites with the hub.  You can enter multiple users/groups as a comma-separated list.

NOTE:  If you leave this field blank, all users will be able to associate their sites with the hub.

4.Click [OK].

When a modern team or communication site is registered as a hub site, the icon to the left of the site is changed to .

To edit hub site settings:

1.Select the hub site for which you want to edit settings.

2.Right-click and choose Edit Hub Site Settings.

3.Update the Hub Name and/or Authorized People as appropriate.

4.Click [OK].

To associate a site with a hub site:

1.Select the modern team or communication site site that you want to associate with a hub site.

2.Right-click and choose Associate with a Hub.

3.From the Edit Hub Association dialog, Select a hub from the drop-down.

4.Click [OK].

When a site is associate with a hub, the icon to the left of the site is changed to .

To change a hub site association:

1.Select the site whose hub association you want to change.

2.Right-click and choose Change Hub Association.

3.From the Edit Hub Association dialog, Select a hub from the drop-down.

NOTE:  If you want to remove a hub association completely, select None from the drop-down.  The site theme and shared navigation of the last associated hub will be retained.

4.Click [OK].

To unregister a hub site:

1.Select the hub site you want to unregister.

2.Right-click and choose Unregister as a Hub Site.

3.Click [OK].

All sites associated with the hub site will be disassociated.  However, these sites will retain the site theme and shared navigation previously inherited from the hub.