Metalogix Content Matrix can migrate web parts for:
·landing pages (default.aspx pages)
·web part pages
·publishing content pages, and
·list view pages.
Web parts can be copied as part of a normal migration copy or as a separate action.
NOTE: Currently, If you are using Office 365 OAuth with MFA Authentication authentication type, web parts cannot be migrated and all options on the Web Parts tab will be disabled.
Essentially, Metalogix Content Matrix reads the XML information of the web parts, processes the data, and moves it over to the target side, where the XML is then written out on the target location. Metalogix Content Matrix will automatically perform link correction on the data within the web part (the data for the settings), as a part of the migration.
In order for any custom or third party web parts to be properly migrated, these web parts must be manually installed or created on the target server before migration. Metalogix Content Matrix does not migrate the actual code of the web part, it only migrates the data within the web part. In order for an actual migration, the desired web part must first exist on the target SharePoint instance, otherwise the migration will fail.
The migration of web parts does not require the use of the Object Model (OM) connection type on the target (through the use of the Local or Metalogix Extensions Web Service connections). The SharePoint Client Object Model (CSOM) and the Office 365 Tenant (Tenant) connection types can be used to migrate web parts. While there are a few limitations for the CSOM/Tenant connection adapters (mainly around web part views), in regards to web part, both the web part zone and ordering should be preserved.
Metalogix Content Matrix can preserve web part views, however, there are a few known issues with this. In the case of list view web parts, you need to make sure that the list being referenced has already been migrated to the target to ensure that the web part, and it's view, will migrate properly. If the list being referenced in the web part is within the scope of the migration, then Metalogix Content Matrix will make sure the list has been copied first, and will then copy web parts.
There is an additional web part view limitation when using the CSOM or Tenant connection adapter on the target, where Metalogix Content Matrix is unable to set the type of a web part view. The most common manifestation of this is to have a web part lose its calendar appearance during migration. However, the other properties of that view will still be preserved. The resulting outcome will be that the content within the web part will be correct, but it will not look the same as the source because the view type is different. This can be corrected by manually, after migration, by changing the web part view to match the same web part view on the source.
NOTE: In some cases the web part view type may migrate correctly. This can only occur if the web part is using the same view type that it was using when it was first created. However, this behavior is not reliable.
There is also a web part limitation on migrating web part connections. Web part connections are connections that exist between web parts (one web part pointing to another web part, etc.). Metalogix Content Matrix is only able to migrate these web part connections if there is an OM connection type (through the use of the Local or Metalogix Extensions Web Service connections) on both the source and target SharePoint environments. Other connection types are unable to access this setting, meaning that if any other connection type is used on either the source or target, the web part connection setting cannot be preserved. This also means that this setting cannot be preserved when migrating to O365 environments.
Preserving themes for a site requires Metalogix Content Matrix to use an Object Model (OM) connection, either local or remote (using the Metalogix Extensions Web Service (MEWS)) on the target side.
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 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 migrate SharePoint permissions. Permission migration is broken down into two pieces: permission levels, and user/group permissions. This section will review how to migrate permissions for users/groups. Metalogix Content Matrix can migrate site, list and item level permissions from one SharePoint instance to another.
There are two methods of migrating permissions. The first method is to copy permissions as a part of a migration action by selecting them in the Copy Options dialog, and the second method is to copy them to a target node using the context (right-click) menu as a separate action.
When talking about permissions in SharePoint it is important to keep in mind that there are three different aspects of permissions to be considered when doing a migration. They are as follows:
·Roles - These are also known as permission levels, and are a collection of rights that can be assigned. In SharePoint, it is possible to create custom permission levels (or custom roles). Content can migrate any custom Roles.
·Securable Objects - These are basically permissions or rights that can be assigned to an object in SharePoint. Only users or groups that have the same level of permissions or higher can access the content holding these permissions. Metalogix Content Matrix can migrate permissions on securable objects at the SharePoint site, list, folder, and item levels.
·Principals - These are permission roles that are assigned to a user or group. In order for a user or group to have access to a secured object, they would need to have the same or higher permission rights as the permissions on the object. Users can also have access to a secured object if they are a part of a group that has access through its assigned permission level.
When permissions are migrated, an algorithm is used to find the best matching permission level (role) on the target, as compared to the source. For example, if a permissions level exists on a source SharePoint environment, and permissions are migrated to the target, Metalogix Content Matrix will look on the target for the closest matching role. Whatever the closest permission level is (by included permissions) will be the permission level that is used on the target. In the case that permission levels (roles) are also migrated, these migrated permission levels will be used, because these created roles will have the closest matching permissions when compared to the existing permissions on the target. If permission levels are not copied, the closest matching permission level will be used instead.
NOTE : Whenever Metalogix Content Matrix copies content, it will migrate the user groups that are associated with the migrating content, provided they have not already been copied to the target server.