You can view, create, and edit Transformers which, as the name implies, "transform" content during migration.
There are several built-in, non-editable transformers that Metalogix Content Matrix uses to process data during the migration. Advanced users can also create custom transformers using PowerShell.
The Transformations tab consists of two main sections: Available Definitions and Applied Transformers For <Object>. The Available Definitions section will list all of the transformation definitions that are available for the current migration action, in alphabetical order. For example, the Site definition is available when migrating at the site level or higher. However, if migrating as a document library or migrating documents, this definition will not be listed.
When one of the Available Definitions items is selected, any transformations that exist/have been configured within the migrating content will appear. Some of the actions that may be grayed out. These grayed out items are mandatory transformations that are run during the course of a normal migration, and these actions cannot be edited or removed. However, they can be reordered by using the up and down arrows to the right-hand side of the window if you want a transformation action to occur before a mandatory action. Actions that appear and are not grayed are user added transformations, and can be moved, edited and deleted at the users discretion.
In some cases, you could add another instance of an existing transformer, and then have it run in two different locations within the migration process. One could be run in the middle, and it could be run again just before the end.
When you select the Add Transformer > Invoke PowerShell script option for an Available Definition, you can use custom PowerShell scripts to create your own transformations beyond the built-in capabilities of the Metalogix Content Matrix.
NOTE: For prerequisites to using PowerShell with Metalogix Content Matrix, see Configuring PowerShell for Use with Metalogix Content Matrix.
Specify when you want the script to run by selecting one of the following options:
Begin Transformation The transformation script will run before the migration of the affected objects, allowing you to read and make changes to objects on the source before objects themselves migrate.
Transform The transformation script will run while the migration of the affected object(s) is in progress. For example, the user mapping between source and target would be run using the Transform option.
End Transformation The transformation script will run after the migration of affected object(s), allowing you to read and make changes to objects on the target.
EXAMPLE: The following Transformer consists of two scripts for disabling and re-enabling the Required setting for a column list.
·The first script entered into the Begin Transformation tab sets the setting of any columns that are Required to false before copying begins.
·The second script, entered into the End Transformations tab, sets the setting back to true after item migration has completed.
When you finish configuring a migration action, you can run it immediately or save a copy of the settings to a job file, which displays in the Job List section. You can then:
· run a migration directly from the Jobs List section
·schedule the job to run at a specified time, either as a Windows Scheduled Task or straight from PowerShell.
·If the Console is configured as the Controller (Host) machine for Distributed Migration, submit a Distributed Migration job.
You can also save the job configuration as a template so that you can preserve and reuse settings for future migration jobs.
When the migration starts, a status dialog box will appear. The migration logs can be viewed (in progress or after the migration is finished) by clicking [Details>>]. The Status section of the status box will list a live count for the number of successes, warnings, failures, etc. for the migration. The Progress section of this dialog will list any completions and the type of completion (Sites, lists, items, users, groups, etc.). A Migration Completed message will appear when finished. Click Close to exit the status dialog.
You can create job configuration templates for a set of selected settings which can be saved and reused, including any options that are not normally preserved using the Preserve Configuration Options option (in the ribbon Settings menu).
These templates can also be moved to another machine and used with a separate install of Metalogix Content Matrix Console (provided that it is the same Edition of Metalogix Content Matrix, and the same version number or greater).
To save a job configuration template:
1.After initiating a migration, complete the Configure (Object) Copying Options with the settings that you want to include in the template.
2.Click [Save Job Configuration].
Here you can set the display name for the job template. This is not the actual file name, but it is the name that Metalogix Content Matrix will use to list the template.
NOTE: In most cases, when a job template is saved by Metalogix Content Matrix it will be saved to the following location:
<Drive>:\Users\<User>\AppData\Roaming\Metalogix\Metalogix Content Matrix Console - <Product> Edition
However, it is highly recommended that you do not interact with this system location. If you are trying to save a job template so it can be exported to another system the template can be exported from the Manage Job Configurations dialog.
3.Enter the desired display name value and click [OK] to continue.
Once the save is complete, you will be returned to the Configure <Object> Copying Options dialog where the migration can either be Run or Saved.
The saved job templates will now be visible in the Manage Job Configurations dialog.
NOTE: If you are looking to save a job template and move it to another system for use, this should be done using the Export option in the Manage Job Configurations window. Additionally, if you are trying to Import a job template from another system, this must also be done from either the Manage Job Configurations dialog or it can be imported when applying a template.