Chat now with support
Chat with Support

Metalogix Content Matrix 9.3 - SharePoint Edition User Guide

Introduction Entering the License Key Content Matrix Console End User Interface Enabling Advanced Mode Connecting and Migrating Account Requirements Connecting to SharePoint Preparing for a Migration How Content Matrix Handles Various SharePoint Components
How Team Sites are Migrated to Modern Team Sites How Publishing Sites are Migrated to Communication Sites How MySites are Migrated How Records Centers are Migrated to SharePoint Online Using the Import Pipeline How Master Pages are Migrated How List Template Galleries Are Migrated How Content Types are Migrated Document Version and Checked Out File Limitations How Ghosted and Un-Ghosted Pages are Migrated How Document Sets are Migrated How Navigation is Migrated How "Share With" Metadata is Migrated to SharePoint Online Using the Import Pipeline How Web Parts are Migrated How Site Themes are Preserved How Site Features Are Migrated How Managed Metadata, Terms, and Term Stores are Migrated How Users and Permissions are Migrated How BCS/BDC Data is Migrated How OneNote Notebooks are Migrated How Customized Form Pages are Migrated How InfoPath Forms are Migrated How SharePoint Workflows are Migrated How Nintex Workflows and Forms are Migrated How Link Correction Works
Initiating a Migration Configuring Copying Options Saving or Running a Migration Job Copying SharePoint Objects as a Separate Action Converting Classic Pages to Modern Pages After a Migration Incremental Migration Using PowerShell with Content Matrix
Configuring PowerShell for Use with Content Matrix Creating and Running a PowerShell Script 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 Migration Frequently Asked Questions
DB_Owner Permission 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 Migrating SharePoint On Premises 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 Migrating JavaScript Migrating Site Variations Migrating with SharePoint Document IDs Changing a Job Configuration for Multiple Files 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 How Do I Identify and Remove Containers and Queues from My Azure Private Storage Account? Import Pipeline Batches Getting Stuck "Error, the batch will be resubmitted" Message Displays When Using the Import Pipeline Item Count at Target is Increased When Migrating Using the Import Pipeline Custom Lists with Versioning Enabled Not Being Migrated When Using the Import Pipeline Supported Nintex Actions for SPO Migration Support for GCC High Tenants
About Us

Using Older Versions of the Extensions Web Service

Question

Can I use an older version of the Metalogix Extensions Web Service with a newer version of the Metalogix Content Matrix Console?

Answer

It is not recommended to use older versions of the Metalogix Extensions Web Service with newer build of Metalogix Content Matrix, but this is possible after build v5.0.0.6. In order to use an older version of the Web Service some configuration changes must be made. To do this, close the Metalogix Content Matrix Console and go to its installation folder (for example, C:\Program Files (x86)\Metalogix Content Matrix Console - SharePoint Edition). Find the WebServiceConfiguration.xml file, and edit it.

This file will list the default Web Service version number, which can be modified. The format of this entry should be:

<WebServiceConfiguration>
<Server Name="default" WebServiceVersion="[Version Number5.0.0.6]" />
</WebServiceConfiguration>

Once the old version number is specified, save the XML file and re-open the Metalogix Content Matrix Console.

It is possible to add additional lines to this code to specify server names. In most cases these additional lines only need to be added if connecting to different (or multiple) servers, and these other servers are using a different version of the Metalogix Extensions Web Service. Any number of lines can be added for additional servers. If added, any additional lines will apply the server name and version number to any Web Service connections that are made to the specified server. The default Web Service version number value will be used for all other connections. If connecting to a site that uses Alternate Access Mappings (AAM) that point to a different URL, a separate entry will need to be made for the AAM.

The format for any additional lines is:

<Server Name="http://[ServerName]" WebServiceVersion="5.0.0.6" />

If a newer version of the Metalogix Content Matrix Console is installed the WebServiceConfiguration.xml file will be overwritten, so any manual changes that were made will need to be entered again.

Migrating JavaScript

Question

Can I use Metalogix Content Matrix to migrate JavaScript content from my source to my target SharePoint server?

Answer

It is possible to migrate some JavaScript using Metalogix Content Matrix, depending on the type of JavaScript being migrated. If the JavaScript from the source is embedded in a Content Editor Web Part, or embedded in a publishing page (in a pages library), it should be migrated the same as other SharePoint content. If the JavaScript is not embedded in either of these, then it will not be migrated with Metalogix Content Matrix. JavaScript can only be migrated into SharePoint, in locations that SharePoint itself will allow JavaScript to be manually added (in web parts and publishing pages).

There are two things to keep in mind if migrating JavaScript that is embedded in web parts or publishing pages. The first is that any links in the JavaScript will not be corrected. This is because the links are also embedded in the content, so they would not be picked up as part of the link correction process. These links must be manually corrected. In order for Metalogix Content Matrix to correct these links it would have to edit the actual contents of the web part or publishing page, and this is something we try to avoid.

The second thing to keep in mind is that if the Reattach Publishing Page Layouts check-box is selected any customizations for the page (including JavaScript and any other customizations) will be lost.

Migrating Site Variations

Question

Can Metalogix Content Matrix migrate site variations?

Answer

Yes, Metalogix Content Matrix does have the ability to migrate SharePoint site variations. In order for site variations to correctly migrate the Site Variation feature must be enabled on the target SharePoint environment before the migration. When the site content is migrated using Metalogix Content Matrix, the content is copied into the target location, and it is actually the SharePoint API that creates the site variations.

If there are any special variation configurations on the source content, these configurations would need to be recreated on the target environment prior to migration.

Migrating with SharePoint Document IDs

Question

What is the difference between SharePoint 2007 document IDs, and the SharePoint 2010 and later Document ID feature? And what is the difference between the various ID preservation options that are available in the List Content Options tab in the Configure Copy Options dialog?

Answer

There are three types of ID's that can be preserved when migrating content in Content. Each of these ID types has its own check-box option on the List Content Options tab in the Configure Copy Options dialog. A breakdown of each of these ID types and their available migration options is below:

·SharePoint List Item IDs - These are IDs on SharePoint List items and folders. SharePoint lists can contain items and folders, and these items and folders are a collection of data that is strictly in SharePoint (meaning that there are no actual documents, such as DOC files, CSV files, etc.). The IDs for SharePoint List content are contained in an ID field in the list metadata, and these ID values are used by SharePoint to differentiate (as a unique identifier) all of the items and folders in the list. The values are incremented whenever a new item is added to the list.

These types of IDs can be preserved when migrating content, as long as there is an Object Model (OM) connection to the target (either through a Local connection, or the use of the Metalogix Extensions Web Service), and the Preserve IDs on items/folders in Lists option is selected.

·SharePoint Document Library Item IDs - These are IDs on SharePoint Document Library documents and folders. Document Libraries and folders use the document's filename (and path) as the unique identifier, however, there is still an ID value for each document. This ID value is instead used to help with document ordering in most cases, although it can be set up as a unique identifier as well. The values for this data are contained in an ID column, and the values will increment when a new document is added to the document library.

These types of IDs can be preserved using the Preserve IDs on items/folders in Document Libraries option, however, this action is not normally available, and requires some special configuration before it can be used. This option is mainly for use if performing incremental copies of document libraries. If this option is not used then SharePoint itself will automatically assign this value. For more information on how to enable this option, please contact Quest Support.

·Document ID Service - The use of these types of IDs started with SharePoint 2010, and are only available if the Document ID Service feature is enables at the Site Collection level. These ID values are a little different because these IDs can be directly linked to documents and document sets in SharePoint. The benefit of this is that it creates a URL for that specific document or document set, and that URL can always be used to directly access that document no matter where it is moved to within the Site Collection (because it uses the document ID in the URL instead of giving a file path). The values for this type of ID are contained in the Document ID column. For more information on the SharePoint Document ID feature please see the following MSDN article: http://msdn.microsoft.com/en-us/library/ee559302.aspx.

These types of IDs can be preserved by using the Preserve SharePoint Document IDs (Requires SharePoint Crawl) option. This option is only available when migrating from SharePoint 2010 or later sources into SharePoint or later target environments (any SharePoint connection adapters can be used). In order for the Preserve SharePoint Document IDs option to work the Document ID Service feature must be activated on the target Site Collection before migration.

When this option is used the migrated documents or document sets will use the same ID value on the target as they had on the source. However, because the ID value might not conform to the target Site Collection's Document ID standard, the URL for the document or document set will not immediately work on the target (the URL would still work on the source). In order for this URL value to work in the target environment users must run a SharePoint Crawl action on the target web application. After performing the crawl the Site Collection will be able to find the document or document set based on the URL using the ID value. Any old links that incorporate the ID value for the migrated document or document set will work, provided link correction has also been used.

NOTE: If content is migrated to the target, and this Document ID is preserved, but there are also documents that already exist within the Site Collection, and two or more of these documents or document sets use the same ID value, then when the the link is used SharePoint will open a Search results page, and display all of the documents or document sets that use this same ID. Users can then select the specific document or document sets they are trying to access.

 
If the Preserve SharePoint Document IDs (Requires SharePoint Crawl) option is not used, the migrated documents or document sets will automatically be assigned a new Document ID value by the target Site Collection, the same as if the document or document set has been manually uploaded. This means that the document or document set will get a new URL containing its new Document ID value, and the links for these Document IDs can be used immediately.

SPECIAL CASE: When documents or document sets are migrated into a SharePoint 2010 or later site collection with the Document ID Service feature disabled, some of the documents or document sets will still have their source Document ID value and Document ID URL. This happens when the documents or document sets that are being migrated contain some specific metadata that SharePoint will automatically push into these columns. This most often happens with certain file types, like DOCX files and other Microsoft file types. If connected to the target SharePoint 2010 or later environment using the Object Model (OM), via a Local connection or the Metalogix Extensions Web Service, then users can use the Disable SharePoint Document Parsing option (located in the List Content Options tab in the Configuration Copying Options dialog), and this should cause Metalogix Content Matrix to no longer read these fields when migrating the documents or document sets.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating