Chat now with support
Chat with Support

Metalogix Content Matrix 9.2 - SharePoint Edition User Guide

Introduction Entering the License Key Metalogix Content Matrix Console End User Interface Enabling Advanced Mode Connecting to SharePoint Migrating to SharePoint Online Using the Import Pipeline Preparing for a Migration How Content Matrix Handles Various SharePoint Components
How Team Sites are Migrated to SharePoint Online and SharePoint 2019 How Master Pages are Migrated How List Template Galleries Are Migrated How Content Types are Migrated Document Version and Checked Out File Limitations How Ghosted and Un-Ghosted Pages are Migrated How Records Centers are Migrated to SharePoint Online Using the Import Pipeline How Document Sets are Migrated How Navigation is Migrated How MySites are Migrated How Managed Metadata, Terms, and Term Stores are Migrated How "Share With" Metadata is Migrated to SharePoint Online Using the Import Pipeline How Web Parts are Migrated How Site Themes are Preserved How Site Features Are Migrated How Users and Permissions are Migrated How BCS/BDC Data is Migrated How OneNote Notebooks are Migrated How Customized Form Pages are Migrated How InfoPath Forms are Migrated How SharePoint Workflows are Migrated How Nintex Workflows and Forms are Migrated How Link Correction Works
Initiating a Migration Configuring Copying Options Saving or Running a Migration Job Copying SharePoint Objects as a Separate Action Incremental Migration Using PowerShell with Content Matrix
Configuring PowerShell for Use with Content Matrix
Registering Metalogix Command DLL Files 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 About Us

Migrating Content When the Source Custom List Template is Missing


I have a list on my source that uses a custom list template (ex. a "Fab 40" list) and I want to migrate that list to my new target SharePoint environment. However, I am unable to install that template on my target before migration. How will Metalogix Content Matrix deal with this?


If at all possible, it is recommended that users install any custom list templates on the target environment before migration. That would allow Metalogix Content Matrix to use those templates when migrating, and trying to reproduce the same results on the target. But there are some customizations within templates that Metalogix Content Matrix is unable to migrate content or metadata into, such as the "Fab 40" templates.

In some cases users are unable to install the custom templates in the target environment, such as when migrating to O365. In these cases Metalogix Content Matrix will attempt to find the base template of the source customized list. Then it will create a list on the target using that same base template, and migrate the content into that list.

To help with this two variables have been added to the list XML attributes. They are:

·BaseTemplate - This is the value for the custom list template.

·BaseType - This is the value for the default template that any custom template is based on. If the custom template does not exist on the target, this template will be used for the list creation instead. Please see for more information on the SharePoint BaseType value.

These variables will help Metalogix Content Matrix determine which base template to use so that an "Issue Tracking" list won't be created in a case where it should be a "Custom List" template.

Let's look at an example where you have a custom list on the source, and that list has a BaseTemplate value of "1011", a BaseType of "0", and has not been installed on the target. In this case, Metalogix Content Matrix will look at the source list and find the BaseTemplate value of 1011. It will then look on the target to see if there is a template that has the same value. If it finds one, then Metalogix Content Matrix will create a list with that template and migrate the data over. But, if the BaseTemplate value is not found on the target, then Metalogix Content Matrix will look at the BaseType value instead, since this value should exist by default in the target SharePoint environment. In this example we also happen to know that a BaseType value of "0" is a "Custom List" or "Generic List" type. So Metalogix Content Matrix will create a list on the target, using the "Custom List" template, and will then migrate the source data into that custom list.

Are SharePoint Online Migrations Throttled?


I am migrating some content to SharePoint Online/Office 365 (SPO/O365). Are migrations to Office 365 throttled? And if so, how does Metalogix Content Matrix deal with this?


Before we can answer these questions, there is some information that we need to review first.

SharePoint Online (SPO) is on the open Internet, and is a multi-tenant environment in which multiple MS customers are hosted on a single SharePoint Server Farm. In light of that, Microsoft uses a number of mechanisms to protect SPO customers' environments, and the integrity of these Server Farms.

Based on internal performance benchmarking, there is an impact of between 33% and 40% on the performance of migrations to SPO because of some of these necessary protection mechanisms. Our discussions with the SPO product group, and our experience with numerous customers who have migrated large farms to SPO have shown that the following are among some of the known factors that impact this performance:

·User-based throttling - This ensures that any single user cannot perform so many simultaneous operations on their SPO environment, that these would cause performance issues for other users within the same or other tenants. Refer to the Microsoft article Avoid getting throttled or blocked in SharePoint Online. In the past, if a migration was performed using a single username/password combination, migrations were significantly slower than migrations that involve multiple username and password combinations. However, Microsoft is starting to reduce user-based throttling and increase tenant-based throttling. Given that the rollout of throttling changes occurs over a period of time rather than all farms at once, it is difficult to say if the farm you are migrating into has been impacted by these changes yet.

·Tenant-based throttling - This ensures that no one tenant on a multi-tenant farm can use so many resources, that other tenants' performance suffers significantly. Microsoft started using this to protect tenants on multi-tenant environments. We fully expect this to be the most significant throttling mechanism in use by Microsoft moving forward.

·Farm-based throttling - This ensures that if tenants on the farm are seeing low performance across the farm, no single tenant can create significant additional workload on the farm.

You can reduce throttling during migrations by connecting to SharePoint Online using Office 365 OAuth Authentication.

What to Expect when Migrating with StoragePoint


I am migrating content to my target SharePoint environment and I have Metalogix StoragePoint installed. What kind of results should I expect after 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.

NOTES:  For the StoragePoint options to be available:

·StoragePoint 5.1 must be installed on the target environment.

·The target environment cannot use a CSOM connection type and/or have SharePoint 2019 installed.

IMPORTANT:  When a SharePoint 2013 or 2016 Database connection is used on the source, Storage Point options are available for selection, but the migration of StoragePoint data will fail.  This is a known issue.

The following is a breakdown of expected results:

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.

·Shallow Copy of Externalized Data - Shallow copying is no longer supported in Metalogix Content Matrix. For more information, please see Shallow Copying Externalized Content.

·None - This option is for cases where Metalogix StoragePoint is not installed on the target SharePoint environment, or for cases where StoragePoint is installed but users do not want to use it 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.

·Shallow Copy of Externalized Data - Shallow copying is no longer supported in Metalogix Content Matrix. For more information, please see Shallow Copying Externalized Content.

·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).

How do I Remove Items from My Azure Blob Storage Account?


I am running out of storage space in my Azure blob storage account. How do I remove Azure blob storage containers or queue containers from my blob storage account to free up space for more migration actions?


A prerequisite to removing items is that Azure PowerShell must be installed and configured. For instructions on how to do this, please see the following link:

To remove blob storage containers or queue containers from your Azure blob storage account, do the following:

1.Ensure there are no active migration actions running that use the Azure storage where the items are stored.

2.Open Azure PowerShell.

3.Connect to Azure using the New-AzureStorageContext Cmdlet. Your account name and account key are required parameters. Note that these are different from your Client ID and Application Secret.        $context = New-AzureStorageContext -StorageAccountName $accountName -StorageAccountKey $accountKey

4.Get the items using either the Get-AzureStorageContainer or the Get-AzureStorageQueue Cmdlet. A sample call is shown below:

$containers = Get-AzureStorageContainer -Context $context

5.Remove the items using either the Remove-AzureStorageContainer or the Remove-AzureStorageQueue Cmdlet, depending on the item type retrieved in the previous step. A sample call is shown below:

$containers | %{Remove-AzureStorageContainer -Name $_.Name -Context $context -Force}

6.All items of the specified type are now removed from your Azure blob storage account.

NOTE: In the majority of cases, these items are automatically removed after successful or canceled migrations. Typically, items will only accumulate when the import logs associated with the successful migration of a batch fail to download.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating