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 users 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 users 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:
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. 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 quest on the source to a SharePoint Online domain called questsoftware, the users would be migrated as follows:
In this example, users would be migrated as follows:
quest\amahfudh -> amahfudh@questsoftware.com
quest\doconnor -> doconnor@questsoftware.com
quest\fsullivan -> fsullivan@questsoftware.com
quest\gbond -> gbond@questsoftware.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.
Domain Mappings
In addition to allowing you to map individual users explicitly, Metalogix Content Matrix allows you to map all users from one domain to another, across both SharePoint on premises and SharePoint Online environments.
Domain Mapping can be used in conjunction with explicit user mapping. For example, you can map all users across a domain, and then map specific users into other user accounts.
NOTE: Domain mappings can also be imported using the Import mappings from XML option.
|
|
Domain Mapping supports the following connection types on both source and target: ·SharePoint on premises local and remote (MEWS) Object Model ·SharePoint Online CSOM and Azure/SPO Container. |
|---|
NOTE: If you do not specify an extension for an online domain, .com will be used.
EXAMPLES:
·If you have an on-premises source domain called quest, and you map it to a SharePoint Online target domain called questsoftware.com, you could enter the mapping as shown below.
In this example, users would be migrated as follows:
quest\amahfudh -> amahfudh@questsoftware.com
quest\doconnor -> doconnor@questsoftware.com
quest\fsullivan -> fsullivan@questsoftware.com
quest\gbond -> gbond@questsoftware.com
and so on.
·If you have an on-premises source domain called quest, and you map it to a SharePoint Online target domain called questsoftware.net, you would enter the mapping as shown below.
In this example, users would be migrated as follows:
quest\amahfudh -> amahfudh@questsoftware.net
quest\doconnor -> doconnor@questsoftware.net
quest\fsullivan -> fsullivan@questsoftware.net
quest\gbond -> gbond@questsoftware.net
and so on.
·If you have an online source domain called questsoftware.com and you map it to a target domain called questsoftware.net, you could enter the mapping as shown below.
In this example, users would be migrated as follows:
amahfudh@questsoftware.com -> amahfudh@questsoftware.net
doconnor@questsoftware.com -> doconnor@questsoftware.net
fsullivan@questsoftware.com -> fsullivan@questsoftware.net
gbond@questsoftware.com -> gbond@questsoftware.net
To map domains:
1.In the Specify Global Mappings dialog select the Domain Mappings tab.
2.Click New to display the Create Domain Mapping dialog.
3.Enter the Source Domain name and the Target Domain name. Use the information in the following table for guidance.
|
Source |
Target |
Format/Example |
|---|---|---|
|
On Premises |
On Premises |
Source Domain: quest Target Domain: questsoftware NOTES: When migrating Claims-enabled accounts, remember to include the Claims prefix. For example: i:0#.w|quest -> i:0#.w|questsoftware. |
|
On Premises |
SPO |
Source Domain: quest Target Domain: questsoftware (or questsoftware.com) |
|
SPO |
SPO |
Source Domain: questsoftware (or questsoftware.com) Target Domain: questsoftware.net |
|
SPO |
On Premises |
Source Domain: questsoftware (or questsoftware.com) Target Domain: quest |
4.Click [OK].
URL Mappings
Metalogix Content Matrix can set explicit mappings for URLs which can be used with link correction. While link correction only applies to the content that exists within the scope of the migration, URL mapping can help by-pass this issue for any mappings that are specifically set.
For example, if there is a link within some content that is being migrated, and this link points to a URL location that is outside of the migrating content, a URL mapping can be set up for it. Then after migration, this link will point to the URL that the mapping was set up for, despite the target URL being outside the scope of the migrating content. If there are any other links to content that exists under the location that the URL is mapped to, the links to that sub-content will be corrected as well. For example, if a URL mapping is set to a document library in a location that is outside the scope of the current migration, the URL mapping will correct the links that point to this document library. In addition, any links within the migrating content that are pointing to any folders or documents within the document library will also be corrected. Links that point to that document library's site, or other lists in the same site, will not be corrected.
The URL mapping behavior may change if the URLs being mapped exist within the scope of the migration. In this case the link correction within Metalogix Content Matrix will likely override the URL mapping, if the source link has a mapping created for it through the normal link correction process.
You have the option of using the Sites, Lists, and Folders renamed on target option. This option allows you to specify any sites, lists, or folders that may have been renamed during migration. This is only used for link correction purposes, and will not actually rename any sites, lists, or folders
For example, if a site was renamed during migration, this renaming would be entered here so that the link correction would be able to correctly identify the site and correct all the necessary navigation links for it, during the navigation copy.
You can add as many additional mappings as desired. You can also map a single source URL to multiple target URLs.
URL mappings can also be imported using the Import mappings from XML option.
To map URLs:
1.In the Specify Global Mappings dialog select the URL Mappings tab.
2.In the Source Address column enter the URL for the source location.
This must be a full URL, and cannot be a relative URL. For example, "http://OldServer/Sales/FactsAndFigures" would be a valid URL value, while "./Sales/FactsAndFigures" or "www.OldServer/Sales/FactsAndFigures" would both be considered relative or invalid URL values.
3.Enter a value in the Target Address column.
This is the same relative address as the Source Address, but using the location of the target side URL.
NOTE: Metalogix Content Matrix will check to see if any entered values in the URL mappings window are valid. This check will ignore any letter case differences or encoding (meaning that "encoding space" and "encoding%20space" are viewed as the same). It should also be noted that spaces in the hostname of the URL are not considered valid. This check applies to both the Source Address and Target Address columns.
4.Click [OK] to return to the Specify Global Mappings dialog.