Tchater maintenant avec le support
Tchattez avec un ingénieur du support

On Demand Migration Current - User Guide

About On Demand Migration Before You Start Account Migration Mail Migration Public Folders Migration OneDrive Migration SharePoint Migration Microsoft Teams Migration Microsoft 365 Groups Migration Troubleshooting Finalizing the Migration

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

Public Folders Migration

The Public Folders migration workflow consists of the following steps:

# Step
1 Create or open a migration project
2 [optional] Configure connections
3 Discover Public Folders
4 Migrate Public Folders
5 Monitor the progress and track issues

What We Migrate

All types of Public Folders (appointment, contact, journal, mail, note, task, and so on) can be migrated in case they are supported in the target tenant.

Please consider the following migration specifics:

  • If the public folder with the same path already exists on the target, the source public folder will not be migrated. Check the Events tab.
  • The first processed mailbox will be set as a primary for a public folder. Other mailboxes will be set as secondary public folder mailboxes.
  • Send As and Send on Behalf properties will only be transferred for mail-enabled Public Folders.
  • Read and unread status is not migrated.

Public Folders Migration Dashboard

From this dashboard you can:

  • Keep track of your location within project and quickly return to the main project dashboard using breadcrumbs on the top of the pane
  • View list of discovered public folders with source and target paths, and last events related to the public folder
  • Quickly navigate to the event lists
  • Quickly navigate to the tasks list
  • Create discovery tasks and public folder migration tasks
  • Export feature data into comma-separated file
  • Temporarily remove public folders from the migration project
  • Search public folder
  • Filter public folder by status, by matching state, or by mail settings
  • Delete public folder
Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation