Converse agora com nosso suporte
Chat com o suporte

Content Matrix 9.9 - 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 2013 and Later 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

Import Pipeline Batches Getting Stuck

Navigation:  Frequently Asked Questions >

Import Pipeline Batches Getting Stuck

Question

I am migrating some content using the Import Pipeline.  After some time the batches seem to simply stop. Why am I facing this issue?

Answer

Migration duration and overall performance using the the Import Pipeline may vary due to factors outside the control of Content Matrix. Migration processing resides within Microsoft's domain and is subject to Microsoft's internal processes, such as maintenance and upgrades.

You may experience a delay of several hours before batch completion if the machines that Microsoft uses undergo maintenance/upgrades or if there are Microsoft 365 service issues/outages (as can be seen in the Microsoft 365 Admin Center under Service Health).

Migrating Content When the Source Custom List Template is Missing

Navigation:  Frequently Asked Questions >

Migrating Content when the Source Custom List Template is Missing

Question

I have a list on my source that uses a custom list template (ex. a "Fab 40" list) and I want to migrate that list to my new target SharePoint environment. However, I am unable to install that template on my target before migration. How will Content Matrix deal with this?

Answer

If at all possible, it is recommended that users install any custom list templates on the target environment before migration. That would allow Content Matrix to use those templates when migrating, and trying to reproduce the same results on the target. But there are some customizations within templates that Content Matrix is unable to migrate content or metadata into, such as the "Fab 40" templates.

In some cases users are unable to install the custom templates in the target environment, such as when migrating to Microsoft 365. In these cases Content Matrix will attempt to find the base template of the source customized list. Then it will create a list on the target using that same base template, and migrate the content into that list.

To help with this two variables have been added to the list XML attributes. They are:

·BaseTemplate - This is the value for the custom list template.

·BaseType - This is the value for the default template that any custom template is based on. If the custom template does not exist on the target, this template will be used for the list creation instead. Please see http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.client.basetype(v=office.14).aspx for more information on the SharePoint BaseType value.

These variables will help Content Matrix determine which base template to use so that an "Issue Tracking" list won't be created in a case where it should be a "Custom List" template.

Let's look at an example where you have a custom list on the source, and that list has a BaseTemplate value of "1011", a BaseType of "0", and has not been installed on the target. In this case, Content Matrix will look at the source list and find the BaseTemplate value of 1011. It will then look on the target to see if there is a template that has the same value. If it finds one, then Content Matrix will create a list with that template and migrate the data over. But, if the BaseTemplate value is not found on the target, then Content Matrix will look at the BaseType value instead, since this value should exist by default in the target SharePoint environment. In this example we also happen to know that a BaseType value of "0" is a "Custom List" or "Generic List" type. So Content Matrix will create a list on the target, using the "Custom List" template, and will then migrate the source data into that custom list.

When Migrating to SharePoint Online HTTP Status Code 429 (“Too many requests”) or 503 (“Server Too Busy”) Message Returned

Navigation:  Frequently Asked Questions >

When Migrating to SharePoint Online HTTP Status Code 429 (“Too many requests”) or 503 (“Server Too Busy”) Message Returned

Question

When migrating to SharePoint Online, why do I receive one or both of the following messages?

·429 (“Too many requests”)

·503 (“Server Too Busy”)

Answer

SharePoint Online uses throttling to maintain optimal performance and reliability of the SharePoint Online service.

As of version 9.8, Content Matrix has incorporated the use of RateLimit headers developed by Microsoft to reduce throttling.

Refer to the Microsoft article Avoid getting throttled or blocked in SharePoint Online for a description of RateLimit headers and additional tips on how to avoid throttling.

How Do I Identify and Remove Containers and Queues from My Azure Private Storage Account?

Navigation:  Frequently Asked Questions >

How Do I Identify and Remove Containers and Queues from My Azure Private Storage Account?

Question

I am running out of storage space in my Azure private storage account. How do I remove containers and queues created by Content Matrix to free up space for more migration actions?

Answer

While you can use the Microsoft Azure Storage Explorer UI to delete items individually, you can use Azure PowerShell commands to simultaneously remove all containers or queues that were created on the same date.  A prerequisite to removing multiple containers and queues is that Azure PowerShell must be installed and configured. Refer to the Microsoft Azure PowerShell documentation for installation instructions and general information about Azure PowerShell Cmdlets.

Naming Conventions

Beginning in version 9.3, Content Matrix uses naming conventions that allow you to easily identify containers and queues created by Content Matrix during migration using the Import Pipeline.  

File Type

Naming Convention

Blob Container
(per SharePoint list)

YYYYMMDD-<List Internal Name>-<GUID>-<blob>.

EXAMPLE:  

20200929-shreddocumentt-f0da9f001d3b450cb36ad9e9ecae219f-blob

Metadata Container
(per Import Pipeline job)

YYYYMMDD-<List Internal Name>-<GUID>-<Batch number in XXX format>

EXAMPLE:  

20200929-shreddocumentt-f0da9f001d3b450cb36ad9e9ecae219f-001

Reporting Queue
(per Import Pipeline job)

YYYYMMDD-<List Internal Name>-<GUID>-<Batch number in XXX format>

EXAMPLE:

20200929-shreddocumentt-f0da9f001d3b450cb36ad9e9ecae219f-001

To remove items from your Azure blob storage account using Azure PowerShell:

1.Ensure there are no active migration actions running that use the Azure storage where the items are stored.

2.Open Azure PowerShell.

3.Connect to Azure using the New-AzStorageContext cmdlet. Your account name and account key are required parameters. Note that these are different from your Client ID and Application Secret.        $context = New-AzStorageContext -StorageAccountName $accountName -StorageAccountKey $accountKey

4.Use the information in the following table to determine the appropriate command to use.

If you want to remove ...

Then use the command ...

all blob and metadata containers created on a specific date

Get-AzStorageContainer -Prefix "<MMDDYY>" -Context <context> | Remove-AzStorageContainer -Force

 

EXAMPLE:

Get-AzStorageContainer -Prefix "20200929" -Context $context02 | Remove-AzStorageContainer -Force

all reporting queues created on a specific date

Get-AzStorageQueue -Prefix "<MMDDYY>" -Context <context> | Remove-AzStorageQueue -Force

 

EXAMPLE:

Get-AzStorageQueue -Prefix "20200929" -Context $context02 | Remove-AzStorageQueue -Force

 

Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação