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

Copying Alerts as a Post-Migration Task

Metalogix Content Matrix can copy:

·Site, list, and item level alerts to SharePoint on-premises targets

·Site and list (but not item) level alerts to SharePoint Online targets

Advanced Mode Icon  This option is only available when Advanced Mode is enabled.

Alerts can be copied only as a separate, post-migration action, using the context (right-click) menu, or by creating a job/batch file.

NOTE: It is recommended that alerts not be migrated within five to ten minutes of the site, list or item being migrated to the target. This is to avoid the risk of having SharePoint send out any unnecessary email alerts regarding any modifications (migrations) that may have been made.

Connection icon

For SharePoint on premises targets:

Alerts cannot be copied to or from any SharePoint site that is using the Native Web Service (NWS) connection type, because its methods cannot properly fetch, copy, or paste the necessary alerts data.  When using another connection type, such as a Database connection or an Object Model connection through the local connection or the Extensions Web Service, the migrating user (or the Web Service account) must have access to the alerts either in SharePoint or through the database.

For SharePoint Online targets:

·Alerts can only be copied using the Azure Migration Pipeline, to which your SharePoint Online target environment must be connected. Metalogix Content Matrix must also be configured to support the use of the Azure Pipeline for migrations. Refer to the PDF document entitled Metalogix Content Matrix Performance Optimization Guide for Metalogix Content Matrix configuration requirements.

If your scope includes lists not supported by the Azure Migration Pipeline, the migration of alerts for the unsupported lists will fail.

·Target objects (site, list, and item) must have the same ID on the target as they do on the source (which means that, as part of the migration, the option to Preserve IDs on items/folders must have been checked on the List Content Options dialog).

To copy alerts as a post-migration action:

1.In Explorer View, select the source site, list, or item from which you want to copy alerts.

EXCEPTION: The migration of alerts for individual items is not supported for SharePoint Online targets.

2.Select the target object to which you want the alerts copied.

3.Right-click, and choose Copy [Object].

NOTE:  Item level alerts can only be copied one at a time.

4.Select the target object to which you want to copy the alerts, right click and choose Paste Site Objects > Alerts.

5.On the Configure Alert Coping Options dialog, check the applicable option(s):

§Recursively Copy Alerts for all Child Sites - This will copy alerts for all sites and lists recursively down through any content, within the scope of the migration. Item level alerts are not included in this option.

§Recursively Copy All Item Alerts - This will copy all item level alerts recursively down through any content, within the scope of the migration.

§If the target is SharePoint Online, the following additional options display:

§Use Azure Office 365 Upload - This option is checked and grayed out by default, as it is currently the only supported method for migrating alerts to SharePoint Online.

If you attempt to migrate alerts to SharePoint Online and the Azure Migration Pipeline is not configured, the operation will fail.

§Encrypt Azure Migration Jobs - If you want migration job manifest files encrypted, check this box.

Configure Copy Alerts Option

Now you can save or run the action.

Alert Migration Error Handling

When copying alerts Metalogix Content Matrix will check to see if the user already exists on the target. If the user the alert is assigned to does not exist on the target, then Metalogix Content Matrix will try to copy that user to the target before the alert is copied. If for some reason the user cannot be copied to the target an error message will be placed in the log file.

In the case that alerts are not turned on, in the target SharePoint server, Metalogix Content Matrix will give the following error:

Exception thrown: Server was unable to process request. ---> Alerts have been turned off for this virtual server. For assistance, contact your server administrator.

To resolve this issue, activate the alerts feature on the target SharePoint server, and try the migration again.

Copying Audiences as a Post-Migration Task

Metalogix Content Matrix can copy audiences if:

· You are copying to a full, on premise version of SharePoint

NOTE: References to Distribution/Security Groups will be preserved as long as the source and target systems are running the same version of SharePoint and are both using the Active Directory (AD). References to SharePoint Groups will always be preserved as long as the groups themselves have been copied to the target.

AND

·The Target Type is "Farm" or "Web App"

NOTE:  Audiences do not exist in WSS 2.0, WSS 3.0, or SharePoint Foundation.

Advanced Mode Icon  This option is only available when Advanced Mode is enabled.

References to Distribution/Security Groups will be preserved as long as the source and target systems are running the same version of SharePoint and are both using the Active Directory (AD). References to SharePoint Groups will always be preserved as long as the groups themselves have been copied to the target.

Connection icon

The source and target farms must use an Object Model (OM) connection (through the local connection or the Extensions Web Service), in order to map references to audiences between servers.

NOTE:  Because an OM connection cannot be made to an SPS 2003 or Office 365 source, their audiences cannot be copied.

Prerequisites for Copying Audience

In order to copy audiences, the migrating account must have permissions to manage audiences.  Refer to the following Microsoft TechNet articles for details:

·For SharePoint 2007 (personalization services): https://technet.microsoft.com/en-us/library/cc263168(v=office.12).aspx

·For SharePoint 2010 (User Profile Service): https://technet.microsoft.com/en-us/library/ee721065(v=office.14).aspx

·For SharePoint 2013 (User Profile Service): https://technet.microsoft.com/en-us/library/ee721057.aspx

It is also recommended that It you migrate MySites before copying and  compiling audience memberships, because User Profiles (which are copied as part of a MySite migration), can then be added to the audiences, so when the audiences are compiled into audience memberships they will have the MySites User Profile data added to these memberships as well.

If MySites are not copied first, and the audiences are compiled before the MySites are migrated, then a second compiling of audiences would be necessary after MySites are migrated, so that the User Profile data of the MySites can be added into the audiences and compiled into audience memberships.

To copy Audiences as a post-migration task:

After audiences are copied over, a compilation of them will need to be done in order to get the audience membership. Metalogix Content Matrix also can run this compilation as a part of the audience copying process, so that it doesn't have to be done separately.

1.In Explorer View, navigate to the source Farm or Web App node that you want to copy audiences from.

2.Right-click, and choose Copy Farm Audiences.

Copy Farm Auditences Menu Option

3.Select the desired target server node.

4.Right-click and choose Paste Audiences.

5.In the Configure Audience Copying Options dialog select the appropriate How should existing audiences be handled? option.  Use the information in the following table for guidance.

Configure Audience Copying Options

If you want to …

Then …

delete all audiences that exist on the target site prior to migration

select Delete all existing audiences.

delete only audiences on the target that have the same name as an audience that is being copied.

select Overwrite existing audiences.

only copy audiences that do not already exist on the target.

select Preserve existing audiences.

NOTE:  If audience with the same name already exists on the target, it will not be copied from the source.

6.If you want Metalogix Content Matrix to do a compilation of the audiences in order to populate audience memberships, check the Start audience compilation after migration box.

NOTE:  If this option is left unchecked, audience memberships will not be populated. The audience compilation would then need to be started manually], or through a subsequent audience  migration action.

7.Select any other desired migration options from the General Options tab.

Now you can save or run the action.

Copying SharePoint's E-mail Notification Settings as a Post-Migration Task

Metalogix Content Matrix can do a post-migration copy of the source SharePoint environment's email notification settings. This is SharePoint's own site/list email notification setting (not to be confused with Metalogix Content Matrix Console's own email notification setting for sending an email when a migration completes).

Advanced Mode Icon  This option is only available when Advanced Mode is enabled.

To copy SharePoint Email Notification Settings:

1.In Explorer View, select to the site or list for which you want to copy the email notification settings.

2.Right-click, and choose Copy [Object].

3.Select the target node under which you want to copy the notification settings .

4.Right-click and choose Paste Site Objects > E-Mail Notification Setting.

5.Paste Email Notification Settings

 

A message displays warning about the possibility that an email notification may be sent out if the selected target has been modified (by a migration or any other action) within the previous five minutes. Click [OK] to continue.

5.If you initiated the action at the site level, select the desired option(s).  Use the information in the following table for guidance.

NOTE:  If you initiated the action at the list level, the action will automatically run without further configuration.

Configure Email Notification Settings

If you want to …

Then …

migrate the source e-mail notification settings (for all lists that have this setting configured) for all sites and sub-sites under the selected target node

select Copy notification settings recursive in subsites.

Rename mappings between the source and target

·Select Sites and lists renamed on target.

·Click […] and in the Specify new names of sites and lists dialog, configure the renamed mappings.

For example, if a list was renamed during the initial migration, you could use this option to create a rename mapping from the lists old name to the lists new name. then when the E-mail notifications are migrated Metalogix Content Matrix will look for the new list name instead of the old list name.

Now you can save or run the action.

Copying List Views as a Post-Migration Task

By default, a migrated list uses the list type-specific Default view on the target.  You can, however, copy custom views from the source list to one or more target lists as a separate, post-migration task.

Advanced Mode Icon  This option is only available when Advanced Mode is enabled.

To copy list views as a post-migration task:

1.In Explorer View, select the list whose view(s) you want to copy.

2.Right-click and choose Copy List.

3.Select the target list(s) to which you want to copy the view(s).

4.Right-click and choose Paste List Objects > Views.

5. On the Configure List Views Copying Options  List Views Options tab, make sure the Overwrite Existing Views box is checked.

Copy List Views

NOTE:  You can also configure Web Part Options and General Options for the list(s) as part of the action.

6.Now you can save or run the action.

Related Documents