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 Mail Migration Public Folders Migration OneDrive Migration SharePoint Migration Microsoft Teams Migration Content Migration for Office 365 Groups Troubleshooting Finalizing the Migration

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:




NOTE: File names containing non-ASCII characters are not supported.
  1. Go to the migration project Dashboard in case you use new migration UI. In case you are using classic experience or you are already on the SharePoint migration Dashboard, go to step 4.
  2. Click SharePoint widget.
  3. Open SharePoint Contents and click Map from File. Do not select anything from the list – you have already provided all required data in the file.
  4. Click Browse to open the mapping file created on Step 1.
  5. Browse for file and click Open. Selected file name appears next to the Browse button.
  6. Schedule when the task will be started. See Task Scheduling for details. Click Next to view task summary.
  7. 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.


  • 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.


SharePoint sites, webs and lists can be grouped in collections.

To gather a site and all its children into a collection

  1. Add the site to a collection.
  2. Run the Discover SharePoint Contents task for the site.

For known issues, see


Exporting Site Collection Mapping

To export site collection mapping into comma-separated values (CSV) file for analytics or archival purposes open SharePoint Contents on SharePoint migration Dashboard, select site collections to export and click Export.

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

Removing Sites from the Migration Project

You can temporarily remove any source site collections from the migration project, if necessary. Consider, site collections cannot be removed permanently from the migration project, all existing source site collections will be added in after next discovery.

To temporarily remove sites from the migration project:

  1. Go to the migration project Dashboard.
  2. Click SharePoint widget.
  3. Open SharePoint Contents and select the items you want to remove from the migration project.
  4. Click More Actions | Delete
  5. Click Delete to confirm the action.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating