About On Demand Migration
Before You Start
Required Permissions
Signing up for Quest On Demand
Organizations and Regions
Adding a Tenant
Upgrading Throttling Policies
Working with On Demand Migration
Test and Pilot Migrations
Project Management
Project Dashboard
Task Management
Event Management
Searching
Filtering
Starting Migration Project
Configuring Connections
Sharing Availability Information
Collecting Account Information
Pre-Migration Assessment
Account Migration
Account Migration Project Dashboard
Granular Permissions
Using Collections
Exporting Mapping for Selected Objects
Matching Accounts
Migrating Accounts
Guest User Account Migration Considerations
Hybrid Account Migration
Integration with Migration Manager for AD
Deploying Migration Manager for Active Directory
Configuring Hybrid
Installing Hybrid Migration Service
Matching Hybrid Accounts
Migrating Hybrid Accounts
Domain Coexistence
Mail Migration
Deploying Client Update Agent
Migrating Mailboxes
Switching Clients
Mail Forwarding Scenarios
Tenant to Tenant Migration with Domain Transfer Scenario
OneDrive Migration
Resource Processing
Public Folders Migration
What We Migrate: Public Folders Migration
Public Folders Migration Dashboard
Prerequisites
Configuring Connections for Public Folders Migration
Discovering Public Folders
Removing Public Folders from the Migration Project
Migrating Public Folders
SharePoint Migration
What We Migrate
SharePoint Migration Considerations
SharePoint Migration Dashboard
Prerequisites
Discovering Sites
Setting Migration Defaults
Setting Custom SharePoint Admin Center URLs
Matching Sites
Exporting Site Collection Mapping
Removing Sites from the Migration Project
Migrating sites
Microsoft Teams Migration
What We Migrate: Microsoft Teams Migration
Teams Migration Interface Walkthrough
Prerequisites
Discovering Teams
Using Collections for Teams
Exporting Mapping for Teams
Using Manual Mapping for Teams
Pre-Migration Assessment for Teams
Provisioning Teams for Target Tenant
Migrating Microsoft Teams
Migrating Microsoft Teams Chats
Content Migration for Office 365 Groups
What We Migrate for Groups
Prerequisites
Enumerating Groups
Provisioning Groups
Migrating Groups and Associated Content
Troubleshooting
Finalizing the Migration
Configuring Notifications for Mailbox Owners
On Demand Migration allows to configure notification messages that appear after successful switch in:
- in new target mailboxes and / or in original source mailboxes (used now) in case you have selected Source to target mail forwarding direction on Mail Flow page
- in "new" (destination) source mailboxes and / or in original target mailboxes (used now) in case you selected Target to source mail forwarding direction on Mail Flow page
The following can be configured :
- Sender's email address - specifies email to replay (optional). In case no replay needed you can skip this field. In this case no email address will be displayed in the message.
- Send from: - specifies sender that will be displayed to user
- Subject: - specifies message subject
- Message: - specifies message text (plain text only)
Mail Forwarding Scenarios
To support the customer preferences related to mail forwarding, the following behavior is now supported for mail migration task in case forwarding is not set using On Demand Migration (Mail Flow column is empty) and for mailbox switch (standard and reverse scenarios) tasks:
| Before | After | |||
|---|---|---|---|---|
| Task Type | Source. ForwardingSMTPAddress |
Target. ForwardingSMTPAddress |
Source. ForwardingSMTPAddress |
Target. ForwardingSMTPAddress |
| Mail migration | Points to target * | Not set / Set to any smtp address | Not set (cleared) | Source.PrimarySMTPAddress |
| Points to any SMTP address except for target * | Not set / Set to any smtp address | Remains unchanged | Source.PrimarySMTPAddress | |
| Not set | Not set / Set to any smtp address | Not set | Source.PrimarySMTPAddress | |
| Switch (From source to target option) | Not set / Set to any smtp address | Points to source** | Target.PrimarySMTPAddress or one of the existing email addresses from selected custom domain for forwarding, if set | Not set (cleared) |
| Not set / Set to any smtp address | Points to any SMTP address except for source ** | Target.PrimarySMTPAddress or one of the existing email addresses from selected custom domain for forwarding, if set | Remains unchanged | |
| Not set / Set to any smtp address | Not set | Target.PrimarySMTPAddress or one of the existing email addresses from selected custom domain for forwarding, if set | Not set | |
| Unswitch (From target to sourceoption) | Points to target * | Not set / Set to any smtp address | Not set (cleared) | Source.PrimarySMTPAddress or one of the existing email addresses from selected custom domain for forwarding, if set |
| Points to any SMTP address except for target * | Not set / Set to any smtp address | Remains unchanged | Source.PrimarySMTPAddress or one of the existing email addresses from selected custom domain for forwarding, if set | |
| Not set | Not set / Set to any smtp address | Not set | Source.PrimarySMTPAddress or one of the existing email addresses from selected custom domain for forwarding, if set | |
* Target.PrimarySMTPAddress or any of Target.EmailAddresses
** Source.PrimarySMTPAddress or any of Source.EmailAddresses
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:
- Sign in to the https://admin.microsoft.com using a Global administrator account 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.
- Sign in to the https://admin.microsoft.com using a Global administrator account 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.
- Add your updated DNS information to the domain registrar
- 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.
- Sign in to the https://admin.microsoft.com using a Global administratoraccount to change primary emails of affected users. For more information, see Change a user name and email address.
- 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
- Run matching task for all affected account pairs to update TargetEmail column. Clear matching operation is not required. No additional licenses will be consumed.
- 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
Once the users are matched/migrated, you can transfer the content of their OneDrive for Business storages to the target tenant.
