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

Applying Content Types to Lists and Libraries

Metalogix Content Matrix can apply content types to SharePoint lists and libraries, and can also map items in lists to the newly applied content types (or map new items in a list to an existing content type).

Advanced Mode Icon These options are only available when Advanced Mode is enabled.

This option can be useful when migrating a list and applying a new content type to that list and its items. Another example would be if items are being copied from the source site to a different existing list on the target, and a different content type needs to be applied to those items.

When the [...] button is clicked from the List Content Options tab , one of the following dialogs displays:

· Apply Content Types to Lists (if migrating a site)  

Apply Content Types to Lists

NOTE:  Any existing mappings display in the bottom section of the dialog.

OR

·Content Type Application Options dialog (if migrating a list or items).

Content Type Application Options

To apply content types to a list or library:

1.In the dialog's top section, use the explorer tree view window to navigate to, and select, the list or library that the content type(s) will be applied to.,

2.Either:

§ click the Apply Content Types to Selected List button at the top of the dialog. to display the Content Type Application Options dialog.

OR

§use the Apply Content Types via Rule option to display the List Filter Conditions window, and apply filter expressions.  

Note that the left From the left (Content types on target site) window lists all of the available content types that exist on the target SharePoint instance.

Content Type Application Options

4.From Content types on target site window,  select all the desired content types you want to be applied to the selected list, and move them to the right (Content types to apply) window.

5.Select any of the remaining options that you want to apply.  Use the information in the following table for guidance

If you want to ...

Then ...

map a content type column on the source to a column on the target, as the new content type column

A.Check the Map source data to new content type columns box.

B.Click the [...].] button to display the Edit Column Mappings dialog.

C.Continue with the procedure for Mapping Columns.

map items from the source into a new content type on the target based one or more specified filters

A.Check the Map source data to new content type columns box.

B.Click the [...] button to display the Map Items to Content Types dialog.

C.Continue with the procedure for Mapping Items to Content Types.

NOTE:  This option is available only when migrating Exchange folders (not individual items).

change the default content type  for the target list or library

A.Check the Change default content type box

B.Select a content type from the drop-down.

NOTE:  When you check this box, the Add unmapped items to the default content type is automatically enabled and checked.

Mapping Items to Content Types

You can specify content types for target items when you click the [...] button from the Content Type Application Options dialog.

To map items to content types:

PF Map Items to Content Types

1.Select the content type, and click [Edit Conditions] to display the List Items and Documents Where filter dialog.

2.Select the filter(s) you want to apply as you would when Applying Filter Expressions.

NOTE:  If you select [Clear Condition], all conditions that are currently applied to that content type will be cleared.

3.Once all filters have been set, click [OK] to return to the Content Type Application Options dialog.

Applying New Document Sets to Libraries, Folders, and Documents

Metalogix Content Matrix can apply Document Sets to libraries, folders, or documents as a part of a migration. Document Sets can be applied when migrating to SharePoint 2010, 2013, 2016, or Office 365 environments, and can be configured at the time of migration. This feature allows for any SharePoint folders, or document libraries to be migrated as a SharePoint Document Set. Please see Microsoft's Document Sets planning page for more basic details on document sets.

NOTE:  If you want to apply an existing Document Set to a list, library, or folder, initiate a list-level migration and paste the object to a Document Set on the target.

When you check the Apply new document sets during copy check box and click the [...] button from the List Content Options dialog, the Apply Document Sets dialog displays.  

Apply Document Sets

To apply new Document Sets:

1.In the upper (tree view) window, select the content to which you want to apply the Document Sets.

2.Select the appropriate Apply Document Set option.  Use the information in the following table for guidance.

If ...

Then ...

·you selected a folder

AND

·you want to apply a Document Set Content Type

A.Select Apply Document Set to Selected Folder to display the Document Set Content Type dialog.

Document Set Content Types

B.Select an available Content Type from the drop down.

C.Click [OK] to dismiss the Document Set Content Dialog and return to the Apply Document Sets dialog, which now displays the newly added mapping in the Folders tab.

·you selected a document library

AND

·you want to apply  a new Document Set  to all or selected items within the library based on a filter expression

A.Select Apply New Document Set To Library to display the Map Documents to Document Sets dialog.

Map Documents to Document Sets

B.Click [New Document Set] to display the Enter Name dialog and enter a name for the new Document Set.

C.Click [OK] to dismiss the Enter Name dialog, and display the Document Filter Conditions dialog.

D.Apply the desired filter expressions for the item-level Document Set.

NOTE:  If no condition filter value is entered in the Document Filter Conditions dialog, no items in the document library will be applied to the Document Set.

E.Click [OK] to dismiss the Document Filter Conditions dialog and re-display the Map Documents to Document Sets dialog.

F.Select the appropriate Content Type to apply to the Document Set from the drop-down.

G.Click [OK] to dismiss the Map Document Sets dialog and return to the Apply Document Sets dialog, which now displays the newly added mapping in the Lists tab.

·you selected a site

AND

·you want to apply new Document Sets lists and/or items on the site based on filter expressions

A.Select Apply New Document Set via Rule to display the Lists Filter Conditions dialog.

B.Apply the desired filter expressions for the list-level Document Set.

List Filter Conditions

C.Click [OK] to dismiss the List Filter Conditions dialog and display the Map Documents to Document Sets dialog.

D.Click [New Document Set] to display the Enter Name dialog and enter a name for the new document set.

E.Click [OK] to dismiss the Enter Name dialog, and display the Document Filter Conditions dialog.

F.Apply the desired filter expressions for the item-level document set.

G.Click [OK] to dismiss the Map Document Sets dialog and return to the Apply Document Sets dialog, which now displays the newly added mapping in the Lists tab.

H.Repeat Steps A-G to apply lists and items within the site to document sets.

·you initiated an item-level migration

AND

·you want to apply a new document set to individual items to  based on filter expressions

A.Select Apply New Document Set via Rule to display the Map Documents to Document Sets dialog.

B.Click [New Document Set] to display the Enter Name dialog and enter a name for the new document set.

C.Click [OK] to dismiss the Enter Name dialog, and display the Map Documents to Document Sets dialog.

D.Apply the desired filter expressions for the item-level document set.

E.Select the appropriate Content Type to apply to the document set from the drop-down.

F.Click [OK] to dismiss the Map Document Sets dialog and return to the Apply Document Sets dialog, which now displays the newly added mapping in the Lists tab.

Note that you can use the Navigate To option to locate the object to which a selected filter applies in the upper (tree view) window.

Managed Metadata Options

The Managed Metadata (or taxonomy) options are available when migrating from SharePoint 2010 Server or later (including Office 365 tenants), and can be selected at all migration levels (site collection, site, list, and item).

NOTE:   For these options to function properly the term stores must be created on the target before migration, which will then allow for the migration (and mapping) of the terms, and the migration of data using these terms.

Connection icon

You can migrate Managed Metadata using any of the following connection types:

·Object Model (OM) Connection - This is either a Local or Remote (Extensions Web Service) connection type and can be used for SharePoint 2010, 2013, and 2016 source/target environments.

NOTE:  You can also use either of these connections to migrate managed metatada using GUID Mappings, which may significantly improve performance over choosing to Resolve by Name and Hierarchy, which requires Metalogix Content Matrix to crawl through the entire term store.

·Office 365 Tenant Connection - This is a server level connection to an Office 365 Tenant environment. If using an Office 365 Tenant environment as a source, this is the only connection that can be used. If using any other environment as a source, this connection type can only be used as a target.

·Client Side Object Model (CSOM) connections  This connection type can only be used by Office 365 environments, and can be used for either a source or target connection.

·Database Connections - This connection is only supported as a source connection for the migration of metadata using GUID Mapping . There are prerequisite actions to be performed before using this connection type.

 

You cannot migrate managed metadata when the source connection is NWS, because neither term store migration nor GUID Mapping is supported.

Prerequisites for transforming columns into Managed Metadata:

You can migrate Managed Metadata only if all of the following conditions are met:

·You are migrating into a SharePoint 2010 Server or later target and the migrating account has the following permissions for the Term Store that will be used:

§Full Access to Term Store and Term Store Administrator for the Managed Metadata Service being used on the target

§Additionally, for O365 environments: Global Administrator and Term Store Administrator.

NOTE:  It is recommended that the same permissions be set on the source, although Read permissions may be sufficient, depending on your environment).  If you encounter the error The Managed Metadata Service is inaccessible because the current web application has not been granted permissions to access it, it may also be necessary to add the account that the App Pool user is running under in order to have permissions.

§When migrating at the site collection level, or when migrating the Term Store explicitly, it is highly recommended that you map term stores before migration to ensure that the correct term store is being used.

NOTE:  A 1:1 relationship must exist between Source/Target term store mappings.  That is a term store from the source can only be mapped to one term store on the target, and the same target term store cannot be mapped to more than one source term store.

·You are migrating using the Full Copy mode. (These options are not currently available when running an Incremental copy.)

·When using the Resolve managed metadata by name and hierarchy option, make sure that the default storage location for column specific term sets option is enabled in the target SharePoint environment.  See the following TechNet article for more information for SharePoint 2013/2016.

Related Documents