Viewing StoragePoint Details
Metalogix Content Matrix can display the Metalogix StoragePoint details for any document items that have been offloaded to StoragePoint.
To view StoragePoint details:
1.In Explorer View, navigate to a SharePoint Document Library that contains items that have been offloaded to StoragePoint.
2.Switch to the Items View tab.
3.Select an item, right-click and choose StoragePoint Details.
NOTE: The StoragePoint Details option will only be available in the menu if the selected items have been offloaded into StoragePoint. If the selected item has not been offloaded to StoragePoint the StoragePoint Details options will not be available. Only one item can be selected at a time.
The Storage Point Details dialog provides the below information:
§Address - The web address for the specified item within SharePoint.
§Endpoint Relative Folder - The folder that has been configured as endpoint for the offloaded item (i.e. the location of the item in the offloaded storage space).
§Filename - The StoragePoint file name reference that is left behind in SharePoint after the item has been offloaded.
4.When finished, click [Close].
How Content Matrix Handles Various SharePoint Components
Before configuring a migration, it is important to understand how Metalogix Content Matrix migrates various SharePoint components so that you can plan appropriately. These include:
SharePoint 2003 Portal Listings
How Master Pages are Migrated
The Master Pages Gallery is basically a Document Library at the root of a site.
Metalogix Content Matrix can work with Master Pages at two levels:
·At the Site Collection level, where it can copy master pages and page layouts.
·At the Site level, where it can preserve the master page association.
When a SharePoint site is migrated, Metalogix Content Matrix will run a check to see if a master page with the same name as the source site's master page exists. There are then two main scenarios:
·Migrating from an older version of SharePoint to a newer version of SharePoint - Because master pages are quite different between different versions of SharePoint, when master pages are migrated from an older version of SharePoint to a newer version, a suffix will be appended to the end of the master page name based on the source UI version. For example, if you are migrating from MOSS 2007 to a later version, the master pages will have "_2007" appended to the end of the master page name. If migrating from SharePoint 2010 to a later version, the suffix would be "_2010" instead.
When a SharePoint site is migrated, Metalogix Content Matrix will look for the source master page by name. If the master page name is found, Metalogix Content Matrix will then do another check to ensure that the correct UI version is being used on the target site collection. If this UI version also matches, then the master page will be used for the migrating site. If the UI version is not the same, then the current default master page will be used instead.
If the master page cannot be found by name, then Metalogix Content Matrix will check to see if there is another master page that has the same name plus the appended UI version suffix that would represent the source. For example, if migrating from SharePoint 2013 to SharePoint 2016 and the master page is named "AccountMaster3," then Metalogix Content Matrix will look for a master page with the same "AccountMaster3" name. If that fails it will then look for a master page with the same name plus "_2013" appended to the end, like "AccountMaster3_2013." If this is found, then the same UI version check will be run that is used for the exact same master page name, and the same results will be given.
If no master page with the same name is found, either the direct same name, or the name with the UI version appended to the end, then the current default master page will be used instead.
NOTE: If the master page belongs to a UI version that is not supported by the target SharePoint instance, the master page will be skipped.
·Migrating between similar versions of SharePoint - For migrations that are run between the same basic UI version of SharePoint, such as SharePoint 2013 to SharePoint 2013 and SharePoint 2016 to SharePoint 2016, Metalogix Content Matrix will look for a master page with exactly the same name as the master page on the source. If one is found, then Metalogix Content Matrix will use that master page. If no master page with the same name is found, then the current default master page will be used instead.
How List Template Galleries Are Migrated
Metalogix Content Matrix lets you copy the List Template Gallery from a source SharePoint Site Collection to a target SharePoint Site Collection.
|
|
In order for the List Template gallery to be migrated, you must have a Object Model (OM) connection (through either a Local or Remote Extensions Web Service connection) on both the source and target environments. |
|---|
The List Template Gallery can be migrated as part of a Site Collection copy (when copy a Site Collection and pasting as a Site Collection), or it can be copied as a separate action. Any list templates that are copied from the source will overwrite any list templates on the target that have the same name. If the file names are different, then the list templates will be added to the existing List Template Gallery.
For example, if there are two templates on the target named "Template A" and "Template B", and these are migrated to the target where there are also two templates, which are named "Template B" and "Template C" then only "Template B" will be over written. In this case "Template A" will be copied to the target, and since there is no existing file with the same name it will be added without overwriting any other files. Since there was no file with the "Template C" name that was migrated to the target, the "Template C" file will also exist (as is) on the target. However, since both the source and the target have a file with the "Template B" name, the "Template B" file on the target will be overwritten by the one from the source. The end result is that three files will now exist on the target: Template A, Template B (which is a copy of the source version of the file), and Template C.