Chat now with support
Chat with Support

Welcome, erwin customers to Quest Support Portal click here for for frequently asked questions regarding servicing your supported assets.

On Demand Migration Current - Administrator Guide

About On Demand Migration Signing up for Quest On Demand Before You Start Working with On Demand Migration Starting a Migration Project Account Migration Mail Migration Public Folders Migration OneDrive Migration SharePoint Migration Microsoft Teams Migration Content Migration for Office 365 Groups Troubleshooting Finalizing the Migration

Issues: warnings and errors

To see the warnings and errors for a given object

From the SharePoint contents tab

  1. Highlight the object to see the details pane on the right.
  2. From the details pane click Events.

Repair using granular migration of a site, lists, web, SharePoint members

From the SharePoint contents tab

  1. Locate objects with object state provisioned with issues or content state migrated with issues. See Review migration results.
  2. Check these objects.
  3. Click Migrate. See also Migrate.

List objects: warnings and errors

If a list object content state is migrated with issues then the most likely reason is the number of list items is fewer on the target than on the source.

To see the number of list items on the source

From the SharePoint contents tab

  1. Highlight the list object to see the details pane on the right.
  2. The details pane provides a count of the number of the list items for this list on the source.

Repair using granular migration

From the SharePoint contents tab

  1. Locate the list objects that did not migrate.
  2. Check these objects.
  3. Click Migrate. See also Migrate.

Incremental migration of lists

The On Demand Migration for SharePoint service can migrate new and updated list items in previously migrated lists with the content state migrated. See Object and content states.

NOTE: Incremental migration of system libraries like Site Pages is not supported. These libraries are always fully re-migrated. See Merging and Re-Migration Considerations.

To trigger an incremental migration of a SharePoint list:

  1. Open the SharePoint contents tab and locate the SharePoint list. There are a couple ways to do this:
    1. Add a filter to show only objects of type list.
    2. Add a filter to show only lists with content state migrated.
  2. Select the list. You can check multiple lists to migrate multiple lists.
  3. Click MIGRATE

Repairing lists with migration issues

The On Demand Migration for SharePoint service can repair lists with the content state Migrated with Issues. See Object and content states. When such a list is migrated, the contents of the list in the source and target tenants are compared. Missing items in the target are restored and items that are updated in the source since the previous migration will be incrementally migrated.

Lists are migrated based on the migration state. You can select multiple lists with different content states and the lists will be migrated based on its state. For example, an incremental migration will occur if new list items were added to a source list that was previously migrated, a repair migration will occur if the list was migrated with issues, and a full migration will occur for lists that have not been migrated.

To repair a list with migration issues:

  1. Open the SharePoint contents tab and locate the SharePoint list as described below:
    1. Clear all filters and search criteria Add a filter to show only objects of type List.
    2. Add a filter to show only objects where Type = List and Content State = Migrated with Issues.
  2. Select the list. You can select multiple lists if needed.
  3. Click MIGRATE. The New Migration Task wizard starts.
  4. Step 1: Options
    1. Specify the information as described below:
      1. Map unmatched users to - enter the Office 365 email address of an existing user in the target tenant.
      2. Include child structure and content - select this option if the list has any hierarchical items that you want to migrate.
      3. Clear selected SharePoint objects from the target before starting the migration - if this option is selected, a full migration will occur because the target list will be deleted and the existing migration state will be ignored.
    2. Click Next.
  5. Step 2: Version Options
    1. Select from the following options:
      1. Migrate most recent version only
      2. Migrate two most recent versions
      3. Migrate more versions (with options) - you must specify additional criteria if you select this option.
    2. Click Next.
  6. Step 3: Schedule
    1. Choose from one of three options to schedule the task. The scheduler will be activated only after you complete the task wizard.
      1. Run now - the task will run immediately.
      2. Run later - the task will start after a time delay.
      3. Schedule - specify a future date and time.
    2. Click Next.
  7. Step 4: Summary
    1. Verify the task settings.
    2. Click Next.
  8. When the task completes, verify the Content State for the selected list. If issues persist, check for event warnings.

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. Go to the migration project Dashboard.
  2. Click SharePoint widget.
  3. Open SharePoint Contents.
  4. Select the site you want to match and click Match.

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

  1. Enable the Include site content option to also match discovered child objects on the source with the corresponding object on the target, if it exists.
  2. By default, the matching is performed based on the URLs. Use manual mapping to match with a different criteria. Click Next to proceed.
  3. Schedule when the task will be started. See Task Scheduling for details. Click Next to view the task summary.
  4. 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.

See the Considerations for details on processing behavior if the target site or sub-site 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.

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

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

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating