Chat now with support
Chat with Support

Metalogix Content Matrix 8.9 - SharePoint Edition User Guide

Introduction Entering the License Key Content Matrix Console End User Interface Enabling Advanced Mode Connecting to SharePoint Migrating to O365 Using the Azure Pipeline/SPO Containers Preparing for a Migration How Content Matrix Handles Various SharePoint Components Initiating a Migration Configuring Copying Options Saving or Running a Migration Action Copying SharePoint Objects as a Separate Action Self-Service Migration Incremental Migration Log Files 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 and Self-Service Migration Frequently Asked Questions
DB_Owner Permission Migrating with the Fabulous 40 Templates Item Count Discrepancies 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 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 Preserving IDs when Migrating a Custom List as a Folder Migrating JavaScript Migrating Site Variations Migrating with SharePoint Document IDs Changing a Job Configuration for Multiple Files SharePoint 2003 Version Migration Limitations 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 on the Target Migration Error Message 'There was an Error Reading from the Pipe: The Pipe has been Ended (109, 0xd6)' How do I Remove Items from My Azure Blob Storage Account? Azure Batches Getting Stuck "Error, the batch will be resubmitted" Message Displays When Using Azure Item Count at Target is Increased When Migrating Using the Azure Pipeline Custom Lists with Versioning Enabled Not Being Migrated When Using the Azure Pipeline Supported Nintex Actions for SPO Migration "Insufficient Credentials" Message Connecting to Modern Team Site Using Web Browser Authentication Error Making a Browser-Based Connection with PowerShell Console Open
About Us

Configuring Email Notification Settings

When you click the [...] button from the General Options dialog - Send Email upon Job Completion option, you can configure settings to have Metalogix Content Matrix send a "Success" or "Failure" email notification to a specified account (or accounts) once a migration has been complete.

NOTE:  The "Success" or "Failure" status of the migration is determined by the status in the job file. If the overall job status is listed as "Successful" in the Job List section, the "Successful" message will be sent. If the overall job is listed as a "Failure" in the Job List section, the "Failure" message will be sent. If there are any failures within the job, but the overall status is listed as "Successful," then the "Successful" message will be sent.

This is not to be confused with Copying SharePoint's Email Notification Settings as part of a migration.

Send Email Configuration

Example Email Templates

You must specify HTM or HTML or basic message templates for both successful and failed migrations, as shown in the examples below.

NOTE:  Metalogix Content Matrix will process the HTML, and replace the <ML*> tags in the templates with the actual content.

Example of "Successful" HTML Template

<b>Success: </b>
<MLJobName><br>
<MLSource><br>
<MLTarget><br>
<MLStartTime><br>
<MLStatus><br>
<MLFinishedTime><br>
<MLDuration><br>
<MLLogSummary><br>

Example of "Failure" HTML Template

<b>Failure: </b>
<MLJobName><br>
<MLSource><br>
<MLTarget><br>
<MLStartTime><br>
<MLStatus><br>
<MLFinishedTime><br>
<MLDuration><br>
<MLLogSummary><br>

To configure Email Notification Settings:

1.For Server, enter the network name of the email server that the email will be sent from.

2.For Connect as, select the useraccount to connect to the specified server; either:

§the user account that is currently running Metalogix Content Matrix

OR

§Different user - Selecting this option will allow for you to enter a specific set of user credentials (User name/ password) to use when connecting to the server.

3.For From:, enter the email account that the message should be sent from.

4.For To: enter the email account or group that the notification email should be sent to.

5.For CC: enter any email accounts or groups that should be copied on the notification.

6.For BCC:, enter any email accounts or groups that should be blind-copied on the notification.

7.For Subject: Enter the subject line for the email notification.

8.Configure the Email Templates for Success and Failure (which must be HTM or HTML files) by entering the path to the template, or click the [...] button and browse to the template.

IMPORTANT:  Both "Successful" and "Failure" templates must be specified in order for either one to work. If only one the templates is added, neither one will be used.

9.After all the settings have been configured, click [OK] to return to the General Options dialog.

Transformation Options

If Advanced Mode and Custom Transformers has been enabled  you can view, create, and edit Transformers.  Transformers are used primarily to “transform” fields and columns into Managed Metadata. There are also several built-in, non-editable transformers that Metalogix Content Matrix uses to process data during the migration.  Advanced users can also create custom transformers using PowerShell.

The Transformations tab is divided into two sections:

·The Available Definitions section list all of the transformation definitions that are available for the current migration action, in alphabetical order.  Only definitions that are valid for the level at which the migration was initiated are listed.

·The Applied Transformers For <Object> dialog displays all of the transformations for the selected definition.

Grayed out items are mandatory transformations that are run during the course of a normal migration, and these actions cannot be edited or removed. However, they can be reordered by using the up and down arrows to the right-hand side of the window. This allows you to create and apply a transformation action before a mandatory action, if you want your action to run earlier in the process. You can even add a second instance of a mandatory transformer to run at a different stage of the migration process.

Transformation Options

Transforming a Site or List Column into a Managed Metadata Columns

Metalogix Content Matrix can transform SharePoint site or list columns (fields) into Managed Metadata columns, as a part of a migration. This allows users to transform columns on the source into SharePoint Managed Metadata columns on the target.

Column to managed metadata transformation settings are not preserved, so they will have to be configured for each migration that is run.

Additional Considerations for Site Column Transformations

A site column can be transformed into a managed metadata column even if the site column's root site is not being migrated. In this case, Metalogix Content Matrix will add the managed metadata site column(s) to the top level site that is included in the migration, and all of the content in the scope of the migration will inherit these new site columns in place of the old ones. When applying a transformation of site columns in a migration, the site columns transformation will be applied to all of the content within the scope of the action that uses the specified site column. This includes any sites, lists, libraries and even content types that use the site column, and are within the scope of the migration.

For example, if a subsite is being migrated to the target, and this subsite contains lists and/or content types that use a site column which is inherited from the top level site, then when the sub site is migrated these inherited site columns will be replaced by new managed metadata site column. These new managed metadata site columns will use the subsite as their root site (since it was the top level site), and all of the content within the migration scope will inherit these new columns instead of using their original site columns. All the data for these columns will be converted to managed metadata values. Any site columns within content types (in the scope of the migration) will be converted the same way, and placed at the top level site in the migration.

Related Documents