Chat now with support
Chat with Support

Metalogix Content Matrix 9.3 - SharePoint Edition User Guide

Introduction Entering the License Key Content Matrix Console End User Interface Enabling Advanced Mode Connecting and Migrating Account Requirements Connecting to SharePoint Preparing for a Migration How Content Matrix Handles Various SharePoint Components
How Team Sites are Migrated to Modern Team Sites How Publishing Sites are Migrated to Communication Sites How MySites are Migrated How Records Centers are Migrated to SharePoint Online Using the Import Pipeline 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 Document Sets are Migrated How Navigation is 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 Managed Metadata, Terms, and Term Stores 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 Converting Classic Pages to Modern Pages After a Migration Incremental Migration Using PowerShell with Content Matrix
Configuring PowerShell for Use with Content Matrix Creating and Running a PowerShell Script 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 License Key Troubleshooting 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 Troubleshooting the Extensions Web Service Installing the Extensions Web Service on Specific Systems Extensions Web Service Installation Files Using Older Versions of the Extensions Web Service 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 Job List Database fails to Load After Upgrade Customized Wiki Page Web Part Zones Not Being Migrated Preserving SharePoint List Item IDs with a CSOM Connection Type Retrying Failed Document Copies to O365 CSOM Connections Migrating Content When the Source Custom List Template is Missing Are SharePoint Online Migrations Throttled? What to Expect when Migrating with StoragePoint How Do I Identify and Remove Containers and Queues from My Azure Private Storage Account? Import Pipeline Batches Getting Stuck "Error, the batch will be resubmitted" Message Displays When Using 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

Information in Exported Excel Files

When an Excel file is exported from the Metalogix Content Matrix Job List there are a number of page tabs that can be viewed. Each page tab will display a different set of data, and some of these tabs will also display pivot graphs (with pivot tables behind them).

NOTE: The data within all of these Excel tabs (both the tables and the graphs) should only be considered a starting point when looking at your migration data. You can modify the existing graphs through various methods, such as applying filters, changing the data values, etc.  You can also take the "raw" data from the LogItems tab and use it to create your own graphs or sets of data as required.

The exported file contains the following tabs:

·Jobs - All of the specific jobs that are included in the export. This includes migration jobs as well as other actions.

·LogItems - All of the operations that have been run by Metalogix Content Matrix and provide all of the logging details that are available in the Log Viewer and Log Item Details windows. Some examples of these operations are: adding lists, adding content types, copying documents, adding users, updating lists, etc.


·Error Rates - A a graph that represents the number of errors and warnings that Metalogix Content Matrix encounters during a migration on a "per minute" basis. The vertical axis will list the number of errors/warnings that are encountered (at the specified time), and the horizontal axis lists the amount of time (displayed in a "per minute" value). The horizontal axis can also be changed to display in month, day, or hour time values as well. Below the graph is a table that provides a different view of the same error/warning breakdown.


·Operation Counts - The number of operations/actions that are run over a period of time. Some examples are: copying sites, copying lists, copying documents, adding SharePoint groups, adding users, copying permissions, etc., and each operation has its own line representation on the graph. The vertical axis lists the number of operations that are running (at the specified time), and the horizontal axis lists the amount of time (this is displayed in a "per minute" value). The horizontal axis can also be changed to display in month, day, or hour time values as well. Below the graph there is a table that provides a different view of the same migration operation data.


·Operation Duration - The total duration of time for each operation/action type against the total migration time.   This is potentially the most confusing graph to read in the exported Excel file. The vertical axis lists the total duration time for each action. This is determined by finding the difference between each operation/actions Time Started and Time Finished values, and then adding the totals together for all of that operation/actions of that type that are running. This is then displayed against the horizontal axis which lists the time (displayed in a "per minute" value) for the migration. The horizontal axis can also be changed to display in month, day, or hour time values as well. Below the graph there is a table that will provide a different view of the same migration data.


An example of how to read this graph is: if at minute 25 (of the hour, not the 25 minute of the migration) a large number of small documents are copied and completed (all in the 25th minute), then at minute 25 in the graph there will likely be a spike in the "duration time" for the "Copying Document" operation/action. If each document was copied in 2 seconds, and there were 41 small documents, then the Sum of Duration value would be listed as 82 seconds (or 0:01:22). So the results in the graph would show a spike for the Copying Document operation/action and minute 25, with a value of 0:01:22.

·Operation Throughput – The  amount of data/throughput (in MB) that is migrated on a "per minute" basis. The vertical axis lists the amount of data that is being pushed through Metalogix Content Matrix for a given operation (at the specified time), and the horizontal axis lists the time (displayed in a "per minute" value) at which that the action was performed. The horizontal axis can also be changed to display in month, day, or hour time values. Below the graph there is a table that will provide a different view of the same throughput data.



Copying Job Logging to Other Applications

It is possible to copy the results of migration jobs from log files to other applications. This can be beneficial if you want to keep track of copy or incremental information outside of Metalogix Content Matrix, or want to manipulate the information for reporting or retention purposes. The log information is copied as text, to the clipboard, and can then be pasted within any other application that allows text pasting. For example, if a copy action was made, the logging can be copied into a Word file, or into an Excel spreadsheet, then saved.

NOTE: Only the end results of the total action will be copied.

To copy the logging for a job list:

1.Select a job from the Job List.

2.Right-click, and choose Copy selected job to clipboard (alternately Ctrl+C can be used).

3.Open the desired target program (for example: Microsoft Word, Microsoft Excel, Notepad, etc), then paste the content into the application (Ctrl+V, or the paste command in the application itself).

NOTE:  The logging for each action within the list must be copied separately.

To copy the logging for job items:

·Select the desired job list or job item(s) that the logging is to be copied from, and open the job list to access the Log Viewer.

·Select any job items that are to be copied. Single or multiple items can be selected in the Log Viewer. In order to copy the logging for the entire job, all job items in the Log Viewer must be selected.

·When all of the desired items are selected, right-click on one of them, and select Copy Log Items to Clipboard, and select to either copy them with, or without details. The Details are a set of extra columns that are added to the logging. These columns are typically: Details, SourceContent, and TargetContent. These columns do not always contain extra information. The default copy option (Ctrl+C) is to copy the logging without the Details.

Coppy Log Item to Clipboard



Creating a Support Zip File for a Migration Job

You can generate a zip file of data associated with a single job item to help Quest Support facilitate troubleshooting.

The high-level data collected in the zip file includes:

·Application Settings files.

·Product information (product version, license, etc.).

·Information about the job item (what action settings were set, the job log, etc.).

IMPORTANT: Please review the contents of the zip file before sending it to Support. While this feature attempts to only collect non-sensitive data, no guarantees can be made - it is up to you to ensure that any files in the zip folder are stripped of any confidential data. Regardless, Quest assures that the contents of the zip file will only be used for troubleshooting the associated support ticket.

To create a support zip file:

1.In the Job List, select the job for which the zip file is to be generated.

2.Use one of the following options:

§In the main ribbon, click the Help tab, then Create Support Zip File.

§Right-click and choose Create Support Zip File.

3.Save the file to the desired location using the desired file name.

4.If you wish to review the zip file for sensitive information, click Yes to open the zip file. Once you are satisfied with the contents of the zip file, it can be sent to Quest Support to aid in troubleshooting.

Monitoring and Managing SPO Migration Jobs that Use the Import Pipeline

For migrations to SharePoint Online that use the Import Pipeline, you can monitor the progress of the job, including Microsoft-side processing, via the SharePoint Online Migration Jobs window.  

NOTE:  This window is used to monitor Objects and Actions Supported Using the Import Pipeline only.  Any components of a migration that use CSOM can be monitored via Log Item Details.

To launch the SharePoint Online Migration Jobs window:

1.In the Job List, select the migration job you want to monitor/manage.

2.Right-click and choose Manage SharePoint Online Jobs.  

Manage SharePoint Online Jobs

NOTE:  This option is available only if the Use Import Pipeline option was selected on the Configure Copy Options - List Content tab, and the window can be open for only one job at a time.

SharePoint Online Migration Jobs

Status Messages

The following are the status messages that display in the SharePoint Online Migration Jobs window.  

·Processing - Content Matrix is preparing batches for upload to the Import Pipeline.

·Queued - The batch is awaiting upload to the Import Pipeline.

·Running - The batch has been uploaded to the Import Pipeline and is being processed by Microsoft.

·Success - The batch has been processed successfully.

·Warning - The batch has been processed with one or more issues.

·Failed - Microsoft-side batch processing has failed.

To view batch details:

1.Select the batch whose detail you want to view.

2.In the ribbon menu, click View Job.

NOTE:  The identifying URIs (Manifest, Blob Storage, and Azure Queue) are generated by Microsoft and can be used by Support for troubleshooting purposes.

Azure Migration Details

While the job is running, you can view the progress in the Logs section of the window.  

EXCEPTION:  The progress of a running job cannot be viewed if it was configured using PowerShell.

Once the job has finished processing (or if the job was configured using PowerShell), the [Download Job Log] button becomes enabled, and you can view complete job details.

Job List Upload Duration Column

The column Upload Duration in the Job List displays the time it took for the job to upload via the Import Pipeline.  If the migration was done with CSOM only, or the target was SharePoint on premises, the field will be blank.

Jobs List SP

Retrying a Failed Batch

Content Matrix automatically retries a failed batch up to five times by default.  (This can be changed via the EnvironmentSettings.xml MaxAzureBatchRetryCount key.)  You can also manually retry a batch by highlighting the batch then clicking Retry Job in the ribbon menu.

NOTE  You can retry job batches any time before the Azure SAS URL for the job expires (which is 30 days for private containers and a number of days determined by Microsoft for SharePoint Online provided Azure containers).  If you want to resubmit a job after this time period, you will need to re-create the migration job.  It may still be possible to submit an API Support zip file for troubleshooting between the time that the Azure SAS URL expires and Microsoft destroys a container.

To create an API Support Zip file to send to Quest Support for troubleshooting:

1.Select the batch(es) for which you want to create the zip file.  (Note that you can multi-select to create a separate zip file for each batch.)

2.In the ribbon menu, click API Support Zip.

3.Save the zip file(s), and send to Quest Support for troubleshooting.

Note that, by default, a zip file's name is its SPO Job ID.  You can, however, rename it.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating