Metalogix Content Matrix - File Share Edition has the ability to migrate documents directly into Metalogix StoragePoint, while leaving the endpoint reference in the appropriate SharePoint location. These options are available through the StoragePoint options tab.
These options are only available when Advanced Mode is enabled.
When you navigate to the StoragePoint Options tab, a check will be automatically run on the target SharePoint environment to see if Metalogix StoragePoint is installed. If StoragePoint is installed, all of the options within the options tab will be enabled. If StoragePoint is not installed on the target SharePoint environment, all of the options will be disabled. The StoragePoint detection status will be displayed next to the StoragePoint found on target: line at the top of the tab window, and the value will either be Yes or No.
NOTE: The StoragePoint options will only affect documents and attachments that are being migrated into SharePoint. Other content such as Pages (for publishing sites), will not be affected.
Prerequisites for Migrating StoragePoint Content
The option to use Metalogix Content Matrix to migrate StoragePoint data is available only as the following conditions are met:
·Metalogix Content Matrix detects that Metalogix StoragePoint version 5.1 or higher is installed on the target.
·The target farm does not use a CSOM Connection Type.
To configure StoragePoint options:
1.If an endpoint profile is configured and you want any documents and attachments to be migrated to SharePoint, check the Add documents directly to StoragePoint if an endpoint is configured box.
NOTE: When you check this box, documents and attachments will be added directly through the StoragePoint API and the end reference will be added in SharePoint. This helps improve migration efficiency and can potentially help performance speeds when migrating a large number of documents and/or attachments.
2.If you want the source File Share location to be converted into a Storage Endpoint location on the target instead of actually copying the files, check the Link Files to SharePoint by configuring the source directory as a StoragePoint endpoint.
NOTE: When you check this box, the appropriate endpoint location link will be added to the SharePoint environment. This option's standard use case is for target SharePoint environments that have StoragePoint installed, but no endpoint has been configured.
If both StoragePoint options are selected at the same time, the Link Files to SharePoint by configuring the source directory as a StoragePoint endpoint option will take priority, and overwrite the first option. This means that the source File Share will be configured as an endpoint for StoragePoint, even if another endpoint is already configured. If there is a conflict between configured endpoints, the documents that experience the conflict will not be migrated.
If Advanced Mode and Custom Transformers options have been enabled, 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.