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

Tenant to Tenant Migration with Domain Transfer Scenario

Client Update Agent now supports tenant to tenant migration with domain transfer. In case you are planning to transfer your custom domain from one tenant to another, perform the following procedure:

  1. Sign in to the https://admin.microsoft.com using an account with the Global administratorrole for the directory. Remove your custom domain from the source tenant as described in Microsoft documentation. Wait until removed domain disappears from the domain list on the source.
  2. Sign in to the https://admin.microsoft.com using an account with the Global administratorrole to add the custom domain to the target tenant as described in Microsoft documentation. You must include .com, .net, or any other top-level extension for this to work properly. Wait until added domain appears in the domain list on the target.
  3. Add your updated DNS information to the domain registrar
  4. After you register your custom domain name, make sure it's valid in Azure AD. The propagation from your domain registrar to Azure AD can be instantaneous or it can take a few days, depending on your domain registrar.
  5. Sign in to the https://admin.microsoft.com using an account with the Global administratorrole to change primary emails of affected users. For more information, see Change a user name and email address.
  6. Re-discover accounts including mailboxes to update all information. Now you can see default email addresses for the source tenant in SourceEmail column on Mailboxes
  7. Run matching task for all affected account pairs to update TargetEmail column. Clear matching operation is not required. No additional licenses will be consumed.
  8. Now you are ready to switch the affected accounts from source to the target. You should provide the custom domain name for forwarding.

In case you are planning to perform Teams migration, this can be done after this scenario is completed. You can use the normal team's migration scenario, no additional steps are required.

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

Quest On Demand migrates the following OneDrive content. Some content migration limitations could appear in unique customer migration scenarios. Such limitations are determined to be unsupported because of platform limitations, and cannot be supported because of legacy support limitations or providing a solution for the limitation is on the product roadmap.

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  
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  

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.

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/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.
  • Unable to migrate a document to a target organization where the document URL will be longer than 400 characters
  • Very large OneDrives (hundreds of thousands of files and/or 500GB or larger) should be divided into two or more OneDrives to improve migration throughput.

 

Dashboard

The On Demand Migration Dashboard tab in the Accounts and User Data workspace provides summary information about migration tasks and events.The OneDrive users tile indicates the number of OneDrive users and the status of their migration.

Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação