Preserving themes for a site requires Metalogix Content Matrix to use an Object Model (OM) connection on the target side, through the use of the local or the Extensions Web Service connection. The Native Web Service (NWS) connection on the target cannot properly set some of the data required in order to preserve the themes.
When migrating to/from SharePoint 2013 or later (including O365), Metalogix Content Matrix will migrate some additional required components when preserving themes. In these versions there is a hidden list called "Composed Looks" that contains some of the Theme information, and this list also references the MasterPage Gallery for additional information. Metalogix Content Matrix will also migrate the corresponding items from the "Composed Looks" and MasterPage Gallery. This will be done for each theme that is copied, so if only the current theme is copied, only the related item from the "Composed Looks" list and the related MasterPage Gallery item will be copied as well. If all themes are copied, then all items in the "Composed Looks" list and MasterPage Gallery will be copied.
Metalogix Content Matrix can migrate SharePoint 2003 portal listings into SharePoint 2007 and SharePoint 2010. Since portal listings do not exist in SharePoint 2007 and 2010 instances, they are migrated to the target by copying them into links lists.
There are three basic types of portal listings in SharePoint 2003. They are:
·Links that point to content - These are the most common type of portal listing, and they are links that redirect users to other content.
·Person listings - When selected, these links will open a new e-mail to contact the named person.
Note: When migrating Person portal listings, must be made/run first, in order to properly link correct the users from the source to the target.
·Listings that have their own HTML content (not just links to other content).
NOTE: For listings that have their own HTML content, a listing will be created in the Portal Listings links list (the same as all other types of portal listings), but the HTML content itself will be added in a separate document library called Portal Listings Data, which is created to hold this additional data. Inside the Portal Listings Data document library a web part page with a single content editor web part is created and added to display the HTML content.
All three of these portal listing types can be migrated when using Metalogix Content Matrix, and all three can be done in a single step. However, there are some limitations when migrating portal listings. These limitations mainly come into play if using a Native Web Service (NWS) connection to the SharePoint 2003 source, instead of using a Database (DB) connection.
If the NWS connection is used to the source it will not be able to fetch the Last Modified By value for the data. The last modified date would be copied, but not the last modified user. The NWS connection would also run this type of migration much slower, as it can only fetch the listing IDs (and some other metadata) one file at a time, and cannot fetch them in bulk. And lastly, if using the NWS connection on the source there is a group field that Metalogix Content Matrix cannot fetch the values for, so if any customizations have been made to this field, they will not be preserved.
NOTE: When this option is selected as part of a site level migration the Link Correction and Comprehensive Link Correction options under the General Options tab are both checked and disabled because they are required for migrating portal listings.
Metalogix Content Matrix can copy over site features and activate them as a part of a site level migration. Metalogix Content Matrix does not actually copy over the feature itself, it only adds the feature to the target site and activates it.
In order for the feature to be added to the target site it must first be manually installed and available on the target server. If the features from the source do not exist on the target, the migration of features will fail, but the remaining content will continue to copy over.
Metalogix Content Matrix can copy managed metadata values for items and copy and map term stores from a SharePoint 2010 or later (including Office 365) environment into a target SharePoint 2010 or later environment (including Office 365 when a Tenant connection type is used).
Managed Metadata term stores are created through SharePoint Central Administration, and consist of the following managed metadata: Groups, Term Sets, and Terms. Term stores cannot be created by Metalogix Content Matrix, which means that the target side term store must be manually created before any content is migrated. After a term store is created on the target, all the managed metadata and term hierarchy structure from the source can be migrated.
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 and later 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.