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:
- Click Configure Project on the SharePoint migration dashboard.
- In the Edit Project dialog, change default source and/or target SharePoint Admin Center Urls to the custom ones and click Save.
IMPORTANT: 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.
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:
- 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 3.
- Click SharePoint widget.
- Open Site Collections.
- Select the site you want to match and click Match.
TIP: Use search to quickly navigate through the list of site collections.
- By default, the matching is performed based on the URLs. Use manual mapping to match with a different criteria. Click Next to proceed.
- Schedule when the task will be started. See Task Scheduling for details. Click Next to view the task summary.
- 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 Migration Project Dashboard or monitor alerts and notifications in the Events.
Refer to the SharePoint Migration Considerations for details on processing behavior if the target site/subsite exists before the migration is started.
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.
- 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.|
- 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.
- Click SharePoint widget.
- 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.
- Click Browse to open the mapping file created on Step 1.
- Browse for file and click Open. Selected file name appears next to the Browse button.
- Schedule when the task will be started. See Task Scheduling for details. Click Next to view task summary.
- 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.
Exporting Site Collection Mapping
To export site collection mapping into comma-separated values (CSV) file for analytics or archival purposes open Site Collections 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.