Chat now with support
Chat with Support

Metalogix Content Matrix 9.2 - SharePoint Edition User Guide

Introduction Entering the License Key Metalogix Content Matrix Console End User Interface Enabling Advanced Mode Connecting to SharePoint Migrating to SharePoint Online Using the Import Pipeline Preparing for a Migration How Content Matrix Handles Various SharePoint Components
How Team Sites are Migrated to SharePoint Online and SharePoint 2019 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 Records Centers are Migrated to SharePoint Online Using the Import Pipeline How Document Sets are Migrated How Navigation is Migrated How MySites are Migrated How Managed Metadata, Terms, and Term Stores are 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 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 Incremental Migration 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 Migration Frequently Asked Questions About Us

Workflow Options

Before migrating workflows, it is strongly recommended that you review the How SharePoint Workflows are Migrated and How Nintex Workflows and Forms are Migrated sections for requirements and limitations.

NOTES:

·If you are performing a list-level migration:

§Dependent workflow task lists should be available on the target.

§If the workflow has any dependencies on other list or site items, those dependencies should be migrated to the target first.

 

·When migrating SPD 2013 platform workflows, the SuppressEvents property must be set to False in order for workflows to be published after migration.

· When migrating any workflow, it is recommended that site and site collection features also be migrated.

Simplified UI icon

Unless otherwise noted, if you are using Simplified mode and an option is not available for selection, the default value that displays in Advanced mode will automatically be applied.  If you want to change the value of the option, click [Advanced Mode] and switch to the Advanced mode interface.

To configure workflow options:

1.Select Copy Workflow (if you are using Simplified mode) or the Workflow Options tab (if you are using Advanced mode).

Note that available options depend on the level at which you initiated the migration and, in some cases, the version of SharePoint.

Workflow options

The remaining options, described below, can only be changed if you are using Advanced mode:

2.If you are migrating from a SharePoint 2010 or later site collection and want to migrate SPD Globally Reusable Workflows, make sure the Preserve globally reusable workflow templates box.

NOTE:  This option only applies to globally reusable workflow templates.  Globally reusable workflow associations are treated as out-of-the-box workflow associations.

3.If you are migrating from a SharePoint 2010 or later site collection or site, select the appropriate option(s).  Use the information in the following table for guidance.

If you want to migrate …

Then ….

site and site-collection level workflow data

check the Web scope – Preserve migrating site level workflow data box.

site and site-collection level workflow associations

check the applicable Web scope box(es):

·For SharePoint out of the box workflows: Preserve out of the box web workflow associations

·For SPD and/or Nintex workflow associations: Preserve workflow associations for SharePoint Designer and Nintex Workflow.

NOTE:  It is possible for SPD workflow associations (at the Site level) to be migrated if a CSOM or Tenant connection type is used for the target connection. When the CSOM connection type is used for the target connection, this option will be renamed to Preserve workflow associations for SharePoint Designer Workflow, and workflow instances will not be migrated.  

4.If you want to migrate list-level workflow associations, check the applicable List scope box(es):

§For SharePoint out of the box workflows: Preserve out of the box list workflow associations.

§For SPD and/or Nintex workflows:  Preserve workflow associations for SharePoint Designer and Nintex Workflow.

5.If you initiated the migration at the site collection or site and want to migrate both site and list workflow content types, check the applicable Content type scope box(es):

§For SharePoint out of the box workflows: Preserve out of the box content type workflow associations..

§For SPD and/or Nintex workflows: Preserve workflow associations for SharePoint Designer and Nintex Workflow.

If database writing is enabled and you want to preserve workflow instance data for workflows that are not currently active or "In Progress," (including any complete, rejected, or terminated workflows), the Association content preservation options are enabled.

IMPORTANT: For n on-premises target, these options are only available for selection if Metalogix Content Matrix is able to write data directly to the Database. However, on-premises database writing methods are not supported by Microsoft, and if used, will impact your Microsoft warranty. Please contact Quest Support for guidance and see the procedure for Association Content Preservation When Writing Directly to a Database .

Association Content Preservation When Connected to a Database

If database writing is enabled and you want to preserve workflow instance data for workflows that are not currently active or "In Progress," (including any complete, rejected, or terminated workflows, the Association content preservation options are enabled.

IMPORTANT: These options are only available for selection for an on-premises environment, and Metalogix Content Matrix is able to write data directly to the Database. However, database writing methods are not supported by Microsoft, and if used, will impact your Microsoft warranty. Please contact Quest Support for guidance

To configure Association Content Preservation options:

1.Check the Preserve current workflow instance data box.

When this option is selected a warning message about the Database write method will be displayed.  Click [OK] to continue.

2.Use the information in the following table to determine the appropriate option to select.

If you want to ...

Select ...

preserve instance data that is still active within the workflows

Preserve historical state (running workflows cannot be continued).

NOTE:  Any workflow instances in the "Running or "In Progress" state cannot be continued after migration.  Rather, the preservation of "state" is only for historical purposes.

cancel the status of any workflow instance that is currently running

Cancel running workflows during migration.

3.If you want to migrate any previous versions of a workflow instance to the target, check the Include previous version instances box.

NOTE:  Metalogix Content Matrix will first try to connect to an external Nintex Workflow database connection. If one exists, it will then check for any Nintex Workflow database entries corresponding to the list of SharePoint workflow instances that it has migrated. If corresponding entries exist inside the source external Nintex Workflow database connection, then Metalogix Content Matrix will try to write the data directly into the specified target external Nintex Workflow database connection. This option is only available if the database writing option is enabled. For more information on enabling Database writing, please contact Quest Support.

 

IMPORTANT: Nintex workflow histories are currently always migrated from SharePoint 2010 and never migrated from SharePoint 2013 and later, regardless of whether the option Preserve Nintex Workflows instance history is checked.  This is a known issue that will be addressed in a future release.

Modifying the SuppressEvents Property

When migrating SPD 2013 platform workflows, the SuppressEvents property must be set to False in order for workflows to be published after migration.

To modify the SuppressEvents Property:

1.Close the Metalogix Content Matrix Console, if it is not already closed.

2.Navigate to ServerAdapterConfig.xml (located by default in C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\ISAPI\ML) and open it in a text editor.

NOTE:: If the ...\ML folder does not exist, manually create the folder and create a text file inside it named ServerAdapterConfig.xml.

3.In ServerAdapterConfig.xml, copy and paste the following code:

<ServerAdapterConfig>

<SuppressEvents>False</SuppressEvents>

</ServerAdapterConfig>

4.Save and close ServerAdapterConfig.xml and reopen the Metalogix Content Matrix Console.

StoragePoint Options

If this option is selected, then during the migration, any documents and attachments are added directly through the StoragePoint API if an Endpoint Profile is configured, and the end reference will be added in SharePoint. This can potentially improve migration speed when migrating data that contains a large number of documents and/or attachments.

The StoragePoint options will only affect documents and attachments that are being migrated into SharePoint. Other content 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.

·An endpoint is configured.

·SharePoint 2019 is not installed

·The target farm does not use a CSOM Connection Type.

 

IMPORTANT:  When a SharePoint 2013 or 2016 Database connection is used on the source, StoragePoint Options can be selected, but the migration of StoragePoint data will fail.  This is currently a known issue.

 

Advanced Mode Icon These options are only available when Advanced Mode is enabled.

NOTE:  Shallow Copying Externalized Content No Longer Supported

As of the 7.3 release of Metalogix Content Matrix, shallow copying is no longer supported. This is because shallow copy migration actions could cause you to irretrievably lose data on your source environment. As a result, the Shallow Copy Externalized Data option has been removed from the StoragePoint Options tab of the configuration dialog, and only the Add documents directly to StoragePoint if an endpoint is configured and None options remain.

Note that any existing PowerShell scripts that have shallow copying selected will migrate the content normally, without shallow copying.

See also What to Expect when Migrating with StoragePoint.

Storage Point Options

To configure StoragePoint options:

Select the Add documents directly to StoragePoint if an endpoint is configured radio button.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating