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
- Locate the SharePoint object.
- Check the object. You can check multiple objects to migrate multiple objects.
- Click MIGRATE to open the New Migration Task dialog.
- 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.
Review migration results
The migration task is complete and an object state is provisioned with issues or a content state is migrated with issues. Locate these objects in the SharePoint hierarchy.
Review using the SharePoint Content view
Once the migration task is complete, locate objects where the object state is provisioned with issues or the content state is migrated with issues using the SharePoint content view.
From the SharePoint contents tab
- Select the object so the row is highlighted and the details pane opens to the right of the screen.
- From the details pane click Show Contents
- Continue following the webs into the site structure until you see
- an object where the Object State is Provisioned with Issues
- a list where the Content State is Migrated with Issues
- From the details pane click SHOW PARENT to return upward through the hierarchy.
Review using Flat View and Filtering
Once the migration task is complete, locate objects where the object state is provisioned with issues or the content state is migrated with issues using a flat view of the objects and filtering.
To see all SharePoint objects in the table in a flat view
To filter the table to see all Share Point objects with issues with provisioning
- Set the Object State filter to Provisioned with Issues.
TIP: You can filter further by setting a filter on the object Type.
To filter the table to see objects with issues with the migration
- Set the Object State filter to Migrated with Issues.
TIP: You can filter further by setting a filter on the object Type. The smallest object type where migration issues will be found is List.