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

Assessment

On Demand Migration analyzes your domain structure and tracks potential problems, misconfiguration, and risks that might adversely affect the migration. Switch to Assessment view to see the summary reports about the discovered data.

The following reports are available for Accounts:

  • To clean up
    • Disabled accounts
    • Users with non expiring passwords
  • To adjust
    • Duplicate group names
    • Duplicate user names
    • Users without first name
    • Users without last name
  • Account statistics (inventory data)
    • Number of users
    • Number of groups
  • User data
    • External Accounts
    • Tenant members

Once you address the issues you are ready to start the migration.

Matching Accounts

Your target tenant might already contain accounts created for the source tenant users before the migration. You can map them to the corresponding source accounts, so that no data is lost or duplicated.

In this topic:

 

Create and run a New Matching 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 select an existing project.
  4. Click Accounts from the project tiles. You can also click Open Project to open the project dashboard and then click Open from the Accounts tile. The Accounts and User Data dashboard opens.
  5. Click the Match Accounts link in the Getting Started tile

    - or -

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

  6. Select the accounts you want to match and then click Match from the Accounts and User Data dashboard.

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

  7. The New Matching Task wizard opens.
  8. Step 1: Account Matching

    1. Select Match by attribute.
    2. 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 prem 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.
    3. 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. 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.

Prepare a CSV file with mapped accounts

This step is required if you plan to map specific accounts from the source to existing accounts in the tenant that do not have any matching 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 Mapping from File Task as described in the next section, to map the accounts from the source to the target tenant.

To prepare the CSV file:

  1. Log in to the Microsoft 365 admin center (https://admin.microsoft.com) 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.
  5. Create a new CSV file and add the attributes of the users and groups you want to map from the source to the target tenant, from the CSV files that you exported. You can follow any of the two formats shown below:

    NOTE:

    • CSV file must have two columns: <source-attribute-name> and <target-attribute-name>
    • Supported attribute names:
      • userPrincipalName - An Internet-style login name for a user account based on the Internet standard RFC 822. Do not use a mail nickname or proxy address. When you use UserPrincipalName (UPN) as the column header, you can combine UPN and group object GUIDs in the same list
      • objectId - Globally unique identifier (GUID) of the user or group object. When you use ObjectId as the column header, you must specify object GUIDs only. You cannot specify UPNs.
    • 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.

    Format 1 using userPrincipalName

    Format 2 using objectId

  6. Save the CSV file that you created.

Create and run a New 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 select an existing project.
  4. Click Accounts from the project tiles. You can also click Open Project to open the project dashboard and then click Open from the Accounts tile. The Accounts and User Data dashboard opens.
  5. Click the Match Accounts link in the Getting Started tile

    - or -

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

  6. Click More Actions and then click Map From File.

  7. The New Mapping from File Task wizard opens.
  8. Step 1: Account Matching

    1. Click Browse and select the CSV file with the account maps that you prepared.
    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. 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 mapped successfully, the Status changes from New to Completed.

 

Migrating Accounts

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

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. Go to the migration project Dashboard in case you use new migration UI. In case you are using classic experience or you are already on the account migration Dashboard, go to step 3.
  2. Click Accounts widget.
  3. Click Accounts.
  1. Select accounts / groups you want to migrate. In case you are planning to migrate Microsoft 365 Groups including content, it is recommended to perform migration using Teams as described in Migrating Groups and Associated Content

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

  1. Click Migrate Accounts and provide vanity domain name instead of default *.onmicrosoft.com. Typically it is a domain name of your organization.

IMPORTANT: The custom domain name must be set up on the target tenant. See Quickstart: Add a custom domain name to Azure Active Directory for details.

  1. Click Next to proceed.
  2. Schedule when the task will be started. See Task Scheduling for details. Click Next to view the task summary.
  3. Check selected options and name the task. Click Finish to save or start the task depending on schedule option selected.

The migration task is created. You can track its progress in the Tasks, view the summary on the Dashboard or monitor alerts and notifications in the Events.

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

Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation