Chat now with support
Chat with 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

Migrating Accounts

Caution: Don’t start the migration before the discovery task is finished. A matching task is recommended.

When the matching is done, it is time to migrate source accounts that do not have the pairs on the target tenant. Create a new 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 Accounts tile, or click Open from the Accounts tile to open the Accounts and User Data dashboard.
  5. Select the accounts you want to migrate. In case you are planning to migrate Microsoft 365 Groups including content, see Microsoft 365 Groups Migration.
  6. Click the Migrate Accounts link in the Quick Help tile

    - or -

    Select the Accounts tab and select List View if not already selected.

  7. The New Migration Task opens
  8. Step 1: Options
    1. Configure the options as described below:
      • Custom target domain name - provide the domain name of your target tenant.
      • Custom domain for forwarding - specify the custom SMTP domain here that will be used as the forwarding address. If you leave this field blank, the primary SMTP address of the source account will be used as the forwarding address for the mail-enabled user created in the target tenant by this task. The SMTP address must already exist on the source object or the task will fail for the account.
    2. Click Next.
  9. Step 2: 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 - the task will run immediately.
      • Run later - the task must be started manually.
      • Schedule - specify a future date and time to run the task.
    2. Click Next.
  10. Step 3: Summary
    1. Verify the task specifications as described below:
      1. Name - name of the task. You can specify a custom name.
      2. Source tenant - name of the tenant where the statistics will be collected.
      3. Target tenant - name of the target tenant in this project.
      4. Custom target domain name - provide the domain name of your target tenant.
      5. Custom domain for forwarding -
      6. Scheduled start - date and time when the task will start. Now indicates that the task will start immediately.
    2. Click Back to revise or review a previous step or click Finish to complete the task wizard and start the task as scheduled.

You can track its progress in the Taskstab, view the summary on the Dashboard or monitor alerts and notifications in the Eventstab. When accounts are matched successfully, the Status changes from New to Completed.

IMPORTANT: On Demand Migration does not synchronize end-user passwords as part of the data migration process. The migration administrator will need to reset or synchronize end-user passwords from the source tenant to the target tenant using native Microsoft 365 tools or third-party Single Sign On tools.

Preferred Data Location

Each account may be assigned a preferred data location property in Azure Active Directory. During account migration the property is migrated from source to tenant. If the account preferred data location is set in the source then the same setting will be migrated to the target. If the preferred data location is not set in the source then it will not be set on the target. This works for General Tenant to Multi-Geo Tenant and Multi-Geo Tenant to Multi-Geo Tenant migrations.

Migrating distribution lists with group delegations

On Demand migrates distribution lists with group delegations (SendAs and SendOnBehalf). Scenarios where the distribution list in the target exists or does not exist, exists and does or does not have group delegations, are all supported. When the distribution list with group delegations exists in the target then only newly added group delegations are migrated, group delegations are ignored if anything is deleted at the source. Existing SendAs and SendOnBehalf group delegations on the target, either preexisting before On Demand migration or migrated by On Demand will be left intact and merged with the one migrated from the source.

Objects are migrated as follows:

  Mail User Mail Box Mail Enabled Security Group Distribution List
SendAs Y Y Y  
SendOnBehalf Y Y Y Y


NOTE: Microsoft does not support these objects in group delegations so they do not apply to the migration.

  • For SendAS: AAD User, External/Guest User, Distribution List, Security Group
  • For SendOnBehalf: AAD User, External / Guest User, Security Group


Guest User Migration

TIP: Guest user accounts have specific icon to distinguish them from the domain members.

On Demand migration can process all guest user types supported by Microsoft.

Before adding a guest user account to the migration task, please consider the following:

  • Guest user account cannot be migrated if an original account for this guest user is already in the target tenant. The guest user account should be matched but not migrated.
  • Guest user account cannot be migrated in case a guest user account of the same original account is already in the target tenant. To update the target guest user account properties create a matching task to pair these guest user accounts and then migrate the source guest user account again
  • Guest user account cannot be migrated in case the invitation procedure in source domain is not finished yet. In case acceptance procedure was skipped (this case is deprecated now, but such guest users still exist), and the acceptance status is empty, guest user can be migrated successfully.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating