Self-Service Migration, an additionally-licensed component of Metalogix Content Matrix, allows end users to perform migrations of site content, with a simplified set of options, directly from their workstations.
Once Metalogix Content Matrix has been configured for Self-Service Migration, each Self-Service workstation in the configuration employs a simplified version of the Metalogix Content Matrix Console.
From the Metalogix Content Matrix Console, Self-Service users can:
·Connect to SharePoint sites.
Metalogix Content Matrix auto-detects the appropriate connection type to use. Note that, because Self-Service migration jobs are run remotely (on Distributed Migration agent machines, or the Controller machine if Distributed Migration is not also configured or if Distributed Migration agents are not available), the local object-model (OM) connection cannot be used.
REMINDER: A Read-Only connection can be used as a source connection only. It can be used to help users keep their source and target connection separate (and it can help ensure that users do not accidentally migrate any data to a source connection).
·Initiate a site-level migration using the Paste All Site Content option.
·Select a pre-configured job template to use for running the migration.
·View a Summary of the configured migration job.
·Run the migration job via the Controller or Distributed Migration agent.
IMPORTANT: If Self-Service Migration was configured prior to version 8.8, the first time Self-Service users run a migration job, they will be prompted to agree to the terms of a third-party license agreement before being able to continue. (If Self-Service Migration was configured in version 8.8 or later, the third-party license agreement is accepted as part of Self-Service Migration Configuration.)
NOTE: The Controller Console must remain open during job execution.
Currently, users must choose File >Refresh in order to update the Status in the Jobs list.
Before a Self-Service Migration can be performed, a migration job must be configured from the Metalogix Content Matrix Console on the Controller machineincluding any user mappings that are appropriate for the Self-Service users' source and target environmentsthen saved as a job template. Only job templates that have been configured for a Paste All Site Content migration (currently the only migration type available for Self-Service) and saved on the Controller machine will be available for selection by Self-Service users.
NOTE: If a job configuration template is created while a workstation Console is open, the Self-Service user will have to restart the Console in order to see the template.
If you want to include Managed Metadata mappings in the job template, keep in mind that the Managed Metadata will be successfully migrated only if the workstation source and target farm(s)/tenant(s) are the same as those in the mappings. Currently, you cannot use Global Mapping for Managed Metadata; rather, they must be done as part of the job template (via the Migration Option > Site Element Options > Mapped Managed Metadata option).
You can also import an entire migration job (which includes the source and target sites) to an xml file, which a Self-Service user can simply import and run from the workstation.
After an initial migration is run, an incremental copy (also known as a delta migration) will copy any new and updated data from the source to the target.
Incremental copying is not supported if using Native Web Service (NWS) connection on the target. This is in part due to the inability to correctly preserve the item IDs. If trying an incremental copy, with the NWS connection on the target, there is a possibility that some of the data on the target side will be corrupted.
There are three different methods to run an incremental copy from Metalogix Content Matrix:
·Incremental Copy Mode - Update Existing Objects option on the Migration Mode tab
The incremental copying option enables migrations that can preserve and update objects on the target of the migration. This mode is used when you just want to make sure nothing on the target gets overwritten. Only new objects that do not yet exist on the target are copied.
EXCEPTION: For lists and libraries with versioning enabled, any new versions that have been created since the initial migration will be copied to the target.
When this option is selected there are two options that are toggled. The first is the Preserve Item IDs option is enabled. The second is that the workflow copy options are turned off. This is because Incremental copies cannot be run on workflows.
·The Custom Copy option on the Migration Mode tab
The custom copy option allows you to run incremental copies for selected content. This option allows you to configure a mix of the Overwrite and the Incremental modes, meaning that incremental copies can be performed on select content in a migration, while allowing other content to be overwritten.
IMPORTANT: Preserving IDs on items/folders in Lists
When running an incremental copy the Preserve IDs on items/folders in Lists option must have been enabled in the original copy. This is so Metalogix Content Matrix can reference the item ID when looking to see if the items already exists on the target side. If this option was not selected, the incremental copy for SharePoint lists can return some strange results. Generally, in cases where this option was not selected, an incremental copy will create some duplicate content on the target for items it thinks are not in the list, even though they may be (but use a different item ID). The other possible consequence is that some data may be missing, because Metalogix Content Matrix may think that some data exists on the target, even though it may not (but the IDs may be in use). For more information on incremental copying and preserving IDs for SharePoint list items please see Preserving SharePoint List IDs with a CSOM Connection Type .
The preservation of Document ID/s is not an issue for incremental copying of SharePoint documents. Incremental copying for documents is referenced by the folder path/filename of the document instead of the item ID. Metalogix Content Matrix will look for the URL path of the document, and if found, will then compare the modified date between the original target document and the source document to see if any modifications have been made to the file. If any modifications are found, as compared to the target, these will be migrated to the target. If no file was found when looking back to the source/target URL path, then that document/folder will be added.
To perform an incremental copy using Migration mode:
2.On the Migration Mode tab, select Incremental copy.
When this option is selected:
§the Preserve Item IDs option is enabled, and
§the Workflow Copy Options is disabled. (Incremental copies cannot be run on workflows.)
REMINDER: When running an incremental copy the Preserve IDs on items/folders in Lists option must be enabled so that Metalogix Content Matrix can determine if the item already exists or if it has been updated. (When copying documents the folder path and document name are used instead.)
To perform an incremental migration job from an existing job:
1.In the Jobs List, select the job(s) for which you want to perform an incremental migration. (Use [Ctr] click to select multiple jobs.)
2.Right-click and choose Create incremental job.
NOTE: The new job will use the same name as the initial job with " Incrementally" appended to the end of the name