Chat now with support
Chat with Support

On Demand Migration Current - Administrator Guide

About On Demand Migration Before You Start Working with On Demand Migration 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

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.

Exporting Site Collection Mapping

To export site collection mapping into comma-separated values (CSV) file for analytics or archival purposes open Site Collections and click Export.

Output CSV file will contain mapping data for discovered and matched (migrated) site collection URLs.

Migrating Sites

Double-check that the account migration is finished (or at least that all SharePoint users are migrated) and create the Migration task:

  1. Open Site Collections and select the items you want to migrate.

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

  1. Click Migrate.
  1. Provide the target account (FQDN) that will be used as the default owner (if the actual owner is not found.) The value set in the task is preferred over the project setting.
    By default, this filed is already populated with the default target user configured on the project level.
  1. Specify whether child entities are migrated. By default, the entire collection stricture is migrated.
  2. Specify whether the existing target sites are cleaned up (all exciting content removed) before migration.

Caution: If this option is selected, all content of the target site is removed and replaced by source site's content! Use with extreme caution.

  1. Schedule when the task will be started. See Task Scheduling for details.
  1. Click Next to view the task summary. Name the task and check selected options. Click Finish to save or start the task depending on schedule option selected.

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

Related Documents