Chat now with support
Chat with Support

Metalogix Content Matrix 8.8 - SharePoint Edition User Guide

Introduction Entering the License Key Content Matrix Console End User Interface Enabling Advanced Mode Connecting to SharePoint Preparing for a Migration How Content Matrix Handles Various SharePoint Components Initiating a Migration Configuring Copying Options Saving or Running a Migration Action Copying SharePoint Objects as a Separate Action Self-Service Migration Incremental Migration Log Files Using PowerShell with Content Matrix
Configuring PowerShell for Use with Content Matrix
Registering Metalogix Command DLL Files Adding PowerShell Snap-Ins for the Application Framework Content Matrix PowerShell Commandlet List
Metalogix.System.Commands Metalogix.SharePoint.Commands Metalogix.Jobs.Reporting.Commands Metalogix.SharePoint.Migration.Commands
Modifying Content Matrix Configuration and Settings Configuring Content Matrix for Distributed and Self-Service Migration Frequently Asked Questions
DB_Owner Permission Migrating with the Fabulous 40 Templates Item Count Discrepancies Keyboard Shortcuts License Key Troubleshooting Determining the Status of a Migration Running in the Background MySite and User Profile Migration Issues Optimal Setup for Best Performance Using Proxies, Load Balancing or Alternate Access Mappings Troubleshooting the Extensions Web Service Installing the Extensions Web Service on Specific Systems Extensions Web Service Installation Files Using Older Versions of the Extensions Web Service Preserving IDs when Migrating a Custom List as a Folder Migrating JavaScript Migrating Site Variations Migrating with SharePoint 2010/2013/2016 Document IDs Changing a Job Configuration for Multiple Files SharePoint 2003 Version Migration Limitations SharePoint 2013 and 2016 Site Collection Creation Issue Job List Database fails to Load After Upgrade Customized Wiki Page Web Part Zones Not Being Migrated Preserving SharePoint List Item IDs with a CSOM Connection Type Retrying Failed Document Copies to O365 CSOM Connections Migrating Content When the Source Custom List Template is Missing Are SharePoint Online Migrations Throttled? What to Expect when Migrating with StoragePoint on the Target Migration Error Message 'There was an Error Reading from the Pipe: The Pipe has been Ended (109, 0xd6)' How do I Remove Items from My Azure Blob Storage Account? Azure Batches Getting Stuck Supported Nintex Actions for SPO Migration "Insufficient Credentials" Message Connecting to Modern Team Site Using Web Browser Authentication Error Making a Browser-Based Connection with PowerShell Console Open
About Us

Importing and Exporting Migration Jobs

From the Jobs List, you can export a job to an xml file.  This functionality allows you to:

·Copy a job from one instance of Metalogix Content Matrix to another (as long they are for the same Edition).

·Manually modify a job, then re-import it.

To export a job to an xml file:

1.In the Job List, select the job you want to export.

2.Right-click, and choose Export selected job to xml.

The xml file will automatically open in whatever program is set as the default application for xml files, and it can be saved to any desired location.

To import an xml file to the Job List:

1.Make sure the file you want to import uses a different ID value than any existing Jobs (this should only be an issue if the XML file was previously exported from the same Metalogix Content Matrix Console).

NOTE: If the xml file that is being imported contains the same ID value as an already existing Job, then the import will fail.

2.From the Job List menu, choose File > Import Jobs From Xml.

3.Select the xml file to import.

If the import is successful, the job will be listed in the Job List section.  If unsuccessful, an error message will be given.

Scheduling a Migration Job

Metalogix Content Matrix can run a migration action through the Metalogix Content Matrix Console or as a Windows Scheduled Task.

How the Schedule Task Feature Works

Metalogix Content Matrix Console can run any migration as a scheduled task on the system that the client application is installed on. This can be any migration action that exists in the Job List section, whether it's a migration job that was saved or a job that was previously run. Once a job exists in the Job List section users can run the Schedule Task option.

The Schedule Task option saves configurations for the selected job(s) as a PowerShell script. After the script has been saved, you must create a Windows Scheduled task:

·through the Metalogix Content Matrix Console UI

OR

·directly in the Windows Task Scheduler

Once these jobs have been created as scheduled tasks they can no longer be viewed (as scheduled tasks) in Metalogix Content Matrix.  If you want to make any other modifications or remove the task you can do so  directly in the Windows Task Scheduler. If a task has been scheduled, the system will be able to run the task at the appointed time(s), regardless of whether Metalogix Content Matrix client application is open.

After the scheduled task has run, a new entry will be added into Metalogix Content Matrix's Job List section.

Before Configuring Migration Actions to Run as Scheduled Tasks

·Any system that runs the PowerShell script for the scheduled task must have all of the Metalogix PowerShell snap-ins and plug-ins installed and configured for use on the PowerShell console that will run the scripts. If these are not configured the scripts will fail to run, and the migration will fail.

·It is recommended that the connections to the source and target environments have the Remember my password check-box selected. This is to ensure that the PowerShell scripts will be able to establish a connection to both the source and target environments when they are being run. If a password is required and this check-box is not set, the migration will fail. However, users can manually enter this value into the PowerShell script itself if the option was not checked when the script was first generated.

Note: The migration job used to create a scheduled task can either be a job that has previously been run or it can be a job that was saved.

Related Documents