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

Object and content states

On the SharePoint Contents tab, use the Object state and Content state properties to determine the state of any SharePoint object in the migration process.

To populate the table see Populate SharePoint sites.

Object state

Use the object state property to track the object itself. When the object is added to On Demand its status is discovered. When discovered you can trigger a migration: Migrate.

State Description
Discovered On Demand has discovered the object on the source. See the steps to Migrate.
Matched On Demand has matched a site on the source URL with a corresponding site on the target URL.
Provisioned On Demand has created (updated) the SharePoint object (site, web, list, users and groups) on the target without warnings or errors. You are now ready to track the content state.
Provisioned with issues On Demand has created (updated) the object with warnings or errors. See Issues: warnings and errors.

Content state

Use the On Demand content state property to track the progress of migrating the SharePoint object's content. Note that the content state value is transient (may change) while the task status is in progress. See also The transient nature of the object and content states during migration.

State Description
Not Migrated On Demand has not migrated the content. This is the default content state when the object state is discovered.
Migrating On Demand is migrating the object content.
Migrated On Demand has successfully migrated the content to the target without warning or errors. If the object is a list then all the list items have migrated successfully. If the object is a SharePoint site or web (root site) then all the child lists and webs have migrated successfully.
Partially Migrated While a migration task is in progress, partially migrated can be a transitory state showing at least one child is migrating or not migrated. Once the migration task is complete, partially migrated indicates that not all children of the object migrated: at least one child migrated and at least one child did not migrate.
Migrated with Issues On Demand has migrated the content to the target with warnings or errors. See Issues: warnings and errors.

Migrate

Any discovered SharePoint object (object state = discovered) can be migrated including sites, lists (including individual lists) and webs (root and child webs). All children of the object selected for migration will be migrated.

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

To trigger a SharePoint migration

From the SharePoint contents tab

  1. Locate the SharePoint object.
  2. Check the object. You can check multiple objects to migrate multiple objects.
  3. Click MIGRATE to open the New Migration Task dialog.

NOTES:

  • When migrating multiple SharePoint sites, it is best practice to add no more than 10 sites to a migration task to avoid creating a large load that may trigger throttling in the Microsoft export interfaces.
  • Creating and running multiple migration tasks at the same time may create a large load that may trigger throttling in the Microsoft export interfaces.
  • If the parent of the object selected for migration does not already exist on the target then migration will be skipped.
  • Migration of a site or web will do a full migration of all child lists (not incremental) and discovery of any new child web or list.

New Migration Task dialog

From the Version Options tab you can select to

  • Migrate the most recent version only
  • Migrate the two most recent versions
  • Migrate more versions (with options)

When migrate more versions (with options) is selected, additional options are made visible. Migrating documents with multiple versions will significantly increase the time needed for migration. These options are intended to provide a balance between the need to maintain historical data with the practicalities of migrating large amounts of data. Keep this in mind when making your selection.

  • Limit version migration based on document size: The default setting for the version migration document size limit is 80 MB. The larger the selected size limit, the longer the migration will take. For each file, if the most recent version of the file exceeds the size limit then only the most recent version of that file is migrated. If the most recent version of the file is smaller then the size limit then versions of the file are migrated according to the following specifications, irrespective of each version's file size .
  • And limit number of versions migrated from each day (does not override document size limit) Days are measured in UTC time. If migrating one version from each day is sufficient then select to migrate the most recent version from each day. Otherwise, select to migrate the 5 most recent versions from each day for versions created in the last 30 days, then migrate the most recent version from each earlier day. Note the next constraint on the maximum number of versions of the file to be migrated.
  • And limit number of versions migrated for each document (does not override document size limit) The number of versions of each file On Demand will migrate will not exceed the maximum number of versions to be migrated listed here.

The transient nature of the object and content states during migration

When migrating a site the web and list task status will be set to complete when the web or list object state is set to provisioned. This is expected behavior in the current implementation. It indicates that the sub task to provision the object is complete. The Content State will not go to migrated until the child content is migrated

When migrating a site or web, the content state may be set to migrated and then reset to partially migrated. This will typically happen for a site that had not had the SharePoint content discovery run before migration is started. In this case the migration is discovering content to migrate as it goes along. The content state is set to migrating when the migration completes what it has discovered so far, then it looks for more and resets to partially migrating, repeating until all content is discovered and migrated. It discovers lists in a web in groups (not all at once) and then it discovers any sub sites after the lists are done.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating