You can temporarily remove any source public folders from the migration project, if necessary. Consider, public folders cannot be removed permanently from the migration project, all existing source public folders will be added in after next discovery.
To temporarily remove public folders from the migration project:
Make sure that all associated accounts are matched or migrated in account migration project and create the Migration task:
|
TIP: Use search and filtering to quickly navigate through the list of public folders. |
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.
On Demand Migration offers a fast and convenient way to transfer SharePoint content between Office 365 tenants. SharePoint migration functionality requires additional licensing.
|
IMPORTANT: Before migrating any SharePoint sites, you must ensure all affected accounts exist in the target tenant. |
|
NOTE: SharePoint migration projects use the concepts and terminology of the Classic experience (site collections.) . |
Getting Started widget on SharePoint migration Dashboard with Quick help helps you to prepare, start and perform all steps to migrate your SharePoint sites successfully.
Basic SharePoint migration workflow consists of the following steps:
# | Step |
---|---|
1 | Create SharePoint migration project |
2 | Set the migration defaults (optional) |
3 | Grant necessary permissions |
4 | Discover site collections (top-level sites) on the source tenant |
5 | Map source sites to the existing target sites by URL (optional) |
6 | Provide the custom site mapping using CSV file (optional) |
7 | Override migration defaults for specific migration tasks (if necessary) |
8 | Migrate site collections and their content |
9 | 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 migration. |
Quest On Demand migrates the following SharePoint content:
Supported Entity | Supported Entity Properties |
---|---|
Site collections and sites (Modern experience: top-level sites and subsites) |
|
Site templates (partially) |
NOTE: Sites and subsites based on unsupported templates are not supported for site collection discovery and migration and will be skipped. |
Content types |
|
Column types of site, list, and content type |
|
List and libraries |
NOTE: Version history transfer means a significant increase in migration time.
|
List templates |
|
Folder |
|
List item |
|
Document |
|
Site pages |
|
Web Parts |
NOTE:Verified web parts have been tested to ensure all links and references to SharePoint entities are updated during migration as required. Unverified web parts are migrated as is to the target tenant, links and references to other SharePoint entities may remain linked to the entities on the source. |
Quest On Demand supports Shared with me panel functionality on the user's Office portal OneDrive pages for the documents and folders shared using SharePoint.
© 2021 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy