立即与支持人员聊天
与支持团队交流

Content Matrix 9.10 - SharePoint Edition

Introduction Activating the License Key Selecting the SQL Database You Want to Connect to Content Matrix Console End User Interface Enabling Advanced Mode Multilingual Support Connecting to SharePoint Preparing for a Migration How Content Matrix Handles Various SharePoint Components
Team Site to Modern Team Site Migration SharePoint Sites to Modern Communication Site Migration Promotion of First Level Subsites to Site Collections MySite Migration "Share With" Metadata and "Sharing Links" Access Permissions Migration Records Center to SharePoint Online Migration Using the Import Pipeline Master Page Migration List Template Gallery Migration Content Types Migration Document Version and Checked Out File Limitations Ghosted and Un-Ghosted Page Migration Document Set Migration Navigation Migration Classic Web Parts Migration Site Theme Preservation Site Feature Migration Managed Metadata Migration Users and Permissions Migration BCS/BDC Data Migration OneNote Notebooks Migration Customized Form Pages Migration InfoPath Forms Migration SharePoint Workflow Migration Nintex Workflows and Forms Migration Link Correction StoragePoint Content Migration
Initiating a Migration Configuring Copying Options Saving or Running a Migration Job Copying SharePoint Objects as a Separate Action Configuring Hub Sites Incremental Migration Using PowerShell with Content Matrix
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
DB_Owner Permission Keyboard Shortcuts Activating the License Key Silently License Key Troubleshooting Errors Connecting to SharePoint 2019 or SharePoint Server Subscription Edition in a FIPS-Enabled Environment 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 Extensions Web Service Installation Files Migrating JavaScript Migrating Site Variations Migrating with SharePoint Document IDs Changing a Job Configuration for Multiple Files SharePoint Site Collection Creation Issue Customized Wiki Page Web Part Zones Not Being Migrated Preserving SharePoint List Item IDs When Migrating to SharePoint Online Retrying Failed Document Copies to SharePoint Online CSOM Connections Import Pipeline Batches Getting Stuck Migrating Content When the Source Custom List Template is Missing When Migrating to SharePoint Online HTTP Status Code 429 (“Too many requests”) or 503 (“Server Too Busy”) Message Returned How Do I Identify and Remove Containers and Queues from My Azure Private Storage Account? Error: 'The object is associated with property AssociatedMemberGroup.' Migration Error: 'ERROR, the batch will be resubmitted to 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

Mapping Items to Content Types

You can specify content types for target items when you click the [...] button from the Content Type Application Options dialog.

To map items to content types:

PF Map Items to Content Types

1.Select the content type, and click [Edit Conditions] to display the List Items and Documents Where filter dialog.

2.Select the filter(s) you want to apply as you would when Applying Filter Expressions.

NOTE:  If you select [Clear Condition], all conditions that are currently applied to that content type will be cleared.

3.Once all filters have been set, click [OK] to return to the Content Type Application Options dialog.

Applying New Document Sets to Libraries, Folders, and Documents

Content Matrix can apply Document Sets to libraries, folders, or documents as a part of a migration. Document Sets can be applied when migrating to SharePoint (including Microsoft 365), and can be configured at the time of migration. This feature allows for any SharePoint folders, or document libraries to be migrated as a SharePoint Document Set. Please see Microsoft's Document Sets planning page for more basic details on document sets.

NOTE:  If you want to apply an existing Document Set to a list, library, or folder, initiate a list-level migration and paste the object to a Document Set on the target.

When you check the Apply new document sets during copy check box and click the [...] button from the List Content Options dialog, the Apply Document Sets dialog displays.  

Apply Document Sets

To apply new Document Sets:

1.In the upper (tree view) window, select the content to which you want to apply the Document Sets.

2.Select the appropriate Apply Document Set option.  Use the information in the following table for guidance.

If ...

Then ...

·you selected a folder

AND

·you want to apply a Document Set Content Type

A.Select Apply Document Set to Selected Folder to display the Document Set Content Type dialog.

Document Set Content Types

B.Select an available Content Type from the drop down.

C.Click [OK] to dismiss the Document Set Content Dialog and return to the Apply Document Sets dialog, which now displays the newly added mapping in the Folders tab.

·you selected a document library

AND

·you want to apply  a new Document Set  to all or selected items within the library based on a filter expression

A.Select Apply New Document Set To Library to display the Map Documents to Document Sets dialog.

Map Documents to Document Sets

B.Click [New Document Set] to display the Enter Name dialog and enter a name for the new Document Set.

C.Click [OK] to dismiss the Enter Name dialog, and display the Document Filter Conditions dialog.

D.Apply the desired filter expressions for the item-level Document Set.

NOTE:  If no condition filter value is entered in the Document Filter Conditions dialog, no items in the document library will be applied to the Document Set.

E.Click [OK] to dismiss the Document Filter Conditions dialog and re-display the Map Documents to Document Sets dialog.

F.Select the appropriate Content Type to apply to the Document Set from the drop-down.

G.Click [OK] to dismiss the Map Document Sets dialog and return to the Apply Document Sets dialog, which now displays the newly added mapping in the Lists tab.

·you selected a site

AND

·you want to apply new Document Sets lists and/or items on the site based on filter expressions

A.Select Apply New Document Set via Rule to display the Lists Filter Conditions dialog.

B.Apply the desired filter expressions for the list-level Document Set.

List Filter Conditions

C.Click [OK] to dismiss the List Filter Conditions dialog and display the Map Documents to Document Sets dialog.

D.Click [New Document Set] to display the Enter Name dialog and enter a name for the new document set.

E.Click [OK] to dismiss the Enter Name dialog, and display the Document Filter Conditions dialog.

F.Apply the desired filter expressions for the item-level document set.

G.Click [OK] to dismiss the Map Document Sets dialog and return to the Apply Document Sets dialog, which now displays the newly added mapping in the Lists tab.

H.Repeat Steps A-G to apply lists and items within the site to document sets.

·you initiated an item-level migration

AND

·you want to apply a new document set to individual items to  based on filter expressions

A.Select Apply New Document Set via Rule to display the Map Documents to Document Sets dialog.

B.Click [New Document Set] to display the Enter Name dialog and enter a name for the new document set.

C.Click [OK] to dismiss the Enter Name dialog, and display the Map Documents to Document Sets dialog.

D.Apply the desired filter expressions for the item-level document set.

E.Select the appropriate Content Type to apply to the document set from the drop-down.

F.Click [OK] to dismiss the Map Document Sets dialog and return to the Apply Document Sets dialog, which now displays the newly added mapping in the Lists tab.

Note that you can use the Navigate To option to locate the object to which a selected filter applies in the upper (tree view) window.

Managed Metadata Options

Before configuring Managed Metadata options, it is strongly recommended that you review the Managed Metadata Migration section for allowable connection types, permissions, and prerequisites.

Managed Metadata Options

NOTE:  You can also import Managed Metadata taxonomy mappings.

To configure Managed Metadata options:

1.If you want Content Matrix to check both the source and target environments to find any existing Managed Metadata term structure and then migrate a copy of the source term structure over to the target, make sure the Resolve managed metadata by name and hierarchy box is checked.

NOTE:  If there are terms that do not exist, they will be added (using the same hierarchy structure with new GUIDs), and if there are terms that already exist the terms on the target will be used.  If you want terms on the target to be overwritten with those on the source, make sure Map term stores for migration is selected, as described in the next step.

2.If you want to map the term store on the source to a term store on the target:  

NOTE: Migrating Managed Metadata at the site level will only copy the global Managed Metadata, and will not copy any site collection term sets. Site collection term sets are only copied when the Copy referenced managed metadata and Map term stores for migration options are enabled as part of a SharePoint site or list level migration.

a)Check the Map term stores for migration box, then click the [...] button.

The Map Term Store dialog displays with a list of all term stores that currently exist on the target.

Map Term Stores Dialog

NOTES:  

·This option is primary used in the following situations:

§When migrating the entire term store (the global term store).

§When migrating term stores by their ID value

§When migrating at the site collection level that uses more than one Term Store, to ensure that the correct Term Store is used.

·This option is required when migrating to a Microsoft 365 Tenant target environment. In such a migration, this option is enabled by default and cannot be deselected.

·If the Resolve managed metadata by name and hierarchy option is selected, this option would only be selected if you want to map and overwrite the values the target.

b)Right click the Source Term Store you want to map, and select the Target Term Store you want to Map to.

NOTE: If the Target Term Store is set to <Exclude> (the default value), the term store will not be mapped. A 1:1 Relationship must exist between Source/Target term store mappings

3.When you are finished mapping term stores, click [OK].

4.If you want to migrate Managed Metadata columns for items and lists, check the Copy referenced managed metadata box.

NOTE:  This option will not actually create Term Stores. It is recommended that this option be used in conjunction with the Resolve managed metadata by name and hierarchy and/or Map term stores for migration.

5.If you want SharePoint site columns (fields) to be transformed into Managed Metadata fields on the target:

a)Check the Transform specified site columns to managed metadata columns box.

b)Click the […] button.

c)Complete the Configure Transformations for a Site Column dialog as described in the topic Transforming a Site or List Column into a Managed Metadata Columns.

6.If you want SharePoint list columns (fields) to be transformed into Managed Metadata fields on the target:

a)Check the Transform specified list columns to managed metadata columns box.

b)Click the […] button.

c)Complete the Configure Transformations for a List Column dialog as described in the topic Transforming a Site or List Column into a Managed Metadata Columns.

7.If the SharePoint Enterprise Metadata and Keywords Settings option is enabled on the source and you do not want to migrate the Keyword term set or the Enterprise Keyword columns in lists/libraries, check the Skip Keyword term set migration box.

NOTE: The 'Skipping Keywords term set migration' and 'Skipping Enterprise Keywords column’ events will only display in the Job Log if the Copy referenced managed metadata box is also checked.

NOTE:  By default, Content Matrix migrates terms in batches of 50.  You can, however, change this value (for example, decrease it if you are experiencing timeout errors during the migration operation or increase it if you are migrating an excessively large number of terms or keywords).  However, It is recommended that you not  change the batch size unless absolutely necessary.  See Changing the Managed Metadata Migration Batch Size.

Importing Managed Metadata Taxonomy Mappings

If the TaxonomyMigrator has been used to migrate Managed Metadata term groups and term sets and a json file with taxonomy mappings has been generated, these mappings can be imported to the Content Matrix Job Database and/or Distributed Database using PowerShell for use in future migrations.

NOTES:

·Taxonomy migration creates all the term groups and term sets that are not present in the global taxonomy mappings.

·After importing to Content Matrix, mappings will be resolved during content migration and not remigrated.

·The imported mappings are handled as global mappings and not distinguished between multiple term stores.

·The mappings are not visible on UI and can be listed only via PowerShell.

Before Importing Managed Metadata Mappings:

Open the Content Matrix Console and from the Jobs List File menu select the option for the database to which you want to copy the mappings:

·Connect to Distributed Database

OR

·Connect to Job Database

To access the PowerShell cmdlets for importing taxonomy mappings:

Open a PowerShell or PowerShell ISE session and add the PowerShell snap-ins for the application framework.

The following cmdlets are now available:

Load-GlobalTaxonomyMappings

Get-GlobalTaxonomyMappings

Clear-GlobalTaxonomyMappings

To import global taxonomy mappings to the selected database:

Select (from the PowerShell ISE Command Window) or enter Load-GlobalTaxonomyMappings and enter the path to the JSON File , then run the cmdlet.

Example script:  

Load-GlobalTaxonomyMappings –JsonFile "C:\Temp\mappings.json".

 

NOTE:  It will be necessary to restart the Content Matrix Console after taxonomy mappings are loaded.

To display a list of global taxonomy mappings:

Select (from the PowerShell ISE Command Window) or enter Get-GlobalTaxonomyMappings, then run the cmdlet.

A list of the unique identifiers for each source/target mapping displays.

To clear global taxonomy mappings from the selected database:

Select (from the PowerShell ISE Command Window) or enter Clear-GlobalTaxonomyMappings, then run the cmdlet.

相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级