Chat now with support
Chat with Support

On Demand Migration Current - Administrator Guide

About On Demand Migration Before You Start Working with On Demand Migrations Starting Migration Project Configuring Connections Sharing Availability Information Collecting Account Information Pre-Migration Assessment Account Migration Domain Coexistence Mail Migration OneDrive Migration Resource Processing Public Folders Migration SharePoint Online Migration Microsoft Teams Migration Finalizing the Migration

Discovering Sites

Before proceeding with the migration, discover all site collections (top-level sites) in the source tenant. The discovery process enumerate all sites and retrieves the relevant data. Once the discovery task is complete, you will see the sites summary on the SharePoint Online Migration Project Dashboard and all sites will be shown in the Site Collections list.

  1. Click Discover Site Collections on the project dashboard to create a new discovery task.
  2. Schedule when the task will be started. See Task Scheduling for details. Click Next to view the task summary.
  1. Check scheduled start of the task and name the task. Click Finish to save or start the task depending on schedule option selected.

TIP: Give informative names for the tasks. It will greatly simplify the project management and event filtering in the future.

  1. Click Finish. You can monitor the task status using task widget on project dashboard.
  2. Click the task name on the widget to see the details or use Show all link.

Caution: Don’t start the migration before the discovery task is finished. It might result in incorrect processing of migrated objects.

Setting Migration Defaults

To simplify the site migration, you can 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. Click Configure Project on the project dashboard.
  2. 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 Online Entity Matched owner found Matched owner missing Matched owner and default user missing
Top-level sites (site colections) Target account matched with source owner Default target user Migration Task fails
Subsites 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

Matching Sites

Your target tenant might already host top-level sites (site collections) created before the migration. To ensure that no data is lost or duplicated, map them to the corresponding source site collections with theMatching Task:

  1. Open Site Collections.
  2. Select the site you want to match and click Match.

TIP: Use search to quickly navigate through the list of site collections.

  1. By default, the matching is performed based on the URLs. Use manual mapping to match with a different criteria. Click Next to proceed.
  2. Schedule when the task will be started. See Task Scheduling for details. Click Next to view the task summary.
  3. Check selected options, scheduled start of the task and name the task. Click Finish to save or start the task depending on schedule option selected.

The matching task is created. You can track its progress in the Tasks, view the summary on the SharePoint Online Migration Project Dashboard or monitor alerts and notifications in the Events.

Using the Manual Mapping for Sites

In most cases, identical URL is good enough mapping criteria. However, the site naming / structure on the target might be different while the content is the same (for example, /sites/IS site is renamed to /sites/helpdesk.) To handle such differences, provide a file with the custom mapping between source and target site collections.

  1. Prepare a comma-separated values (CSV) file with site collection pairs. The first row contains the name of the source and target attribute used for mapping (currently only URLs are supported.) Subsequent rows list value pairs for those attributes (one pair per row.) For example:

sourceURL,targetURL

/sites/tdemo,/sites/newsite

/sites/accounting,/sites/finance

NOTE: File names containing non-ASCII characters are not supported.
  1. Open Site Collections and click Map from File. Do not select anything from the list – you have already provided all required data in the file.
  2. Click Browse to open the mapping file created on Step 1.
  3. Browse for file and click Open. Selected file name appears next to the Browse button.
  1. Schedule when the task will be started. See Task Scheduling for details. Click Next to view task summary.
  2. Check selected options. Click Finish to save or start the task depending on schedule option selected.

The task is created. You can track the progress in the Tasks list or view the summary on the Dashboard.

NOTE:

  • If the site pair is not found (source, target or both sites are missing), it is ignored without producing an event. This might also happen if the source site exists, but was not enumerated during discovery.
  • The matching is always performed for all pairs provided in the file. Any selection, search, and filters set in the interface are ignored.
Related Documents