Chat now with support
Chat with Support

Metalogix Content Matrix 8.9 - SharePoint Edition User Guide

Introduction Entering the License Key Content Matrix Console End User Interface Enabling Advanced Mode Connecting to SharePoint Migrating to O365 Using the Azure Pipeline/SPO Containers 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 Document IDs Changing a Job Configuration for Multiple Files SharePoint 2003 Version Migration Limitations 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 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 "Error, the batch will be resubmitted" Message Displays When Using Azure Item Count at Target is Increased When Migrating Using the Azure Pipeline Custom Lists with Versioning Enabled Not Being Migrated When Using the Azure Pipeline 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

Grouping Filter Expressions

You can group two or more filter expressions that you want Metalogix Content Matrix to process as a unit. Only  filters that are adjacent to each other can be grouped. For example, if you have six filters (numbered 1 to 6), you can group, numbers 1 and 2, or 4 and 5, or even 2, 3, 4, and 5. But you would not be able to group 1 and 3, 2 and 5, or 2, 4, and 6. In the case trying to make a grouping of 3,4, and 6, you would be able to group 3 and 4, but you would not be able to add 6 to that group, unless 5 was also included. Multiple groups can also be grouped together into a single group, provided they are adjacent each other.

EXAMPLE:

In the below image there are six filters added at the Lists and Libraries level, and these contain three groupings. There are two sub-groupings that are grouped together into a third, larger one.

CONTEN~1_img114

If you were to read through the filters they would be applied as follows: First a Created filter would be applied for the specified date. Next another filter would be applied to that content on the Modified date for a separate date value. Next the end result of the third, large group would be applied. To determine what the result of this is, you need to take a closer look at the smaller groups.

This first of the smaller groups starts by applying a filter to the Title where the "Project" value is contained within the title. The second line in this first group then applies an Or condition based on a Name value. So the result of this group would be any file that contains "Project" in the Title value, Or and file that's actual Name starts with "Migration."

Then we look at the second sub-group. Here the first filter condition starts with Or, meaning that the whole group is part of an Or statement. This second sub-groups states that the files must have a Status value that equals "Active," as well as the CreatedBy user must not be "Metalogix\JohnS."

All together the results of the filters would be any files that have:

§A Created date greater than, or equal to the specified date.

§A Modified date greater than, or equal to the specified date.

§A Title value that contains the "Project" value in it Or a Name value that starts with "Migration."

§Or a Status value of "Active" And a CreatedBy value that is not "Metalogix\JohnS."

To group filter expressions:

1.In the Filter [Object] dialog, highlight the rows you want to group together.  

2.Either:

§Click [Group Filters].

OR

§Right-click and choose Group Filters.

To remove a filter grouping:

1.In the Filter [Object] dialog, highlight the rows within the grouping you want to remove.

2.Either:

§Click [Remove Grouping].

OR

§Right-click and choose Remove Group.

Applying Site Columns or List Columns Filters

By default, all source columns are included in a migration.  You can use this filter option to select specific columns that you want to exclude.  Excluded columns and their data will not be migrated to the target, but the rest of their data will still be migrated.

NOTE:  The name of this feature depends on the level of the migration.  For site collection or site-level migrations the option is called Apply filter on Site Columns. If the migration is at the list level or below, the option is called Apply filter on List Columns.

To apply Site or List Column filters:

1.Click the […] button to the right of the Apply filter on Site (or List) Columns option to display the Filter [Object] dialog.

CONTEN~1_img115

2.From the Columns to Copy section, highlight the columns from the source that you want to exclude.

NOTE:  By default, columns show the Display Names, but you can, alternatively, choose to show Internal Names (by clicking [Show Internal Names]).

3.Click the right-facing arrow to move columns to the Columns to Exclude section.

NOTE:  If you want to return columns to the Columns to Copy section, click the left-facing arrow.

4.When you have finished selecting columns to exclude, click [OK].

Workflow Options

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

NOTES:

·If you are performing a list-level migration:

§Dependent workflow history and 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 initiated the migration 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: These options are only available for selection if 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 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 if 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.

4.If you want to preserve the Nintex Workflow external database entries (which contain the instance history for the Nintex Workflows), check the Preserve Nintex Workflow instance history 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.

Related Documents