Chat now with support
Chat with Support

Metalogix Content Matrix 8.8 - SharePoint Edition User Guide

Introduction Entering the License Key Content Matrix Console End User Interface Enabling Advanced Mode Connecting to SharePoint 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 2010/2013/2016 Document IDs Changing a Job Configuration for Multiple Files SharePoint 2003 Version Migration Limitations SharePoint 2013 and 2016 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 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

Global Mappings

When you click [Open Global Mappings] (from the Simplified mode Migration Options - Site Element Options section or [Edit Global Mappings] (from the Advanced mode Mapping Options tab), the Specify Global Mappings dialog displays, allowing you to  set:

·User Mappings

·Domain Mappings

·URL Mappings

·GUID Mappings

NOTES:  

·If you are using Simplified mode, User Mappings is the only available option via the interface.  However, all types of mappings can be imported from xml.

·Global Mapping can also be performed as a separate action.  

User Mappings

During a migration, user mappings are carried out in the following order of precedence:

A.Explicit mapping

B.Domain Mapping

C.Auto mapping

D.Mapping missing users

E.Mapping to logged-in user

Explicit User Mappings

Explicit user mappings are generally used when trying to migrate a user account that is "orphaned": that is, it exists on the source but is no longer active (or may not be in Active Directory). While the user may not exist, the user’s data may still need to be migrated to the target.

One alternative to adding such an orphaned user to the target is to map the account to another user account. All of the user’s basic metadata would be migrated, but the user name would be populated with the mapped account name instead.

User mappings can also be imported using the Import mappings from XML option.

If you want to map all users (which includes "orphaned" users) from the source domain to a different domain on the target, you can do so using Domain Mappings.

To configure explicit user mappings:

User Mappings

1.In the Specify Global Mappings dialog, make sure the User Mappings tab is selected.

NOTE:  If you are using Simplified mode, User Mapping is the only option, and tabs will not be displayed.

2.From the Source: drop-down on the left side of the dialog, select the source object containing the users you want to map to the target.

The Source list becomes populated with the users that have permissions for that object.

3.Use the information in the following table to determine the appropriate action to take.

If the user ...

Then …

already exists on the target

A.Select the source user that you want to map.

B.From the drop-down on the right (target) side of the dialog, select the target object containing the user to which you want to map.

C.The target list becomes populated with users that have permissions for the selected object.

D.Select the target user to which you want to map the source user.

does not already exist on the target

A.Click Create New User to display the Create New User dialog.

CONTEN~1_img104

B.(Required) Specify a Login Name.

NOTE: This is the most important field as it is used to create/add a new user and should automatically retrieve any necessary values from the target side authenticator.  Be sure to use the appropriate format for the authentication method (for example domain\user name, the O365 login name, or, if using Claims authentication, the appropriate Claims prefix and format).

C.(Optional) Complete the Display Name and/or Email fields. If the Login Name does not authenticate for any reason, these fields will be used to fill out the user data.

D.Click [OK].

4.Click Map.

The mapping displays in the lower half of the dialog.

5.Repeat steps 2-4 until you have completed mapping users.

NOTE:  You can map multiple source users to a single target user.

Auto User Mappings

Currently, all users will be automatically mapped from a source domain to a domain with the same name on the target when migrating:

·from a SharePoint on premises Object Model connection to SharePoint Online

·across SharePoint on premises domains using an Object Model connection, as long as both domains do not use Claims authentication.

Users cannot be automapped across SharePoint on premises domains that both use Claims authentication.  That functionality will be added in a future release.

For example, if you are migrating users from an Active Directory domain called metalogixtest on the source to a SharePoint Online domain called metalogixtest, the users would be migrated as follows:

In this example, users would be migrated as follows:

metalogixtest\amahfudh -> amahfudh@metalogixtest.com

metalogixtest\doconnor -> doconnor@metalogixtest.com

metalogixtest\fsullivan -> fsullivan@metalogixtest.com

metalogixtest\gbond -> gbond@metalogixtest.com

and so on.

If a user who has been deleted or disabled in Active Directory does not exist at the target, and the Map missing users to: box is checked on the Mapping Options tab, a reference to that user will be created there, so that permissions and Authorship metadata can be retained.

NOTE: In order to be mapped, the source and target user name must match exactly.

Related Documents