Chat now with support
Chat with Support

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 Power BI Migration Troubleshooting Finalizing the Migration Appendix A: Using PowerShell Appendix B: How Queuing Works

Switching Applications in a Domain Move Scenario

When performing a tenant-to-tenant migration that includes a domain move, On Demand Migration needs to refresh the source and target usernames and email addresses after the domain move to ensure that the Desktop Update Agent works as expected. To use the Desktop Update Agent after moving a domain from one tenant to another, perform the following procedure:

  1. Complete the Domain Move.
  2. Confirm that the updated usernames and email addresses are shown in the source and target tenants.
  3. Re-run the New Account Discovery Task wizard to refresh source usernames and email addresses.
  4. Re-run the New Account Matching Task wizard to refresh target usernames and email addresses.
  5. Run the New Switch Applications Task wizard. Select the options to Skip mailbox state validation and Skip OneDrive state validation if the account migration states were reset to Matched. For more information, see Configuring the Switch Applications Task in the Desktop Update Agent User Guide.

NOTE: If you run the New Switch Applications Task before the domain move is complete, you will not need to re-run the task since the Desktop Update Agent will check the source and target user information at the time the end-user runs the tool.

 

OneDrive Migration

When the user accounts are matched or migrated, you can transfer the content of their OneDrive for Business stores to the target tenant.

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.

Quest On Demand migrates the following OneDrive components:

Objects and content types

>
Object Support Notes
Document

Document size can be up to 100 GB.

Authorship properties:
  • Created Date
  • Created by
  • Last Modified Date
  • Last Modified By
✔  
Document properties ✔  
Document permissions ✔  
Versions and Version History ✔  
Folder
Properties ✔  
Folder permissions ✔  
Permissions
Direct Sharing Permissions ✔ Permissions for:
  • Internal Users
  • Groups
  • Guest (External) Users
Custom level permissions ✔  
Link Sharing Permissions ✔ Permissions for:
  • Internal Users
  • Groups
  • Guest (External) Users
M365 security and compliance features
Legal Hold ✖  
Retention Labels ✖  
Microsoft Information Protection policies and labels ✖  
M365 Compliance Customer Lockbox ✖  
Power Platform features
Power Apps ✖  
Power Pages ✖  
Power Automate (Flow) ✖  
Power Virtual Agents ✖  
Others
Microsoft public preview features ✖ In general, Microsoft public preview features are not supported in production migrations. These features may also take additional time to fully develop and test for release to production.
Personal SharePoint Lists ✖  
SharePoint subsites, lists and libraries added to a user's OneDrive ✖  
Whiteboard ✔ The folder that contains the Whiteboard files is migrated. If you plan to migrated Teams, you must pre-migrate the Whiteboard files created by the Whiteboard creator.

Limitations

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

Considerations

Before starting the OneDrive migration consider the following:

  • When active or expired Sharing Links are migrated, existing permissions are converted to direct permissions in the target tenant.
  • Migrating Sharing Link permissions for external users requires the external user be an Azure Active Directory guest.
  • Migrating Authors and Editors will only map to the Primary SMTP Address. Multiple SMTP addresses are not currently supported.
  • Migrating a OneDrive user Recycle Bin is not supported.
  • Document with URLs longer than 400 characters cannot be migrated to a target tenant.
  • Very large OneDrives with hundreds of thousands of files or files that are 500 GB or larger, should be divided into two or more OneDrives to improve migration throughput.

Prerequisites

  • You must match or migrate user accounts in the migration project to ensure that membership, content ownership, and permissions are processed correctly.
  • The target tenant should has the fully configured OneDrive feature with a valid license plan. Licenses can be automatically assigned to the target users during the migration.
  • Tenant administrator consents are granted for source and target tenants .The following consents should be granted for OneDrive migration feature:
    • Migration - Basic
    • Migration - SharePoint

    If tenant administrator consents are not granted or have expired, account discovery will be deactivated and you will be unable to continue.

  • Tenant administrator credentials must also be provided for both tenants in the Configure Connections dialog.

 

Prerequisites

  • You must match all accounts in the project to ensure that membership and content ownership are processed correctly.
  • The following admin consents should be granted for SharePoint migration:
    • Migration - Basic
    • Migration - OneDrive - Minimal (for source)
    • Migration - OneDrive - Full (for source and target)
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating