Tchater maintenant avec le support
Tchattez avec un ingénieur du support

On Demand Migration Current - User Guide

About On Demand Migration Before You Start Account Migration Mail Migration Public Folders Migration OneDrive Migration SharePoint Migration Microsoft Teams Migration Microsoft 365 Groups Migration Troubleshooting Finalizing the Migration

Considerations

Your target tenant might already host SharePoint top-level sites (site collections) or sub-sites created before the migration. See the table below to see the migration action that will be used depending on the existing site properties and the selected migration options.

Target site (sub-site) exists Source and target default languages match Clear existing site collection option is selected Migration action
Yes Yes No Merge, all supported properties will be overwritten using source settings
Yes Yes Yes Create and migrate
Yes No Yes/No Skip and report
No - - Create and migrate

Merging and Re-Migration considerations

  • Sub-sites based on unsupported site templates are skipped
  • System settings including site columns, content types etc. from the source will overwrite settings that were changed on the target.
  • New site structure including list item and docs that only exist on the target remains unchanged.
  • If a new list item with the same name is added on both source and target, the source item will be migrated and added as a separate item (i.e. target will have two items with identical names).
  • If a new document with the same name is added on both the source and target, the migration of the source item will be skipped, and the warning that the item already exists on the target is reported. Document libraries only allow one document per name.
  • For previously migrated list items and docs (same name and ID):
    • Updates on source will be migrated to the target
    • Updates to target will be overwritten by re-migrated source item or document
  • System libraries like Site Pages are always cleared before a re-migration. Any new files added only to the target will be deleted from the target as part of the re-migration.

Currently, only the latest versions of documents and list items are migrated. In case of re-migration, please consider the following:

  • The migrated document is always replaced, document version remains unchanged.
  • The list item is always replaced and list item version remains unchanged, unless Create a new version each time you edit an item in the list list versioning setting is enabled. If this setting is enabled, the remigrated list item will be added as new version.

Language considerations

When SharePoint groups in a site are migrated from a source to a target tenant with different default site languages, the group names may not match. In that case, the source groups are migrated to the target tenant with the original names from the source.

For Team sites (sites associated with the Microsoft 365 Groups and Teams) the migration of some members in the default SharePoint group may fail because the reference to the M365 group cannot be matched due to the different languages on the source and target. The resulting warning event is benign because equivalent permissions to the SharePoint group on the source will be created during the Teams or Microsoft 365 group provisioning by the Teams migration service.

SharePoint Migration Dashboard

Using this intuitive interface you can:

  • Keep track of your location within project and quickly return to the main project dashboard using breadcrumbs on the top of the pane
  • View list of discovered site collection with last information, completed workflows, site collection information, and last events related to the site collection
  • Quickly navigate to the event lists
  • Quickly navigate to the tasks list
  • Create discovery tasks, matching tasks, and site collection migration tasks
  • Export feature data into comma-separated file and use this file for manual mapping
  • Temporarily remove sites from migration project
  • Search site collection
  • Filter site collection by workflow, or by matching state
  • Delete site collection

Prerequisites

  • It is highly recommended to match / migrate all accounts in the corresponding Migration project to ensure that membership and content ownership are processed correctly.
  • The target tenant should already have the fully configured SharePoint with the active license plan. Note, that licenses are not automatically assigned to the target users during the migration.
  • Consents already get granted for source and target tenants.
    The following admin consents should be granted for SharePoint migration feature:
    • Migration - Basic,
    • Migration - SharePoint

In case necessary admin consents are not granted or expired, discovery will be disabled and the following notification will be displayed: Grant admin consent to the Migration module on the Tenants page for both source and target tenants: Basic and SharePoint. To grant admin consents open Tenants page and grant the Required Consents and Permissions to allow the product to access the source tenant and the target tenant. You will be redirected to the Microsoft web site for granting admin consent. Once admin consent is granted, you can start discovering site collections.

Configuring the Migration Project

You must set a default site owner that will be used if the actual owner (user account) is not found in the target. See the details on user mapping below.

Caution: If both the actual owner account and the default owner are not found in the target, the migration task will fail.

  1. Go to the migration project Dashboard in case you use new migration UI.
  2. Click SharePoint widget.
  3. Click Configure Project on the project dashboard.
  4. In the Edit Project dialog, provide the user from the target tenant and click Save.

You can set a different default owner for a group of sites by overriding this setting in the migration task.

User Mapping Workflow

During the migration, On Demand Migration gets the accounts associated with the migrated (source) site and then looks up their pairs in the target tenant. Depending on the results, one of the following actions is performed:

  • If a matched target user is found, On Demand Migration sets it as an owner of the migrated site.
  • If a matched user is not found on target, On Demand Migration switches the site owner to the default account.
  • If the actual owner account has no match on the target and the default owner is missing, the migration task fails.

This table describes how ownership is handled by On Demand Migration depending on the SharePoint entity:

SharePoint Entity Matched owner found Matched owner missing Matched owner and default user missing
Top-level sites (site collection) Target account matched with source owner Default target user Migration Task fails
Sub sites System account

System account

Lists

System account

System account

Folders Target account matched with source owner Default target user
Files Target account matched with source owner Default target user
List Items Target account matched with source owner Default target user

Setting Custom SharePoint Admin Center URLs

On Demand Migration builds the expected SharePoint Admin Center URL based on SharePoint's default naming convention. If a customer has custom SharePoint Admin Center URLs, these URLs should be set manually as described below:

  1. Click Configure Project on the SharePoint migration dashboard.
  2. In the Edit Project dialog, change default source or target SharePoint Admin Center URLs to the custom ones and click Save.

NOTE: On Demand Migration does not validate SharePoint Admin Center URLs. These URLs are a subject of special request to Microsoft. Do not change the default URL if the custom one is not yet approved by Microsoft.

Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation