Chat now with support
Chat with Support

Metalogix Content Matrix 8.8 - Blogs and Wikis Edition User Guide

Introduction Entering the License Key Content Matrix Console End User Interface Source Blog and Wiki Structure Connecting to a Source Blog or Wiki Connecting to SharePoint Preparing for Your Migration Initiating a Migration Configuring Copying Options Saving or Running a Migration Action Running Link Correction as a Post-Migration Task 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.Blog.Commands
Modifying Content Matrix Configuration and Settings Frequently Asked Questions About Us

Version Option

Use the Versions Options tab to specify how you want page, post, and document versions to be migrated.

To configure Version Options:

1.If you want Metalogix Content Matrix to Migrate versions, make sure this box is checked.

NOTE:  If this box is not checked, only current version of pages, posts, and documents will be migrated.

2.Use the information in the table below to determine the appropriate option to select.

If you want to migrate ….

Then …

all existing versions of a page, post, or document

select Migrate all Versions.

a specified number of versions of a post, page, or document

·select Migrate latest [number]versions, and

·select the number of versions you want to keep.

Permissions Options

Use the Permissions Options tab to specify how you want source users' Authorship metadata (Created, Created By, Modified, and Modified By fields) to be migrated.

IMPORTANT:

·Users from the source can only be mapped to the SharePoint target if there is some kind of shared Active Directory (AD) between them.

·Migrated permissions will not alter any existing permissions or permission levels on the SharePoint target.  Instead, they will be added to the existing permissions.

To configure Permissions Options:

1.If you  want source users' Authorship metadata (Created, Created By, Modified, and Modified By fields) to be migrated to the target SharePoint instance, make sure the Map user metadata box is checked.

2.Select the applicable sub-option(s).  Use the information in the following table for guidance.

If you want to ...

Then ...

map user accounts between source and target

Click the [...] button.

Follow the procedure for Mapping Users.

NOTE:  This option allows you to map a user account from the source to an existing user on the target SharePoint instance, so users that don't exist on the target can be mapped to another account

have Metalogix Content Matrix use an algorithm to a "best match" mapping of existing site-level permissions between  source and target

check the Auto-map site permissions by best-match box.

NOTES:  

·Metalogix Content Matrix will only auto-map permissions for users who already exist on the target.

·In most cases, sources that have source side permissions will map readers/subscribers into the "Read" permission. Users that were able to write pages or posts on the source will be mapped into "Full Control" on the target.

have Metalogix Content Matrix use an algorithm to a "best match" mapping of existing post/page-level permissions between source and target

check the Auto-map page permissions by best-match box.

NOTES:  

·Metalogix Content Matrix will only auto-map permissions for users who already exist on the target.

·In most cases, sources that have source side permissions will map readers/subscribers into the "Read" permission. Users that were able to write pages or posts on the source will be mapped into "Full Control" on the target.

Mapping Users

You can set user and group mappings for migrating content when you click the [...] button from the Permissions Options tab. This allows you  to preserve authorship metadata as well as help integrate the blor or Wiki users with the SharePoint permissions model. In some cases it is possible for users to be automatically imported into the SharePoint environment, however, this is only possible if the blog/Wiki source and the target SharePoint environment are working from the same Active Directory (AD). If this is not the case, then users would need to be mapped into SharePoint user accounts on the target, and these accounts must already exist in order for them to be mapped from the source.

All user mappings are globally set, so once a mapping is created it will always be used unless removed.

NOTE:  If the source environment has a large number of users/groups, it is recommended that the XML user mapping method be used instead, to help improve performance, and for better control over user mapping.

To map users:

NOTE: Metalogix Content Matrix supports many-to-one user mappings between source and target.

1.To retrieve all users from the source and target environments, click Load Users ...

BW User Mappings

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

NOTE:  You can Filter items in each window to narrow displayed lists.

If you want to ...

Then...

manually map individual users or groups on the source to a target SharePoint user or group

·From the source list, select the Item(s) that you want to map.

·From the target list, select a target Item.

·Click the Map icon.

have Metalogix Content Matrix automatically map source users/groups to target SharePoint users/groups

·From the source list, select the Item(s) that you want to map.

·Click the Auto icon.

NOTE:  Metalogix Content Matrix will only map users automatically if the source and target side names match, or if the emails match, and the source and target environments are using the same AD.

The mappings you create will display in the bottom window.  (Note that you can also Unmap individually-selected mappings in the bottom window or or Clear all mappings from the bottom window.

3.Click [OK] once all desired mappings have been made and return to the Copy Options dialog.

Importing User Mappings from an xml File

Metalogix Content Matrix can import any desired user mappings from an XML file. Importing user mappings from an XML file involves creating an XML file with the desired mappings, then importing that file. This option is generally used if migrating from an eRoom environment that has a large number of users/groups.

To create a an xml file of user mapings:

Create a file, with any name, that contains any desired user mappings. The file can either be text based or an XML file, but must contain a root level node named Mappings, and have one child node for every mapping that you want imported. Each child node must contain two attributes: Source and Target. The Source is the Login Name of the source side user, and the Target attribute is the Login Name of the target user that is being mapped to.

The XML file should follow the below format:

<Mappings>
<Mapping Source="BlogUser1" Target="Domain\User87" />
<Mapping Source="BlogUser2" Target="Domain\User254" />
</Mappings>

NOTE: The Login Names used in the above example may vary depending on the authentication methods used by the source and target environments.

To import the XML file into Metalogix Content Matrix:

1.In Explorer View, select the top-level node of the  select the Blog or Wiki node (this is either a Confluence server node or a WordPress site node).

2.Right-click and choose Import User Mappings to display the Import Users Mappings dialog.

3.Click Import From XML button, then navigate to and open the XML file you want to import.

The Import User Mappings dialog is populated with the mappings contained in the XML file.

BW Import User Mappings POPULATED

 

Now you can:

§delete single mappings (by selecting the desired mapping, and clicking Delete)

§clear all mappings (by clicking Clear)

Any mappings that are listed in the Import Users Mappings dialog are not authenticated until the time of migration. Any spelling mistakes that exist will not be corrected. If a user mapping is not valid, or authenticated, the migration account will be used instead.

4.Click [Save] to continue and add the mappings.

Related Documents