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

Exporting Accounts

  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 tab and select List View if not already selected.
  6. Select the accounts to export.
  7. Click More > Export.

  8. Open the CSV file by extracting it from the ZIP file that is downloaded to your computer.

Removing Accounts

To manage large lists of accounts in a project, you can remove one or more accounts from the accounts list that you don't need for migration processes. The accounts that are removed will remain in the source tenant and you must re-discover the accounts in the project when you need them for migration.

If these accounts are listed in other projects, they will be displayed in those projects.

  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 tab and select List View if not already selected.
  6. Select the accounts you want to clear.

    TIP: Use filters, search or collections to quickly navigate through the list of accounts.

  7. Click More > Delete.

  8. The Remove Objects confirmation dialog opens.

  9. Click Remove to remove the selected accounts from the list.

Managing Accounts with Collections

Migrating large numbers of accounts requires careful planning. The accounts could belong to different offices and geographical locations or sensitive departments. Migrating groups of employees in top management, Finance or Legal departments require special care. Organize the accounts into collections to make large account lists more manageable.

Working with the Collection Dashboard

The Collection Dashboard shows the collection-specific summary, allows you to see accounts added to it, create tasks for them, and monitor the progress of tasks.

  • To view the collection dashboard for an existing collection
    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. From the project dashboard, click Open in the Accounts tile to open the Accounts and User Data migration workspace
    5. From the top-right corner of the migration workspace, click Select Collection and then select the collection to view. The collection Dashboard is displayed.
    6. Click Browse Accounts from the collection Dashboard menu or open the Accounts tab. You will see the list of accounts that belong to the collection.

  • To see the tasks for collection-specific account objects, open the Tasks tab.
  • To see the events related to the collection, open the Events tab.
  • To rename the collection, click Rename Collection in the Actions toolbar of the collections dashboard.
  • To delete the collection, click Delete Collection in the Actions toolbar of the collections dashboard.
  • To return to the Account migration workspace, click the collection dropdown at the top-right corner of the page, and select Show All.

Adding accounts to Collections

You can add accounts to collections in three ways:

To add selected accounts to a new collection:

  1. From the project dashboard, click Open in the Accounts tile to open the Accounts and User Data migration workspace.
  2. Open the Accounts tab and select List View if not already selected.
  3. Select the accounts you want to add to a collection.
  4. From the actions toolbar, click New Collection. The New Collection dialog opens.

  5. Enter a collection name in the Collection name field and click Save to add the selected accounts to the collection.

To add selected accounts to an existing collection:

  1. From the project dashboard, click Open in the Accounts tile to open the Accounts and User Data migration workspace.
  2. If you need to create a new collection:
    1. From the top-right corner of the migration workspace, click Select Collection > + New Collection
    2. Enter a collection name and click Save to add this collection to the project.
  3. Click the Accounts tab and select the accounts that you want to add to the collection.
  4. From the actions toolbar, click Add to Collection. The Add to existing collection dialog opens.

  5. Select your collection from the Collection name dropdown and click Save to add the selected accounts to the collection.

To create one or more collections with a CSV file:

Using a CSV file provides the following additional benefits:

  • Multiple collections can be created with the same CSV file.
  • Existing collections can be specified in the CSV file to add additional accounts
  • Accounts can be listed in multiple collections

This is a two-step process as described below:

Step 1: Prepare the CSV file

NOTE: You can download a CSV template for either of the two formats when you click More > Import Collections to open the Import Collections from File dialog.

You can choose one of two formats to prepare the CSV file:

Format 1: Use the ObjectId to identify accounts

  • ObjectId - Column header for the globally unique identifier that represents a discovered account. The following variations of ObjectId are supported: ObjectId, objectid, objectId, OBJECTID
  • Collection - Column header for the collection name

Format 2: Use the UserPrincipalName to identify accounts

  • UserPrincipalName - Column header for the login name of an account based on the Internet standard RFC 822. Do not use a mail nickname or proxy address. The following variations of UserPrincipalName are supported: UserPrincipalName, userprincipalname, USERPRINCIPALNAME
  • Collection - Column header for the collection name

Step 2: Import the CSV file

  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 migration workspace.
  5. Select the Accounts tab and select List View if not already selected.
  6. From the actions toolbar, click More > Import Collections. The Import Collections from File dialog opens.

  7. Click the Provide accounts as a list of drop-down and select either ObjectIds or UserPrincipalNames depending on the format of the CSV file that you have prepared.
  8. Click Browse and select the CSV file. The selected CSV file name appears.
  9. Click Import.

NOTE: Identifiers of accounts that are not discovered are ignored without producing an event.

Removing Accounts from Collections

  1. From the project dashboard, click Open in the Accounts tile to open the Accounts migration workspace.
  2. From the top-right corner of the migration workspace, click Select Collection. Then select a collection to open the collections dashboard.
  3. From the list view, select the accounts that you want to remove from the collection.
  4. From the actions toolbar, click Remove from Collection.
  5. In the confirmation dialog click Remove to remove the selected accounts from the collection.
  6. To return to the Accounts migration workspace, click the collection dropdown at the top-right corner of the page, and select Show All.

Matching and Mapping Accounts

Before migrating user or group accounts, check if the target tenant already contains accounts from the source tenant to avoid duplication. You can match accounts from the Account List View. Alternatively, you can use a CSV file to manually match or map accounts with the New Account Mapping from File Task wizard, including those with different attributes or those not yet present in the target tenant.

You can match source accounts with existing target accounts that have the same attributes directly in the Account List View. For accounts with different attributes, use a CSV file to specify the match. When you match accounts, the target account information is displayed in the Account List View. During migration, the target account will be updated if it already exists or created if it does not exist.

For mapping source accounts to new target accounts, use a CSV file. When you map accounts, the target account information is displayed in the Account List View. During migration, new target accounts will be created based on the mappings.

If needed, you can reset all existing matches and mappings to start over.

NOTE: If a source account is not matched or mapped, and a target account exists with the same Name, UserPrincipalName or PrimarySmtpAddress, then the account migration will fail.

Example 1: Matching accounts

Jordan Davis is a user in the source tenant. If Jordan Davis exists in the target tenant as well, you can match the accounts by display name directly from the Accounts List View by using the New Account Matching Task wizard.

Some users in the source may have one set of matching attributes like display name, while others may have another set of matching properties like email, mail nick name, immutable id or employee id. You can run the Account Matching Task multiple times, and each time you can specify a different matching attribute for the selected set of users.

When accounts are successfully matched, the Account State column value in the Accounts List View will change to Matched. When matched accounts are migrated, the target account will be updated with the attribute values of the source, and permissions are merged.

When accounts cannot be matched, the Account State column value in the Accounts List View will remain as Discovered. When unmatched accounts are migrated to the target tenant, then On Demand Migration automatically uses the source account information to create this account in the target tenant.

Example 2: Merging accounts

Group A and Group B are two groups in the source tenant that must be merged with Group C that exists in the target tenant. You can match one or more accounts from the source tenant to a single account in the target tenant by using a CSV file in the New Account Mapping from File Task wizard. When the task completes successfully, the Account State column value in the Account List View will change to Matched for both Group A and Group B. Information about group C will also be displayed.

The order in which the two groups from the source are migrated will determine the outcome for the target group in a merger. If Group A is migrated first, then Group C is renamed as Group A in the target. The permissions of Group C are retained, and permissions from Group A that were not in Group C are added (permissions are merged). When Group B is migrated, Group C that was renamed to Group A in the target will be renamed again to Group B, and the permissions are merged once more.

Example 3: Creating new accounts

Group X in the source tenant must be mapped to a new Group Z that does not yet exist in the target tenant. You can accomplish this by using a CSV file with the New Account Mapping from File Task wizard. After successfully completing the task, the Account State column in the Account List View will indicate Mapped for Group X, and information about Group Z will also be displayed.

When Group X is migrated, a new Group Z will be created in the target tenant based on the attributes specified in the CSV file. All the permissions and details from Group X will be transferred to Group Z. The values provided in the CSV file that are used to create Group Z will remain unchanged even if you update Group X before migration.

Avoid mapping multiple accounts from the source tenant to non-existent accounts in the target tenant, as this will cause the migration to fail.

 

In this topic:

Matching accounts selected from the accounts list

  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. Go to the Accounts tab and select List View if not already selected.
  6. Select the accounts you want to match and then click Match > Match Selected from the List View menu. The New Account Matching Task wizard opens.
  7. Step 1: Account Matching

    1. Select and configure the options as described below:
      • Clear existing matches - all matches are cleared.
      • Match by attribute - use the specified attribute pairs to match accounts in the source and target tenants. Select the same matching attribute for the Source attribute and Target attribute. The matching attributes are as described below:
        • displayName - the attribute of the account as specified in the same active directory property.
        • mail - email address
        • mailNickname - email alias used in Exchange servers.
        • ImmutableId - a specific attribute for a Microsoft 365 account object that is synchronized from on premise Active Directory. When AAD Sync is used with the default settings on Uniquely Identifying your users, the Active Directory objectGUID is used as the immutableId.
        • employeeId - the identifier of an employee in active directory.
    2. Click Next.
  8. Step 2: Notification
    1. Send notification email once the task is completed - select this option to send a notification email when a discovery task completes.
      • Only in a case of failure - Select this option to send the email if the discovery task fails to complete successfully.
    2. Recipients - enter the email address of the recipients of this email. You can specify multiple recipient email addresses separated by semicolon.
  9. Step 3: 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 - task runs immediately.
      • Run later - task must be started manually.
      • Schedule - task will be started at a future date and time entered in the corresponding calendar field.
    2. Click Next.
  10. Step 4: Summary
    1. Verify the task specifications as described below:
      • Name - name of the task. The default name is Account Matching Task. You can specify a custom name.
      • Source tenant - name of the tenant where the statistics will be collected.
      • Target tenant - name of the target tenant in this project.
      • Assign Licenses - value is Yes.
      • 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.

Matching or mapping accounts with a CSV file

Use this method to match or map accounts from the source to accounts in the tenant that have different attributes. The CSV file lets you specify the accounts that you want to map and ignore the rest. You can then use this file in the New Account Mapping from File Task wizard to match or map the accounts from the source to the target tenant.

The steps are as follows:

  1. Download the relevant CSV template.
  2. Prepare the CSV file.
  3. Start the Account Mapping from File Task.

TIP: You can get a list of users or groups for your CSV file along with pertinent information directly from the Microsoft 365 Admin Center.

  1. Log in to the Microsoft 365 admin center with the credentials of your source tenant administrator.
  2. Export Users:
    1. From the navigation pane, click Active users.
    2. If needed, you can filter the set of users that you want to export. Then click Export. A Users_<timestamp>.csv file will be downloaded to your computer.

  3. Export Groups:
    1. From the navigation pane, click Active groups.
    2. Select the Microsoft 365 tab in the Active Groups page.
    3. If needed, you can filter the set of groups that you want to export. Click Export and then click Export groups in this list. A Groups.csv file will be downloaded to your computer.

  4. Repeat steps 1-3 for the target tenant.

Step 1: Download the relevant CSV template

  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 tab and select List View if not already selected.
  6. From the List View menu click Match > Map From File. The New Account Mapping from File Task wizard opens.
  7. Step 1: Mapping File
    1. Click Download Example File.
    2. Click Cancel to exit the wizard.

Step 2: Prepare the CSV file

  1. Create a CSV file and add the attributes of the users and groups you want to match or map from the source to the target tenant. You can use any of the two formats shown below:

    NOTE:

    • User account pairs in which one of the accounts is a guest account are not supported.
    • CSV file names with non-ASCII characters are not supported.

    You can prepare the CSV in one of two formats to match the source account with an existing target account. If a match is not found, the source account is created in the target tenant during migration.

    Format 1 Using the SourceUPN and TargetUPN

    • SourceUPN - Source account name in the format of an email address based on the Internet standard RFC 822. Do not use a mail nickname or proxy address.
    • TargetUPN - Target account name in the format of an email address based on the Internet standard RFC 822. Do not use a mail nickname or proxy address.

    Format 2 Using the SourceObjectId and TargetObjectId

    • SourceObjectId - Globally unique identifier (GUID) of the source account.
    • TargetObjectId - Globally unique identifier (GUID) of the target account.

     

  2. Save the CSV file that you created.

Step 3: Start the Account Mapping from File 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 tab and select List View if not already selected.
  6. From the List View menu click Match > Map From File. The New Account Mapping from File Task wizard opens.
  7. Step 1: Mapping File
    1. Click Browse and select the CSV file with the account maps that you prepared.
    2. Click Next.
  8. Step 2: Notification
    1. Send notification email once the task is completed - select this option to send a notification email when a discovery task completes.
      • Only in a case of failure - Select this option to send the email if the discovery task fails to complete successfully.
    2. Recipients - enter the email address of the recipients of this email. You can specify multiple recipient email addresses separated by semicolon.
  9. Step 3: 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 - task runs immediately.
      • Run later - task must be started manually.
      • Schedule - task will be started at a future date and time entered in the corresponding calendar field.
    2. Click Next.
  10. Step 4: Summary
    1. Verify the task specifications as described below:
      1. Name - name of the task. The default name is Account Mapping from File 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. 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.

Reviewing the Account Matching Task

  1. Open the Tasks tab.
  2. Select the account discovery task that you want to review.
  3. In the task details pane that opens, the information presented is as described below:
    1. Type - Type of the task. The type is Matching.
    2. Created - Date and time when the task was created.
    3. Modified - Date and time when the task was last updated.
    4. State - State of the task.
    5. Last Operation - The action that was most recently performed in this task.
    6. Schedule - Date and time when the task started. Now indicates that the task started immediately after the task was created.
    7. Accounts (number) - The number of accounts that were selected for matching and the number of accounts passing through the various states of the task from New to Completed.
    8. Events (number) - Number indicates the count of events that the task encountered. The values indicate the type of the events and the event count for each type.

Reviewing the Account Matching Task Events

  1. Open the Tasks tab.
  2. Select the account discovery task for which you want to review the events.
  3. In the task details pane that opens, click Events (number). The Events tab opens with a filtered list of events for the selected task.
  4. Select an event that you want to review. In the task details pane that opens, the information presented is as described below:
    1. Object - name of the account object if applicable.
    2. Task - name of the task.
    3. Time - date and time when the event occurred.
    4. Category - type of task. For account mapping tasks, the category is Matching.
    5. Summary - a descriptive statement about the event.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating