立即与支持人员聊天
与支持团队交流

On Demand Migration Current - User Guide

About On Demand Migration 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: Using PowerShell

Migrating OneDrive

You can migrate OneDrive for discovered and matched accounts with large selection of migration options. These options give you control over the scope of files migrated, permissions, licensing and version management

Recommendation

The OnDemand migration service for OneDrive attempts to provision OneDrive for accounts being migrated if the OneDrive has not been provisioned. You can manually provision the OneDrive before a migration as described below:

  1. Provision OneDrive for accounts in the target tenant that don't have a OneDrive provisioned.
  2. OneDrive must be provisioned at least 24 hours before starting a migration.

In this topic:

 

Starting a OneDrive Migration Task

  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 OneDrive tile, or click Open from the OneDrive tile to open the Accounts and User Data dashboard.
  5. Open the OneDrive tab and verify that the List View has displays the list of user Accounts. See Discovering Accountsif the list is empty.
  6. Select one or more accounts for which you migrate the OneDrive contents. This enables the Migrate OneDrive menu option.

    NOTE: To migrate OneDrive for user accounts in a collection

    1. Select the collection from the dropdown menu in the top right corner labeled Select Collection.
    2. Select the accounts to migrate from the collection. To check all accounts, select the check box in the list header.
    3. Proceed to the next step.
  7. Click Migrate OneDrive to open the New OneDrive Migration Task wizard and follow the steps described below. The New OneDrive Migration Task wizard helps you configure the migration options and settings for OneDrive for Business. The default settings are optimized for fast migration. You can change the options and settings to address specific migration needs.

  8. Step 1: Migration Options

    1. Choose a migration action
      • Overwrite target files - Select this option to overwrite the file in the target tenant if it was previously migrated.
      • Skip if the target file is the same version or newer - This is the default selection. When this option is selected, the migration service will not migrate a file if the file already exists on the target tenant and has the same or newer version than the file in the source tenant. Select this option to speed up the migration process especially if you are starting multiple migration tasks.
      • Overwrite if the target file is older or make a copy if the target file is newer - Select this option to overwrite the file in the target tenant if it was previously migrated and the file in the target is an older version, or create a copy of the source file if it was previously migrated and the file in the target is a newer version. When a copy is created in the target it will be renamed. For example, Sample.txt will be renamed to Sample_migration_copy.txt. If the file versions in the source and target are the same, it is skipped.

        NOTE: Do not rename a previously migrated file or folder before the migration completes. If you rename a previously migrated file or folder before the migration completes, it may be unexpectedly overwritten even though you select the second or third option. New files or folders are not impacted. The migration service compares both file versions and modified date to determine older or newer files.

    2. [Optional] Files are migrated to the root folder. You can specify an alternate target migration folder
      • Relative folder path - specify the relative path to a folder where the OneDrive contents will be migrated.
    3. Click Next.
  9. Step 2: Version Options

    1. Specify the scope of file migration

      Each OneDrive file has its own version history and each change to a file is saved with a new version. Select from the following migration options to determine how file versions should be migrated:

      NOTE: Only the latest version of frequently updated files such as outlook PST files, database files and log files will be migrated

      • 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 file 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 file version does not exceed the selected size limit, then the file and its versions will be migrated.
    2. Click Next.
  10. Step 3: Attribute Options

    This step determines how file and folder attributes are migrated and managed by the migration service.

    1. Account display: Select which account will be displayed in the Created by and Modified by properties of migrated content:
      • System Account - This is the default selection. The Created by and Modified by properties of the migrated file or folder is displayed as System Account.
      • Matching target account - The Created by and Modified by properties of the migrated file or folder is displayed as the target account that was matched with the source account. If the target account cannot be found, the migration service records a warning event and the properties of the migrated file or folder is displayed as System Account.
    2. Permission migration: Select how the sharing permissions will be transferred to the target users:
      • Do not migrate permissions - This is the default selection. Permissions associated with the file being migrated will be ignored.
      • Update permissions for migrated content - The permissions of files that are migrated will be updated. Some files may be skipped if you selected the Skip if the target file is the same version or newer in the previous step. Sharing Links are not migrated unless Convert Sharing Links permissions to direct permissions is selected.
      • Update permissions for all content - All file or folder permissions in the target tenant will be updated whether or not they were migrated if the corresponding file or folder is present in the source tenant. Sharing Links are not migrated unless Convert Sharing Links permissions to direct permissions is selected.
    3. Auto rerun: Select whether to migrate permissions with the Auto rerun task to reduce the task load
      • Migrate permissions with the Auto rerun task - the permissions will be migrated with the Auto rerun task after the migration completes.
    4. Permission conversion
      • Convert Sharing Links permissions to direct permissions - migration is slower with this option select. Select this option to convert Sharing Links permissions of files or folders in the source tenant to direct permissions in the target tenant. Only shared links that were activated by the users or group members (the user or group member clicked on the link to access the file or folder) in the source tenant will be migrated and converted to direct permissions. Users or group members who did not activate a shared link in the source tenant will not get the direct permissions in the target tenant and must re-request permissions from the owner when they access the file or folder in the target tenant.

      NOTE:

      1. Users can access their shared content through the Shared With Me view in OneDrive. Some restrictions apply.
      2. Some sharing permissions are not converted if the user has shared the file or folder with more than 30 users. Only 30 users will receive direct permissions from the Sharing Links, while others will not be processed due to a Microsoft limitation.
      3. If a Sharing Link permission is removed on the source file or folder after it is migrated, the links to this file or folder are still visible in the Shared with me and Shared by me views in OneDrive, but the file or folder cannot be accessed.
      4. Group permissions are not displayed in the Shared with me view because Microsoft currently does not support this functionality.
      5. For shared folders, only the top level folder is displayed in the folder tree.
      6. For files and folders that do not exist in target tenant before migration the source permission will always be used.
      7. For files and folders that exist in the target tenant before a migration, the following example describes how file sharing permissions will be managed. The rules are the same for internal and external users as permission holders, or groups (Microsoft 365 group or security group) as permission holders.

        For files

        If Overwrite target files for selected migration is selected, the source file sharing permission will be used.

        If Skip if the target file is the same version or newer is selected, the target file sharing permission will be used.

        For folders

        If either Overwrite target files for selected migration or Skip if the target file is the same version or newer option is selected, the target sharing permission will be used as a base. Any addition of permissions in the source will be added onto the target.

    5. Click Next
  11. Step 4: Licensing Plan

    1. Set license at the target - select this check box to assign a selected license to migrated mailbox accounts in the target tenant. Clear the check box to skip license assignments for migrated mailbox accounts.
    2. Select the licensing plan - this dropdown list appears if the Set license at target check box is checked. Select the licensing plan from the dropdown list that you want to assign to migrated mailboxes.
    3. Specify how the selected licensing plan will be assigned to the target accounts:
      • Assign the plan to accounts without Exchange Online option. Licensed users will retain the existing plans - Retain the existing licenses and assign the selected plan only to unlicensed accounts (default). Licensed users will retain the existing plans.
      • Assign the plan to all accounts. Licensed users will be switched to the selected plan - Replace all license assignments with the licenses from the selected plan. Licensed users will be switched to the selected plan.

      NOTE:

      • OneDrive for Business that have not been licensed on the source tenant will retain the unlicensed status in the target tenant.
      • Selected licensing option is only applicable to OneDrive migration. It does not affect the licensing plans picked for Mail Migration.

    4. Click Next.
  12. Step 5: Filter Items

    1. Set up filters as described below:
      • All items - select this option to ignore filters. This is the default option and all OneDrive Content for the selected account will be migrated.
      • All items that were added or modified since the last successful migration - select this option to migrate items that were added or modified in the source since the last successful migration. The migration service will check the Last Successful Run attribute and migrate every item added or modified in the source. If the OneDrive has not been successfully migrated before, all items will be migrated.
      • Items to exclude - select this filter option to exclude files and folders from the migration. Then specify the filter criteria. Items are excluded if any of the following criteria are fulfilled:
        • Exclude specific folders- provide a semicolon-separated list of relative paths to folders that you want to skip. You can use slash or backslash. If it is convenient for you, use spaces after semicolons, e.g., filteredfolder; somefolder/subfolder
        • Exclude specific file types - provide a semicolon-separated list of file extensions. The values are not case sensitive. You can use spaces and dots, e.g., .exe; dll; bat; doc; pdf
        • Exclude files created
          • select Before from the dropdown. Then click in the date field that appears to open the date picker and select a date. Files created before this date will not be migrated.
          • select After from the dropdown and then click in the date field that appears to open the date picker and select a date. Files created after this date will not be migrated.
        • Exclude files modified
          • select Before from the dropdown. Then click in the date field that appears to open the date picker and select a date. Files modified before this date will not be migrated.
          • select After from the dropdown. Then click in the date field that appears to open the date picker and select a date. Files modified after this date will not be migrated.
        • Exclude files bigger than (MB) - enter a numeric value. The maximum value is 1000 MB. Only integer values are supported.
      • Items to include - select this filter option to include files and folders from the migration. Then specify at least one filter criteria. Items are included if any of the following criteria are fulfilled:
        • Include specific folders- provide a semicolon-separated list of relative paths to folders that you want to include. You can use slash or backslash. If it is convenient for you, use spaces after semicolons, e.g., filteredfolder; somefolder/subfolder
        • Include specific file types - provide a semicolon-separated list of file extensions. The values are not case sensitive. You can use spaces and dots, e.g., .exe; dll; BAT
        • Include files created
          • select Before from the dropdown. Then click in the date field that appears to open the date picker and select a date. Files created before this date will be migrated.
          • select After from the dropdown. Then click in the date field that appears to open the date picker and select a date. Files created after this date will be migrated.
        • Include files modified
          • select Before from the dropdown. Then click in the date field that appears to open the date picker and select a date. Files modified before this date will be migrated.
          • select After from the dropdown. Then click in the date field that appears to open the date picker and select a date. Files modified after this date will be migrated.
        • Include files bigger than (MB) - enter a numeric value. The maximum value is 1000 MB. Only integer values are supported.
    2. Click Next.
  13. Step 6: Notification
    1. Send notification email once the task is completed - select this option to send a notification email when a discovery task completes.
      • Only in a case of failure - Select this option to send the email if the discovery 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.
  14. Step 7: 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 entered in the corresponding calendar field.
      • Priority - select a priority from the dropdown for the objects scheduled for migration with this task . Values are: Highest, High, Medium, Low and Lowest. The default priority is Medium. If the system is busy, the objects are queued (Migration state = Queued). When the system accepts new migration work, objects are taken from the queue based on the assigned priority and age in the queue.
    2. Click Next.
  15. Step 8: Auto rerun

    1. Auto re-run task if target user(s) are missing any files or folders - Select this option to rerun the migration task for files or folders that failed to migrate on the first run. The migration task will auto rerun once only. Failure of the files to migrate the first time could be because of intermittent network issues or throttling. We recommend that this setting remains selected.

      This setting is enabled but read-only if the Migrate permissions in the Auto rerun task option is selected in Step 2: Attribute Options. Auto re-run is not available if an alternate migration location has been specified in Step 1 or item filters have been configured in Step 5.

      The migration service will issue an event warning for all files that fail to migrate. You can also check the batches for how many files failed to migrate.

    2. Click Next.
  16. Step 9: Reporting

    Select the check box Generate detailed report of migration errors to generate a migration error report when you run the OneDrive Migration Task.

    You can download the report from the Reports tab of the Accounts and User Data migration workspace by clicking the Download link in the Error Log column. If there are no migration errors, a download link is not available. Error reports are retained for 30 days. After 30 days the download link is replaced with the label Expired and you can no longer download the report. For more information about error reports, see Reports.

  17. Step 10: Summary

    1. Verify the task specifications as described below:
      • Name - name of the task. You can specify a custom name. The default name is OneDrive Migration Task.
      • Source tenant - name of the tenant where the statistics will be collected.
      • 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.
      • Priority - the priority of this task.
      • File migration - migration action when a file is migrated.
      • Versions to migrate - options to migrate the version history.
      • Account to display - account name that will be displayed in the Created by and Modified by properties of migrated content:
      • Alternative migration location - default is the root folder or an alternate target migration folder
      • Sharing permissions - how sharing permissions will be transferred to the target users.
      • Auto-rerun - option to rerun the migration task for files or folders that failed to migrate on the first run.
      • Reporting - option to collect and retain data for report generation.
    2. Click Back to change configurations if necessary or click Finish to save and start the task as scheduled.

 

Tracking the progress of the migration task

While the OneDrive Migration Task is running, click Assessment to track the progress of the migration task.

The following summary reports are available and described below.

OneDrive Users

The Users figure at the top of the OneDrive users pane reports on the total number of OneDrive users to migrate.

Account migration and matching reports on the number of OneDrive users matched and not matched.

OneDrive provision in target reports on the number of provisioned users.

Migration Progress

The migration progress pane reports on the status of the migration of OneDrive users. It is updated in real time.

Statistic Description
Last Run Status This data relates to the Last Run Status column on the List View tab. Show data from the last run status: new, in progress, completed, failed, stopped.

Progress of Started Users

Started Users = The users listed on the List View tab with Migration Progress % greater than zero.

The bar chart shows the Migration Progress % for users. It shows how many users have Migration Progress % at fewer than 50%, 50% to 95%, 95% to 99%, and 100%. For example, if the diagram shows 63 users at 100% then 63 users have Migration Progress % value of 100%.

How is Migration Progress % calculated? It is calculated as a ratio of the number of target items to the number of source items. If 10 items have migrated to the target and there are 100 items to be migrated on the source then the ratio for that user Migration Progress % is 10%.

Average % for started users This is the average Migration Progress % value for users on the List View.

 

Migration Statistics

The migration statistics pane reports on statistics recorded for the last 14 days.

  • Total migration file size for entire project (last 14 days)
  • Total migration file count for entire project (last 14 days)

Dependent on the scope of the file migration the content of OneDrive storage is transferred in batches that can be submitted for processing to OneDrive at the same time to be processed concurrently, it can take a while for OneDrive to complete processing of submitted batches. Refer also to the Events tab while the migration task is running.

 

Viewing the report

  1. Open the Tasks tab.
  2. Select the OneDrive Reporting Task (or your custom name) that you want to review.
  3. In the task details pane that opens click Events (number).
  4. Select the event with the description: Link to download the report is in the Details pane. Report link is active for 1 hour.
  5. Click the report link in the details pane.

  6. You can rerun the OneDrive Reporting Task after 1 hour to generate another report, and follow the same steps described here to view the report.

Assessment

After you start a OneDrive migration, open the Assessment view to see the reports described below.

NOTE: Click the Assessment button again to refresh the reports during a migration.

  • OneDrive Users

    • Number of users
    • Number of user accounts that are matched or unmatched
    • Number of OneDrive accounts provisioned or not provisioned in the target tenant
  • Migration Progress

    • Last Run Status - number of user accounts in state of the migration process
    • Progress of Started Users (Source/Target Items Ratio)
    • Average % for Started Users
  • Migration Statistics

    • Current Migrating Users - number of users that are currently migrating.
    • Scope - indicates the performance of the migration within the last 14 days
    • Total Migration File Size - total files size packaged or migrated within the last 14 days
      • Packaged - total file size submitted for migration
      • Migrated - total file size actually migrated
    • Total Migration File Count - total files packaged or migrated within the last 14 days
      • Packaged - total number of files submitted for migration
      • Migrated - total number of files actually migrated
  • File Size (per hour) - performance chart that indicates the file size packaged and migrated per hour. Data is displayed for the last 14 days.

  • File Count (per hour) - performance chart that indicates the number of files packaged and migrated per hour. Data is displayed for the last 14 days.

  • Average concurrent migrating users (per hour) - indicates the average number of users being concurrently migrated per hour. The optimization is managed seamlessly by the migration service to avoid bandwidth or throttling issues.

Microsoft Teams Migration

On Demand Migration for Teams securely migrates Microsoft Teams and associated Microsoft 365 Groups across Microsoft 365 tenants. You can also use this dashboard for migration of content for Microsoft 365 Groups without Teams functionality. (Microsoft 365 Groups Migration). Microsoft Teams migration requires additional licensing.

Basic Microsoft Teams migration workflow consists of the following steps:

# Step
1 Create a migration project (created automatically with New Migration UI)
2 Grant necessary permissions in case these permissions are not already granted (Prerequisites)

IMPORTANT: It is not recommended to use existing user accounts as source and target temporary Migration Manager accounts, because it is recommended to remove them for safety reasons after the migration will be completed. These accounts can be removed from teams as described in Finalizing the Migration.

3 Discover teams/groups on the source tenant

On this step you can see names, suggested for target teams. In case you need some changes use manual mapping as described below. There are no provision on the target on this step.

TIP: Organize teams in collections to streamline the provision and migration process

4 Export teams mapping to CSV file
5 Map teams manually using exported CSV file

You can use manual mapping to migrate source team to the target team with another name. If the channel do not exist, it will be provisioned. Also you can use manual mapping to merge several source teams to one target team.

6 Create Microsoft 365 Groups and Provision teams on the target tenant. Target teams will be owned by the target temporary Migration Manager account that is used to perform the provisioning.
  • The temporary Migration Manager account in the source tenant will be added to all source teams as a member, and source private channels as an owner.
  • The temporary Migration Manager account in the target tenant will be added to all target teams and Microsoft 365 Groups as a member and an owner, and target private channels as an owner

These accounts can be removed from teams as described in Finalizing the Migration.

7 Migrate teams

Migrate / merge all conversations (including inline content) from the source to target channels.

  • Target temporary Migration Manager account will own all private channels migrated to the target.
8 remigrate teams to incorporate supported changes made after the migration task (step 7) was started.
9 Monitor the progress and track issues

What We Migrate

Migration limitations indicated below may not be an exhaustive list of limitations as some may appear in unique customer migration scenarios, or arise due to platform or legacy support restrictions. In some cases, a solution to a limitation may already be on the product roadmap.

In this topic:

 

Objects and content types
Object Support Notes
Announcements partial Customized background picture for announcements are not migrated
Applications partial Only Word, Excel, PowerPoint, OneNote and List tab applications linked to files in the same channel are supported. If you rename a tab in the source team and then re-migrate, the renamed tab will be migrated. The target will then have two tabs, one with the old name and one with the new name.

Whiteboard tabs are migrated if the Whiteboard files, in the OneDrive of the Whiteboard creator, is pre-imgrated to the target tenant. At least one team owner must have permission to the whiteboard file in source tenant. Whiteboard tabs will be migrated as Weblink tabs in target.

Applications including Shifts for schedule management  
Archived team Archived teams will first be migrated to the target tenant as active teams. Then they will be archived in the target tenant. Archived team can only be migrated once and remigrating archived teams is not supported.
Attached images, media files, documents partial Preview icons are not migrated.
Authorship partial Authorship in messages is migrated as a string with author name and creation date. File authorship is supported.
Bots  
Calls and devices Contacts, contact groups, call history, voicemail, and custom setup are not migrated. Devices and device setup are not migrated.
Chats Images, media files and documents referenced in one-on-one or group chats are stored in your OneDrive for Business folder. They must be migrated using the On Demand Migration for OneDrive service, before you migrate the chats. File links in team chats will not work after chat migration if the files are moved to another folder in the source tenant.

Files that are linked to the private chats and meetings are migrated but do no display in the Files tab of private chats and meetings. In the source tenant a member removed from a chat can still see the history of the chat in the source. In the target tenant, members cannot see the history of chats they have been removed from.

Users deleted on the tenant are not migrated, so do not appear as members of a chat on the target. Deleted users remain visible as members of a chat on the source. One-to-one chats, where one of the users is deleted, are migrated for the user that is still a member of the tenant.

If external users are added to target chats during migration, the external users cannot access the Archived chat file since no permissions are granted to the external users.

If a domain move is done after a chat migration, the Conversation Tabs in migrated chats will not work because the URL of those tabs remain mapped to the original target domain.

Private one-to-one chats are migrated as group chats. All the messages in the migrated chats are posted by the temporary Migration Manager.

Private one-to-one chats with a Skype user are not migrated. The Microsoft Graph API List chat messages do not support querying messages of that type.

Private one-to-one chats initiated by an external user (user from another tenant) are not migrated. Private one-to-one chats not initiated by an external user are migrated, and in the title the external user’s real name is replaced with the text "External user".

Loop components in chats are not supported.

Emoji is not supported when archiving chats.

Errors in chat migration will not be linked to a particular user since chat always happens among multiple users. As a result, those errors will not be visible in Exported Error Logs since the logs are exported per user.

Chat application tabs are not migrated.

Code snippets  
Conversations The target tenant's temporary Migration Manager account is displayed as the owner of all migrated messages on the target: The original owner and creation time of a message are displayed in the first line of the message starting with "Originally posted by...".

Individual messages larger than 4 MB will not migrate. Messages containing several inline messages can exceed 4MB. The chat will migrate without the large messages. An error will display in the On Demand Migration for Teams Events tab of the form: Request failed with RequestEntityTooLarge status code (Request Entity Too Large).

Custom tags for teams GCC tenants do not support tags.
Custom website tab  
E-mail attachments  
Emoji, GIF, Sticker, Praise, memes  
File preview partial Preview icons of files attached to a post are not migrated. The file is migrated as a link.
Formatted text  
Guest accounts and conversations  
Images posted inline from buffer  
Inbox folder and Calendar from the group mailbox associated with a team  
Link preview of public images Preview icons are not migrated. Only the link is migrated.
Link preview of public sites partial Preview icons are not migrated. Only the link is migrated.
Lists partial Lists must be created in the same SharePoint site used by the team or Private Channel. You must select the Standard and Customized (All SharePoint Content) option in the Migration Options step of the New Teams Migration Task to allow the migration of Lists and their content.
Meeting conversations Conversations are migrated as private chats, but cannot be written to the original Teams meeting. Conversations in a channel stay in the channel rather than a private chat, and are migrated to the target channel with a Teams migration task.
Meeting Notes in private meetings  

Meeting recordings

partial

Recordings of scheduled meetings in a team channel, stored in SharePoint or OneDrive, are migrated.

  • Meeting recordings stored in Microsoft Stream (Classic) are not migrated; the link to the recording on the source team channel is retained.
  • On Demand does not support meeting recordings in a group chat. Recordings in group chats and one-to-one chats cannot be migrated with the On Demand Migration for Teams service. Since the recording file is stored in the chat organizer's OneDrive account, you can use the On Demand Migration for OneDrive service to migrate recordings.
  • On Demand does not support meeting recordings for "Meet now" meetings.
@mentions:
  • Users (includes @Everyone)
  • Channels
  • Teams
All @mentions from the source will be created as plain text with blue color in the target tenant to avoid notification to end users during migration.
OneNote partial When the team name in source tenant is different from the one in target tenant, a blank default team’s notebook (with the target team name) will be created in target tenant. The original default team’s notebook (with the source team name) will be migrated correctly by Team’s migration. This results in two default team’s notebook in target.

OneNote tabs migration fails if the team contains a large number of items (folders or files, some of which could be OneNote entities such as notebooks, sections or section groups) and the following error message is reported: Request failed with Forbidden status code (Forbidden). { "error": { "code": "10026", "message": "One or more of the document libraries on the user or group’s OneDrive contains more than 20,000 OneNote items (notebooks, sections, section groups). Please try again later."....Workaround: Before proceeding with migration consider the following Microsoft recommendations to avoid the problem: https://docs.microsoft.com/en-us/archive/blogs/onenotedev/onenote-api-calls-fail-with-a-large-number-of-items-in-a-sharepoint-document-library

OneDrive Shared Library partial OneDrive Shared Library must be created and associated with a team in the same SharePoint site. You must select the Standard and Customized (All SharePoint Content) option in the Migration Options step of the New Teams Migration Task to allow the migration of OneDrive Shared Library and its content.
OneDrive Sharing Links partial Only shared links that were activated by the users or group members (the user or group member clicked on the link to access the file or folder) in the source tenant will be migrated and converted to direct permissions. Users or group members who did not activate a shared link in the source tenant will not get the direct permissions in the target tenant and must re-request permissions from the owner when they access the file or folder in the target tenant. Use the Convert Sharing Links permissions to direct permissions option in the Attribute Options step of the New OneDrive Migration Task to migrate sharing links.
Planner partial Planner Tab, Buckets, Tasks and Comments. If there are more than 400 Planner tasks in a bucket then On Demand migrates the first 400 tasks only. When migrating Planner tasks, assignees in target tasks will receive a notification after migration.

The author of auto-generated comments like 'New task ... created' in migrated tasks will always show as the login user. This is a limitation of Microsoft Graph API when creating tasks in the target tenant with application permission.

Private channels See Channel settings subsection below.
Reaction  
Rich card attachments  
Self-Chat  
Shared channels See Channel settings subsection below.
SharePoint document libraries (Files)  
Standard channels See Channel settings subsection below.
Team owners and team members Only for Microsoft 365 Groups that are migrated / matched. Teams and groups with dynamic membership can be migrated but cannot be merged.

The memberships is not updated in Teams immediately after membership migration. It takes a while before Microsoft synchronizes memberships between groups and Teams. Workaround: Wait for membership synchronization.

Team picture  
Team settings partial Target team settings are not updated if you re-run the provisioning task.

Allow members to upload custom apps and Team code settings are not migrated.

Timestamps  
Wiki sections and pages  
Files uploaded from mobile application 
Media files  
Voice recordings  
Documents  
Channels and Channel Settings
General settings Channel isFavoriteByDefault property migration is not supported. Workaround: Enable Automatically show this channel in everyone’s channel listoption for the channel manually in your Teams client.
Standard channels  
Private channels The Teams client will not display the updates immediately. It may take up to 24 hours before the changes are reflected due to Microsoft limitations. Private channel members not visible in the Teams application unless you explicitly search for a member.
Shared channel Shared Channels can only be provisioned in the original team where the channel was created. Shared Channel membership is not migrated.
Group Settings
Allow external senders to email this group General
Send copies of group conversations and events to group members General
Hide from my organization's global address list General
Others
Microsoft public preview In general, Microsoft public preview features are not supported in production migrations. These features may also take additional time to be fully developed and tested before being released to production.

M365 security and compliance features for Teams

  • Legal Hold
  • Retention Labels
  • Microsoft Information Protection policies and labels
  • M365 Compliance Customer Lockbox
 

Power Platform features for Teams

  • Power Apps
  • Power Pages
  • Power Automate (Flow)
  • Power Virtual Agents
 
Migration from an Education tenant to an Education tenant

Teams migration from one education tenant (Microsoft 365 for Education) to another is partially supported. The following team types and supported content can be migrated:

  • Standard Team
  • Class Team
  • PLC Team
  • Staff Team
Limitations
  • Provisioning of public teams is not supported for migration scenarios from one education tenant to another. Only private teams can be provisioned for these scenarios.
  • When using Microsoft Teams for Education, use On Demand Migration for Teams to discover and migrate the EDU group. If you use On Demand Account Migration to discover and migrate the EDU group, then provisioning the EDU teams will fail with a “Request failed with BadRequest status code (Bad Request)” event error.
  • During provisioning, the teams with the same type will be created in the target tenant. Provisioning of public teams is not supported for migration scenarios from one education tenant to another.
  • Assignment app, personal OneNote notebook linked to a Teams channel and the OneNote tab linked to another team are currently not supported. Links to files in migrated messages are not supported in case these links point to files located outside the default SharePoint URL. These links are missing in the target.

All other Education content is not supported for migration.

Migration from a Commercial tenant to a GCC High tenant

The table below lists the content types in Microsoft Teams that are available for migration from a Commercial tenant to a GCC High tenant with the On Demand Migration for Teams service.

Content type Availability in
GCC High tenant
Migration support
Announcements
Applications
Applications including shifts for schedule management
Associated SharePoint document libraries (files)
Attached images, media files, documents
Authorship
Bots
Calendars
Chats
Code snippets
Conversations
Custom tags for teams
Custom website tab
Email attachments
Emoji, Teams GIFs, memes
Formatted text
Group mailbox associated with team
Guest accounts and conversations
Images posted inline from buffer
Link preview of public images Partial. Icon is not migrated.
Link preview of public sites Partial. Icon is not migrated.
Meeting conversations
Mentions
  • Users
  • Channels
  • Teams
OneNote
Planner (Planner Tab, Buckets, Tasks and Comments)
Private channels
Public channels
Team owners and team members (Creation of Microsoft 365 Groups)
Team picture
Timestamps

Wiki sections and pages

NOTE: Starting January 2024, neither Wiki tabs nor the Wiki app will be accessible through Teams. Users will no longer have the ability to export their wikis. However, users will still be able to download their wiki files from SharePoint. For more information, see https://support.microsoft.com/en-us/office/export-a-wiki-to-a-onenote-notebook-in-microsoft-teams-8cd8ab0c-2314-42b0-a1d0-5c6c4c5e1547

相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级