On Demand Migration Current - Administrator Guide

Specify whether subfolders will be migrated.
Specify whether public folder content will be migrated. You can clear this option for test migration to create an empty public folder structure and transfer folder permissions.

Schedule when the task will be started. See Task Scheduling for details.

Click Next to view the task summary. Name the task and check selected options. Click Finish to save or start the task depending on schedule option selected.

The migration task is created. You can track its progress in the Tasks, view the summary on the Dashboard or monitor alerts and notifications in the Events.

SharePoint Online Migration

On Demand Migration offers a fast and convenient way to transfer SharePoint Online content between Office 365 tenants. SharePoint migration functionality requires additional licensing.

IMPORTANT: Before migrating any SharePoint sites, you must ensure all accounts exist in the target tenant. Account Migration project for your source and target tenant should exists, and account matching /migration should be completed.

NOTE: SharePoint Online migration projects use the concepts and terminology of the Classic experience (site collections.) .

Getting Started widget with Quick help helps you to prepare, start and perform all steps to migrate your SharePoint sites successfully.

Basic SharePoint Online migration workflow consists of the following steps:

#	Step
	Create SharePoint Online migration project
	Set the migration defaults (optional)
	Grant necessary permissions
	Discover site collections (top-level sites) on the source tenant
	Map source sites to the existing target sites by URL (optional)
	Provide the custom site mapping using CSV file (optional)
	Override migration defaults for specific migration tasks (if necessary)
	Migrate site collections and their content
	Monitor the progress and track issues

IMPORTANT: Quest recommends performing test and pilot migrations before starting the full-scale migration of the production environment. This helps you better plan the migration project and align the migration tasks with the organization requirements.

Caution: Finish the account migration before starting SharePoint Online migration.

What We Migrate

Quest On Demand migrates the following SharePoint content:

Supported Entity	Supported Entity Properties
Site collections [Modern experience: top-level sites]	Site collection owner Top-level site Title Site template (STS#0 and STS#3 only) Site collection features Users Groups Site collection admins PermissionLevel
Sites under site collections [Modern experience: subsites]	Title Description Site template (STS#0 and STS#3 only) Inheritance (HasUniquePermissions) Site features Site columns Site content types List templates
Content type	Name Description Parent Group
Site and List Columns	Name Type Single line of text Multiple lines of text Choice Number Currency Date and time Yes/no Person or group Hyperlink or picture
List	List title List template (GenericList, DocumentLibrary, Announcements, Events, Contacts, DiscussionBoard, Links, PictureLibrary, IssueTracking, Tasks, TasksWithTimelineAndHierarchy) List columns Enable folder creation Version settings Enable versioning Enable content approval Drafts Versions limit (major, minor) Content type enabled
List Views (public)	Name Columns Default view (Standard, Calendar, Datasheet, Gantt)
Folder	Folder permissions
List item	ListItemPermissions Metadata (SingleLine, Multi Line, Choice, Currency, DateTime, Number, Url, Yes/No) Attachements Authoring details (Author, Editor, Created, Modified)
File	FilePermissions Metadata (SingleLine, Multi Line, Choice, Currency, DateTime, Number, Url, Yes/No) Authoring details (Author, Editor, Created, Modified)

Limitations

The default site language on the source and the target tenant should match.
On Demand Migration only discovers site collections (top-level sites) based on the templates STS#0 and STS#3. Migration of site collections based on other templates is not supported.
On Demand Migration only migrates subsites based on the templates STS#0 and STS#3.
Private views and personal sites are not migrated.
Only the latest versions of sites are migrated.
Checked out status for files in document libraries is not migrated.

Prerequisites

It is highly recommended to match / migrate all accounts in the corresponding Account Migration project to ensure that membership and content ownership are processed correctly.
The target tenant should already have the fully configured SharePoint with the active license plan. Note, that licenses are not automatically assigned to the target users during the migration.
Consents already get granted for source and target tenants.
The following admin consents should be granted for SharePoint migration project:
- Migration - Basic,
- Migration - Resource Processing for SharePoint

In case necessary admin consents are not granted or expired, discovery will be disabled and the following notification will be displayed: Grant admin consent to the Migration module on the Tenants page for both source and target tenants: Basic and Process Resources for SharePoint. To grant admin consents open Tenants page and grant necessary permissions to allow the product to access the source tenant and the target tenant. You will be redirected to the Microsoft web site for granting admin consent. Once admin consent is granted, you can start discovering site collections.