·Source - The source node for the actions. (Mandatory, should be specified as Get-MLSharePointSite)

·Target - The target node for the actions. (Mandatory, should be specified as Get-MLSharePointServer)

·JobConfigFile - The filepath of the job configuration XML file. (Mandatory)

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

Note: If any additional parameters are provided, or if the job configuration XML file is improperly formatted, an error may appear and the migration action may fail.

Source - The source node for the actions. (Mandatory, should be specified as Get-MLSharePointSite)

Target - The target node for the actions. (Mandatory, should be specified as Get-MLSharePointSite)

JobConfigFile - The filepath of the job configuration XML file. (Mandatory)

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

Note: If any additional parameters are provided, or if the job configuration XML file is improperly formatted, an error may appear and the migration action may fail.

·SourceUsers - A collection of users to be copied to the target site.

·LogSkippedItems - Indicates that actions which have been skipped should not be logged at all.

·CheckResults - Indicates whether the user would like to use the Metalogix Comparison tool to compare the source and target. If chosen, differences will be outputted as warnings to the PowerShell console. All results for an operation can be seen by enabling verbose display.

·OverrideCheckouts - Indicates that the checkout status of a pre-existing target file will be overridden.

·CorrectingLinks - Indicates whether the user would like to employ automatic link correction to metadata fields within their copy.

·LinkCorrectTextFields - Indicates whether the user would like to employ automatic HTML link correction in text fields of items/documents.

·LinkCorrectionScope - Specifies the scope at which links are corrected. The current options are 'SiteCollection' and 'MigrationOnly' level scope.

·UseComprehensiveLinkCorrection - Indicates whether link correction mapping generation is performed before the migration or as the migration occurs.

·ComparisonLevel - Indicates whether a strict or moderate comparison is desired. Note that this has no effect if CheckResults is false.

·MapGroupsByName - Indicates if mapping of SharePoint groups should be done by name, rather than membership.

·OverwriteGroups - Indicates if groups with matching names should be overwritten. Note that this only applies when mapping is being done by name.

·AllowDBUserWriting - Sets user writing operations to use a direct database write when the user is no longer available in Active Directory. Requires that your environment settings be configured to allow DB writing.

·ForceRefresh - Forces a refresh of the source and target nodes prior to copying to ensure that all cached data is up to date.

·MapAudiences - Enabled the mapping of audiences during a copy.

·VerboseLog - Enables verbose logging.

·MapMissingUsersToLoginName - Map all missing users to this Login Name.

·PersistMappings - When set, any dynamically created link correction or GUID mappings will be persisted to the global mappings store. If the global mappings already contain an entry for a particular source GUID, it will be overwritten with the value dynamically generated by the action.

·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.

·ExistingWebPartsAction - Indicates what action the copy should take on web parts that already exist on the target.

·MapGroupsByName - Indicates if mapping of SharePoint groups should be done by name, rather than membership.

·OverwriteGroups - Indicates if groups with matching names should be overwritten. Note that this only applies when mapping is being done by name.

·ForceRefresh - Forces a refresh of the source and target nodes prior to copying to ensure that all cached data is up to date.

·CopyClosedWebParts - Indicates whether closed web parts from the source are copied to the target or not.

·CopyContentZoneContent - Indicates whether content zone content should be updated on the target as part of the copy.

·CopyWebPartsRecursive - Indicates whether webparts should be copied recursively for each sub-site or not.

·MapAudiences - Enabled the mapping of audiences during a copy.

·MapMissingUsersToLoginName - Map all missing users to this Login Name.

·UseComprehensiveLinkCorrection - Indicates whether link correction mapping generation is performed before the migration or as the migration occurs.

·TaskCollection - Defines a collection of transformation tasks, such as renaming, to be applied to the data as it is copied.

·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.