Converse agora com nosso suporte
Chat com o suporte

On Demand Migration Current - User Guide

About On Demand Migration Before you Start Working with On Demand Migration Account Migration Mailbox Migration OneDrive Migration Microsoft Teams Migration Microsoft 365 Groups Migration SharePoint Migration Public Folders Migration Troubleshooting Finalizing the Migration Appendix A: Working with PowerShell

Provisioning Groups

Before you start, verify that you have discovered all the Microsoft 365 groups without teams. Make sure that all accounts that are members of these groups, have been discovered and matched with accounts in the target tenant. Group members are not added to groups in this step. Use the migration task to migrate group membership.

To provision Microsoft 365 Groups:

  1. Log in to Quest On Demand and choose an organization if you have multiple organizations.
  2. From the navigation pane, click Migration to open the My Projects list.
  3. Create a new project or open an existing project.
  4. Click the Teams tile, or click Open from the Teams tile to open the Teams dashboard.
  5. Click theM365 Groups tab.
  6. Select one or more groups from the Groups List View.
  7. Click Provision. The New Groups Provisioning Task wizard opens.
  8. Step 1: Provision Options

    These options control the actions of the provisioning task if the selected groups already exist in the target tenant. Groups that are not in the target tenant will be automatically provisioned.

    Select and configure the options as described below:

    1. Do not provision the group - The group will be skipped if it exists in the target tenant.
    2. Provision a new group. A suffix will be added to the original name - A new group will be provisioned with the specified suffix appended to the group name
      • New group display name suffix - Specify a suffix to append to the group name. The default suffix is (migrated).
    3. Merge with the existing group - Select this option to set up a mapping between a source and target group with the same name. When members are migrated with the migration task, the accounts that are members of the source group will be added to the same group in the target tenant.
    4. Suppress automatic Group Welcome Message sending - Select the check box to prevent group members from receiving a welcome message.
    5. Multi-geo options: Preferred location - If the target tenant is geo-enabled, select a location to update the geo location of the selected groups in the target tenant. The default is None. See Microsoft 365 Multi-Geo availability for the description of the geo locations in the dropdown list.
  9. Step 2: Notification
    1. Send notification email once the task is completed - select this option to send a notification email when a provisioning task completes.
      • Only in a case of failure - select this option to send the email if the provisioning task fails to complete successfully.
    2. Recipients - enter the email address of the recipients of this email. You can specify multiple recipient email addresses separated by semicolon.
    3. Click Next.
  10. 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.
      • Run now - task runs immediately.
      • Run later - task must be started manually.
      • Schedule - task will be started at a future date and time.
        • Start - enter the start time for the task.
    2. Click Next.
  11. Step 4: Summary
    1. Verify the task specifications as described below:
      • Name - Name of the task. The default name is Provision Groups. You can specify a custom name.
      • Source tenant - Name of the source tenant in this project.
      • Target tenant - Name of the target tenant in this project.
      • Scheduled start - Date and time when the task will start. Now indicates that the task will start immediately.
    2. Click Back to revise or review a previous step or click Finish to complete the task wizard and start the task as scheduled.

The migration task is created. You can track its progress from the Taskstab, view the summary on the Dashboard or monitor alerts and notifications from the Eventstab.

Migrating Groups

Before you start, verify that you have provisioned all the Microsoft 365 groups without teams. See Provisioning Groups for more information. Migration will be skipped for all groups that are not yet provisioned.

To migrate Microsoft 365 Groups:

  1. Log in to Quest On Demand and choose an organization if you have multiple organizations.
  2. From the navigation pane, click Migration to open the My Projects list.
  3. Create a new project or open an existing project.
  4. Click Teams from the project tiles. Click Open from the Teams tile to open the Teams dashboard.
  5. Click theM365 Groups tab.
  6. Select one or more groups from the Groups List View that are provisioned (State = Provisioned)
  7. Click Migrate. The New Groups Migration Task wizard opens.
  8. Step 1: Migration Options

    1. Group mailbox - Read only. Group Mailbox and Calendar will always be migrated. This option cannot be cleared.
    2. Migrate associated collaboration tools - Select this option to migrate associated SharePoint sites including files, One Note and other supported tools.
    3. Planner - Select this option to migrate the group planner.
    4. Group Membership - Select this option to migrate group members. If this option is not selected, group members will not be migrated.
  9. Step 2: Version Options
    1. Choose the migration option for file versions associated with groups selected for migration.
      • Latest version only - This is the default selection. The most recent version of the file will be migrated. All other versions will be ignored.
      • More versions - Additional versions of a file will be migrated based on the options described below. Large version sets take a significantly long time to migrate.
        • Number of versions - The maximum number of version to migrate. The available choices are: 2, 5, 10, 30, 60, 90 and 365. When you specify the number of versions, additional options can be selected.
          • Latest version and preceding versions - The version count includes the latest version and the preceding versions in chronological order restricted to the Size Limit of the latest version. For example, if you choose to migrate 5 versions, then the most recent version and 4 preceding versions will be migrated as long as the most recent version does not exceed the selected size limit specified.
          • Latest version and daily latest from preceding days - The version count includes the latest version and the latest version from each preceding day restricted to the Size Limit of the latest version. For example, if there are many versions of a site and you choose to migrate 5 versions, then the most recent version and the latest version from each of the 4 preceding days will be migrated as long as the most recent version does not exceed the selected size limit specified.
          • Size limit - This setting is available if the Latest version and preceding versions or the Latest version and daily latest from preceding days option is selected. By default, the size limit is 80 MB. You can configure the size limitation by selecting from one of the possible values in the dropdown list. If the size of the latest file version exceeds the selected size limit, the latest version will be migrated and previous versions will be ignored. If the size of the latest file version does not exceed the selected size limit, then the file and its versions will be migrated based on your selection between Latest version and preceding versions or Latest version and daily latest from preceding days.
      • All Versions - The latest version of the file will be migrated, and all previous versions of the file will be migrated if the latest version does not exceed a specified size limit. This option requires significantly more time to migrate all the versions.
        • Size limit - This setting is available if the All Versions option is selected. By default, the size limit is 80 MB. You can configure the size limitation by selecting from one of the possible values in the dropdown list. If the size of the latest file version exceeds the selected size limit, the latest version will be migrated and previous versions will be ignored. If the size of the latest site version does not exceed the selected size limit, then the file and its versions will be migrated.
    2. Click Next.
  10. Step 3: Notification
    1. Send notification email once the task is completed - select this option to send a notification email when a migration task completes.
      • Only in a case of failure - select this option to send the email if the migration task fails to complete successfully.
    2. Recipients - enter the email address of the recipients of this email. You can specify multiple recipient email addresses separated by semicolon.
    3. Click Next.
  11. Step 4: Schedule
    1. Choose from one of three options to schedule the task. The scheduler will be activated only after you complete the task wizard.
      • Run now - task runs immediately.
      • Run later - task must be started manually.
      • Schedule - task will be started at a future date and time.
        • Start - enter the start time for the task.
    2. Click Next.
  12. Step 5: Summary
    1. Verify the task specifications as described below:
      • Name - Name of the task. The default name is Migrate Groups. You can specify a custom name.
      • Source tenant - Name of the source tenant in this project.
      • Target tenant - Name of the target tenant in this project.
      • Scheduled start - Date and time when the task will start. Now indicates that the task will start immediately.
    2. Click Back to revise or review a previous step or click Finish to complete the task wizard and start the task as scheduled.

The migration task is created. You can track its progress from the Taskstab, view the summary on the Dashboard or monitor alerts and notifications from the Eventstab.

NOTE: If a group from the source tenant is merged with a group in the target tenant during the provision process, any new mail items, SharePoint files and Planner items that are generated in the source tenant will appear in the target group.

SharePoint Migration

On Demand Migration offers a fast and convenient way to transfer SharePoint content between Microsoft 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. Account matching /migration should be completed.

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

The Getting Started tile on the 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 Match source sites to the existing target sites (optional)
6 Map source sites to custom target sites using a 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.

What We Migrate

The table below indicates the SharePoint content types that are supported or not supported for migration.

NOTE: You can migrate files with a maximum size of 250 GB. 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.

Microsoft public preview features are not supported.

Objects and content types

>
Object Support Notes
Site collections and sites

Modern experience: top-level sites and sub-sites

Document ID service feature  
Hub settings and associations  
Language settings
 
List templates  
Lists and Libraries  
Navigation elements  
People and groups  
Quick launch  
Regional settings  
SharePoint Designer settings  
Site collection admins  
Site collection feature activation
 
Site collection owner  
Site columns  
Site content types  
Site feature activation Active site feature will be activated on the target during migration but the impact of activating the feature may not be supported on the target.
Site permissions  
Sub-sites  
Themes gallery  
Title, description and logo  
Top navigation  
Web parts gallery  
Site templates

Sites and sub-sites based on unsupported templates are not supported for migration and will be skipped. Unsupported site templates listed below is selective of common and popular templates.

Community site (COMMUNITY#0)  
Classic project site (PROJECTSITE#0)  
Classic team site (STS#0, SPSMSITEHOST#0)  
Document Center (BDR#0)  
Enterprise Wiki (ENTERWIKI#0) Some limitations are applicable
Modern communication site (SITEPAGEPUBLISHING#0)  
Modern Microsoft 365 group site (Group#0). The Group or Team site based on the Group#0 must already exist on the target before the migration is allowed to be performed. The Group or Team sites cannot be set to be cleared before migration.
Modern team site without Microsoft 365 group (STS#3)  
Publishing Portal (BLANKINTERNET#0, BLANKINTERNET#2, CMSPUBLISHING#0) Some limitations are applicable
Point publishing sites (POINTPUBLISHINGHUB#0, POINTPUBLISHINGPERSONAL#0, POINTPUBLISHINGTOPIC#0)  
Project Web App site (PWA#0)  
Search Center (SRCHCEN#0, SRCHCENTERLITE#0, SRCHCENTERLITE#1)  
Content types
Advanced settings  
Column  
Column Order  
Document set settings The Document set setting to define default content is not currently supported
Name and description  
Column types of site, list, and content type
Choice  
Currency  
Date and time  
Hyperlink or picture  
Image  
Multiple lines of text  
Number  
Person or group  
Single line of text  
Yes/No  
List and libraries
Advanced settings
  • Folders
  • Search
  • Offline client availability
  • List experience
  • List attachments
  • List item-level permissions
  • List index non-default views
  • Library Document Templates
 
Audience targeting settings
Only Classic audience targeting is supported for document libraries.
List alerts  
List columns  
List content types
  • New content type button order
  • Default content type
 
List name, description and navigation  
List permissions  
List views  
Pages libraries  
Validation settings  
Version history of documents (optional) Version history transfer means a significant increase in migration time.
Version history of list items (optional)  
Version settings  
List templates
Announcements  
Contacts  
Custom list  
Custom list in data sheet view  
Discussion board  
Document Library  
Events and Calendar  
Issue tracking  
Links  
Picture library  
Promoted links  
Tasks  
Tasks with timeline and hierarchy  
Wiki page library  
Folder
Properties  
Folder permissions  
List item
Alerts on list items  
Attachments  
Authorship properties
  • Created date
  • Created by
  • Last modified data
  • Last modified by
 
Column data  
List item permissions  
Document
Alerts on documents  
Authorship properties
  • Created date
  • Created by
  • Last modified data
  • Last modified by
 
Document ID service feature  
Document permissions  
Document properties  
Site pages
Modern site pages  
Classic pages  
Web Parts

Supported web parts have been verified 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.

Modern web parts partial
Supported web parts
Bing Maps Hero Quick Chart
Button Highlighted content Quick links
Call to action Image Recent documents
Code Snippet Image gallery Site activity
Countdown Timer Kindle instant Preview Sites
Divider Link Spacer
Document Library List Text
Embed List properties Twitter
Events Markdown Weather
File viewer News World Clock
Group Calendar Page Properties YouTube
  People  
     
Unsupported web parts    
Conversations Microsoft Power Apps Organization Chart
Highlights My Feed Planner
Microsoft Forms Office 365 Connectors Power BI
    Saved for Later
     
Classic web parts partial
Supported web parts
About the community Get started with your site Page Viewer
Blog Archives Image Viewer Picture Library Slideshow
Blog Notifications Join Community Project Summary
Blog Tools Library Site Feed
Community Tools List Site Users
Content Editor My Membership What's happening
     
Unsupported web parts    
Business Data category Media and Content category Social Collaboration category
Content Rollup category Search category  
Filters category Server-driven content category  
     
Custom web parts  
Workflow and Forms
Microsoft Forms  
Nintex Classic Forms, Responsive Forms, and workflows  
SharePoint 2010 Workflows SharePoint 2010 workflows are no longer supported in SharePoint Online.
SharePoint 2013 Workflow definitions and subscriptions Migration is attempted on a best effort basis and it is recommended that you must review the workflow definitions after the migration.
Workflow instances Any references to in-progress or completed workflows are not migrated
M365 security and compliance features
Legal Hold  
M365 Compliance Customer Lockbox  
Microsoft Information Protection policies and labels  
Retention Labels  
Power Platform features
Power Apps  
Power Automate (Flow)  
Power Pages  
Power Virtual Agents  
Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação