Chat now with support
Chat with Support

Metalogix Content Matrix 9.3 - SharePoint Edition User Guide

Introduction Entering the License Key Content Matrix Console End User Interface Enabling Advanced Mode Connecting and Migrating Account Requirements Connecting to SharePoint Preparing for a Migration How Content Matrix Handles Various SharePoint Components
How Team Sites are Migrated to Modern Team Sites How Publishing Sites are Migrated to Communication Sites How MySites are Migrated How Records Centers are Migrated to SharePoint Online Using the Import Pipeline How Master Pages are Migrated How List Template Galleries Are Migrated How Content Types are Migrated Document Version and Checked Out File Limitations How Ghosted and Un-Ghosted Pages are Migrated How Document Sets are Migrated How Navigation is Migrated How "Share With" Metadata is Migrated to SharePoint Online Using the Import Pipeline How Web Parts are Migrated How Site Themes are Preserved How Site Features Are Migrated How Managed Metadata, Terms, and Term Stores are Migrated How Users and Permissions are Migrated How BCS/BDC Data is Migrated How OneNote Notebooks are Migrated How Customized Form Pages are Migrated How InfoPath Forms are Migrated How SharePoint Workflows are Migrated How Nintex Workflows and Forms are Migrated How Link Correction Works
Initiating a Migration Configuring Copying Options Saving or Running a Migration Job Copying SharePoint Objects as a Separate Action Converting Classic Pages to Modern Pages After a Migration Incremental Migration Using PowerShell with Content Matrix
Configuring PowerShell for Use with Content Matrix Creating and Running a PowerShell Script 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 Migration Frequently Asked Questions
DB_Owner Permission 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 Migrating SharePoint On Premises 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 Migrating JavaScript Migrating Site Variations Migrating with SharePoint Document IDs Changing a Job Configuration for Multiple Files SharePoint 2013 and Later 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 How Do I Identify and Remove Containers and Queues from My Azure Private Storage Account? Import Pipeline Batches Getting Stuck "Error, the batch will be resubmitted" Message Displays When Using the Import Pipeline Item Count at Target is Increased When Migrating Using the Import Pipeline Custom Lists with Versioning Enabled Not Being Migrated When Using the Import Pipeline Supported Nintex Actions for SPO Migration Support for GCC High Tenants
About Us

Metalogix.SharePoint.Commands

Metalogix Content Matrix can generate PowerShell script for you, for any migration action that is available through it. The below cmdlets are used in the generated PowerShell script, but can also be used to write your own script, should you desire to do so. For more information on each cmdlet, simply type get-help [cmdlet]. For example, if you want more information on Copy-MLSharePointList cmdlet you would enter get-help Copy-MLSharePointList, followed by the Enter (return) key.

Below is a list of the available cmdlets (and their parameters), broken up into the available commands for each snap-in.

Add-MLSharePointSiteCollection

·WebApplicationName - Name of the Web Application to Create the Site Collection in. Web Application must exist in the specified Target. (Mandatory)

·WebTemplateName - Web (Site) Template to use for the Site Collection. Web (Site) Template must exist. The value must be in the form name#configuration. E.g., STS#1 for Blank Site (Mandatory)

·Language - Language to use for the Site Collection. Can be Language Code (LCID) or Language Name. Language must exist in the specified Target. (Mandatory)

·ExperienceVersion - The experience version to use when creating the site. This setting is only used for SharePoint 2013. Use 15 for the 2013 UI and 14 for the 2010 UI.

·Title - The Title for the Site Collection. (Mandatory)

·Description - Description for the Site Collection.

·Path - Managed Path for the Site Collection. Include forward-slash characters where required. E.g., "/sites/" or "/sites/". (Mandatory)

·URL - Server Relative portion of URL solely used to identify the Site Collection itself. E.g., "TestSiteCollection" (Mandatory)

·HostHeaderSiteCollectionURL - The URL of the host-named Site Collection in the format http://servername.

·OwnerLogin - Domain and username to be used as the Primary Administrator for the Site Collection. E.g., "sampledomain\sample.user" (Mandatory)

·SecondaryOwnerLogin - Domain and username to be used as the Secondary Administrator for the Site Collection. E.g., "sampledomain\another.user"

·ContentDatabaseName - Content Database Name to use. Not specifying this value will use the default content database (auto detect).

·SelfServiceCreateMode - Allow users without Farm Administrator privileges to add the Site Collection.

·SetSiteQuota - Set Quota for the Site Collection.

·QuotaMaximum - Limit site storage to maximum size (Mb). SetSiteQuota must be set to true and SelfServiceCreateMode should be false. Mutually exclusive with QuotaID.

·QuotaWarning - Send a warning email when the site storage reaches this size (Mb). SetSiteQuota must be set to true and SelfServiceCreateMode should be false. Mutually exclusive with QuotaID.

·QuotaID - Use Quota Template. Can be the integer ID or the string name of the Quota. SetSiteQuota must be set to true and SelfServiceCreateMode should be false.

·Transformers - The collection of data transformers which the action needs to run. Note that if the passed-in value for this parameter does not include transformers which are considered mandatory, they will be added automatically.

·Quiet - If set, the operation will not report progress to the PowerShell console.

·JobFile - The name of a job file to use for logging. If the file does not exist it will be created.

·Source - The source node for the actions.

·Target - The target node for the actions.

·JobDatabase - The connection string of a jobs database to use for logging. If the connection string is invalid, an exception is thrown. If both 'JobFile' and 'JobDatabase' parameters are specified, then the 'JobDatabase' parameter will take precedence and the job will only be written to the job database.

Add-Permissions

·Name - The name of the user or group you wish to assign a permission level to. (Mandatory)

·PermissionLevel - The name of the permission level you want to grant the specified user or group. (Mandatory)

·Recurse - A flag that indicates the given permissions level should be granted to the given user for each item below the target which has unique permissions.

·Transformers - The collection of data transformers which the action needs to run. Note that if the passed-in value for this parameter does not include transformers which are considered mandatory, they will be added automatically.

·Quiet - If set, the operation will not report progress to the PowerShell console.

·JobFile - The name of a job file to use for logging. If the file does not exist it will be created.

·Source - The source node for the actions.

·Target - The target node for the actions.

·JobDatabase - The connection string of a jobs database to use for logging. If the connection string is invalid, an exception is thrown. If both 'JobFile' and 'JobDatabase' parameters are specified, then the 'JobDatabase' parameter will take precedence and the job will only be written to the job database.

Add-SharePointFolder

·Name - The name of the folder to be created. (Mandatory)

·Transformers - The collection of data transformers which the action needs to run. Note that if the passed-in value for this parameter does not include transformers which are considered mandatory, they will be added automatically.

·Quiet - If set, the operation will not report progress to the PowerShell console.

·JobFile - The name of a job file to use for logging. If the file does not exist it will be created.

·Source - The source node for the actions.

·Target - The target node for the actions.

·JobDatabase - The connection string of a jobs database to use for logging. If the connection string is invalid, an exception is thrown. If both 'JobFile' and 'JobDatabase' parameters are specified, then the 'JobDatabase' parameter will take precedence and the job will only be written to the job database.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating