Chat now with support
Chat with Support

Content Matrix 9.9 - SharePoint Edition

Introduction Activating the License Key Selecting the SQL Database You Want to Connect to Content Matrix Console End User Interface Enabling Advanced Mode Multilingual Support Connecting to SharePoint Preparing for a Migration How Content Matrix Handles Various SharePoint Components
Team Site to Modern Team Site Migration SharePoint Sites to Modern Communication Site Migration Promotion of First Level Subsites to Site Collections MySite Migration "Share With" Metadata and "Sharing Links" Access Permissions Migration Records Center to SharePoint Online Migration Using the Import Pipeline Master Page Migration List Template Gallery Migration Content Types Migration Document Version and Checked Out File Limitations Ghosted and Un-Ghosted Page Migration Document Set Migration Navigation Migration Classic Web Parts Migration Site Theme Preservation Site Feature Migration Managed Metadata Migration Users and Permissions Migration BCS/BDC Data Migration OneNote Notebooks Migration Customized Form Pages Migration InfoPath Forms Migration SharePoint Workflow Migration Nintex Workflows and Forms Migration Link Correction StoragePoint Content Migration
Initiating a Migration Configuring Copying Options Saving or Running a Migration Job Copying SharePoint Objects as a Separate Action Configuring Hub Sites Incremental Migration Using PowerShell with Content Matrix
Adding PowerShell Snap-Ins for the Application Framework Content Matrix PowerShell Commandlet List
Metalogix.System.Commands Metalogix.SharePoint.Commands Metalogix.Jobs.Reporting.Commands Metalogix.SharePoint.Migration.Commands
Modifying Content Matrix Configuration and Settings Configuring Content Matrix for Distributed Migration Frequently Asked Questions
DB_Owner Permission Keyboard Shortcuts Activating the License Key Silently License Key Troubleshooting Errors Connecting to SharePoint 2019 or SharePoint Server Subscription Edition in a FIPS-Enabled Environment Determining the Status of a Migration Running in the Background MySite and User Profile Migration Issues Optimal Setup for Best Performance Migrating SharePoint On Premises Using Proxies, Load Balancing or Alternate Access Mappings Extensions Web Service Installation Files Migrating JavaScript Migrating Site Variations Migrating with SharePoint Document IDs Changing a Job Configuration for Multiple Files SharePoint 2013 and Later Site Collection Creation Issue Customized Wiki Page Web Part Zones Not Being Migrated Preserving SharePoint List Item IDs When Migrating to SharePoint Online Retrying Failed Document Copies to SharePoint Online CSOM Connections Import Pipeline Batches Getting Stuck Migrating Content When the Source Custom List Template is Missing When Migrating to SharePoint Online HTTP Status Code 429 (“Too many requests”) or 503 (“Server Too Busy”) Message Returned How Do I Identify and Remove Containers and Queues from My Azure Private Storage Account? Error: 'The object is associated with property AssociatedMemberGroup.' Migration Error: 'ERROR, the batch will be resubmitted to the import pipeline' Item Count at Target is Increased When Migrating Using the Import Pipeline Custom Lists with Versioning Enabled Not Being Migrated When Using the Import Pipeline Supported Nintex Actions for SPO Migration Support for GCC High Tenants
About Us

Converting Classic Pages to Modern Pages After a Migration

Navigation:  Copying SharePoint Objects as a Separate Action >

Converting Classic Pages to Modern Pages After a Migration

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 Microsoft 365 group (STS#3)

· Team Site with Microsoft 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.

Connecting a Top-level SharePoint Online Site Collection to a New Microsoft 365 Group

Navigation:  Copying SharePoint Objects as a Separate Action >

Connecting a Top-level SharePoint Online Site Collection to a New Microsoft 365 Group

Microsoft offers a PowerShell cmdlet that enables you to connect a top-level SharePoint Online site collection to a new Microsoft 365 group.  Refer to the Microsoft article Set-SPOSiteOffice365Group (Microsoft.Online.SharePoint.PowerShell) | Microsoft Docs for details.

You can also create group connections in bulk.  Refer to the Microsoft article Connect to a Microsoft 365 group | Microsoft Docs for details.

Configuring Hub Sites

Navigation:  [No topics above this level]

Configuring Hub Sites

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.

Note:  You can also register and associate hub sites as part of a migration to SharePoint Online if you choose to promote first level sites to site collections.

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.

Configuring Hub Sites from the Content Matrix Console

Navigation:  Configuring Hub Sites >

Configuring Hub Sites from the Content Matrix Console

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 Hub symbol.

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 Associate Hub icon.

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.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating