Chatee ahora con Soporte
Chat con el soporte

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

StoragePoint Content Migration

There are a number of different behaviors to expect when migrating to a target SharePoint environment that has Quest® StoragePoint installed. The different results you will see depend on which option is selected in the StoragePoint Options tab.

Prerequisites for Migrating StoragePoint Content

You can use Content Matrix to migrate StoragePoint content if Content Matrix detects that StoragePoint version 5.1 or later (or for SharePoint Server Subscription Edition, StoragePoint version 6.2 or later) is installed on the target.

For content to be externalized:

·An endpoint must be configured on the target.

NOTE:  If you do not have an endpoint configured, content will be migrated directly into SharePoint.

·For a SharePoint 2010 source Database connection, an external connection to StoragePoint must be made.

·For a SharePoint 2013 or later source Database connection, an external SharePoint server connection must be made.

NOTE: Content cannot be externalized if the source is SharePoint 2007.

To allow the migration of large files:

·Large File Support must be enabled in StoragePoint.

·If a source Database connection is used, a Host Name must be set.

·If migrating to SharePoint Online, the Import Pipeline must be used.

NOTE:  Use of the Import Pipeline allows you to migrate files over 2 GB.  For migrations to SharePoint on premises, you can migrate files up to 2 GB.

·An external connection to StoragePoint must be made.

To make an external connection to StoragePoint (to allow Large File Support):

1.Select the site whose StoragePoint content you want to migrate.

2.Right-click and choose Attach External Connections > StoragePoint Connection.

3.For Host Name when connecting to the StoragePoint database, click [Fill in default URL] to have it auto-populated.

StoragePoint Options - Successful Outcome

·Add documents to StoragePoint if an endpoint is configured - This option is for when content from a non-externalized environment (a source environment that does not have StoragePoint installed) is being migrated into an externalized SharePoint target. In this case, any of the files or documents that are included in the migration will be externalized, meaning that those files and documents will call StoragePoint as they are being migrated, and will be externalized directly with the reference link left behind in the file or document's place (in the target SharePoint environment). Once the migration is complete, users can navigate to one of the migrated documents in Content Matrix, switch to the Items View, right-click the document, and then select StoragePoint Details. Here, users should be able to see the StoragePoint endpoint folder location for the externalized content, as well as the externalized file name. If the document is opened through SharePoint directly, it will open as expected.

·None - This option is for cases where users do not want to use StoragePoint as part of the migration process. When this option is selected, content will be migrated directly into SharePoint with all StoragePoint-related features ignored. However, if the target environment is configured to be externalized with StoragePoint, it is possible that the content will be migrated into the SharePoint target as if the StoragePoint options are ignored, but the target SharePoint environment would then externalize the content separately after the migration completes. While the end result would be the externalization of the data, the migration process itself is only migrating content directly into the SharePoint target.

StoragePoint Options - Unsuccessful Outcome

·Add documents to StoragePoint if an endpoint is configured - If this option failed to migrate the documents/files into StoragePoint, then when users go to the StoragePoint Details, there will be nothing set. This indicates that the files were not placed into the StoragePoint EndPoint and were not externalized.

·None - If this option is selected but fails, then the content migration to the target will have failed. This means that the documents/files that are included in the migration action will not exist on the target (externalized or not).

Additional Considerations for Nintex Forms

Content Matrix can migrate Nintex Classic and Responsive forms.

Connection icon

The migration of Nintex forms is supported for Object Model (OM) on premises connections, either local or remote (through the Metalogix Extensions Web Service (MEWS)).  

Even if you elect to Use Import Pipeline to migrate to SPO, Nintex forms will be migrated to the target using CSOM.

Prerequisites

·For migrated Nintex forms to be published on a SharePoint on premises target, the SharePoint features Nintex Forms Prerequisites and Nintex Forms for SharePoint List Forms must be activated.

·For Nintex forms to be published on an SPO target, the Nintex Forms for Microsoft 365 app must be deployed.

If prerequisites are not met before migration, the forms will need to be published manually after the features or app is installed on the target.  

Current Limitations

·Nintex forms do not migrate for default content types of Asset Libraries.

·The following Nintex Responsive forms controls in SharePoint on premises are not supported in SharePoint Online and will be replaced with label controls on the target:

§SQL Request

§Web Request

§Change Content Type

Initiating a Migration

From the Content Matrix Explorer View, you can "copy" an object from the source connection then "paste" it to the appropriate location on the target connection.  You will then be prompted to configure Copy Options.

Before you initiate a migration, it is strongly recommended that you review How Content Matrix Handles Various SharePoint Components.  

Migrating as a Site Collection

Content Matrix can migrate SharePoint Site Collections and promote sub-sites into Site Collections. These migrations can be made within the same SharePoint instance, or can be performed between two separate SharePoint instances. Any site can be promoted into a Site Collection in the same way any Site Collection can be copied to become a sub-site. The location in the hierarchy of the target node is what determines if a site will copy as a Site Collection or as a sub-site.

 

Connection icon

·For migrations to an on premises SharePoint target, an Object Model (OM) level connection must be made with the target environment.

NOTE:  Due to some User authentication changes that have been made starting with SharePoint 2013, which inadvertently restrict the creation of Site Collections using the SharePoint OM remotely,  Content Matrix will use a set of elevated permissions to create Site Collections, which means the migrating user account must explicitly (by name) have "Full Control" permissions on the Web Application that the Site Collection is being created on. A preliminary check will be made before elevation occurs to ensure the migrating user has enough permissions initially to be able to use the elevated Site Collection creation. Creating Site Collections for a SharePoint on premises target with the Local OM connection type does not have this same restriction, but the same permissions are recommended in case elevated permissions are needed.

·For migration to a Microsoft 365 tenant, a Microsoft 365 Tenant connection must be used.

To initiate a Site Collection migration:

1.In Explorer View, select the source site collection or site that you want to migrate.

2.Right-click and choose Copy Site.

3.Select the target node under which you want to create the site collection.

4.Right-click and choose Paste Site Collection.

Paste as Site Collection

The Configure Site Collection Copying Options dialog displays.

Continue with Configuring Copying Options.

Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación