Chat now with support
Chat with Support

Welcome, erwin customers to Quest Support Portal click here for for frequently asked questions regarding servicing your supported assets.

On Demand Migration Current - Administrator Guide

About On Demand Migration Signing up for Quest On Demand Before You Start Working with On Demand Migration Starting a Migration Project Account Migration Mail Migration Public Folders Migration OneDrive Migration SharePoint Migration Microsoft Teams Migration Content Migration for Office 365 Groups Troubleshooting Finalizing the Migration

Populating from File

You can populate any existing collection using a comma-separated values (CSV) file with account attributes.

NOTES:
  • CSV file can contain one or more columns. There are no special requirements for header names.
  • One of column must contain case insensitive user principal name data that will be used for matching.
  • File names with non-ASCII characters are not supported.

To populate collection from CSV file

  1. Prepare a comma-separated values (CSV) file with data of discovered accounts you want to add to the collection. File can contain accounts that have not been discovered, but these accounts won"t be added to the collection. One of the columns should contain the user principal names (UPNs). For example:

userPrincipalName, email, objectID

Example@testexample.onmicrosoft.com, Example@testdomain.com, d6801a8b-5cb1-48f4-9757-4465564c5c63

  1. Select a collection you want to populate on Dashboard and click it to open the Collection Dashboard
  2. Click Fill from File to populate the collection with discovered objects you specified in the file created on Step 1.
  3. Click Browse to open the comma-separated CSV file created on Step 1.
  4. Browse for file and click Open. Selected file name appears next to the Browse button.
  1. Click Populate to populate the collection.

The collection is populated. You can see added objects on the Collection Dashboard.

NOTE: The objects that do not exist in the source or target tenants and the source accounts that are not enumerated during the Discovery are ignored without producing an event.

Exporting Mapping for Selected Objects

To export the mapping as a comma-separated values (CSV) file, select objects in the grid and click More Actions | Export.

You can customize this file and use it as a base for manual mapping.

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. To create Matching Task:

NOTE: Email address of existing object remains unchanged by default.

  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.
  1. Click Accounts
  2. Select the accounts you want to match and click Match Accounts.

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

  1. Select Match by attributes. By default, you are matching the accounts using the attribute value. For example, identical display name or email address. You can also create more complex matching rules, for example using different attributes on source and target. 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 the matching rule, scheduled start of the task and name the task. Click Finish to save or start the task depending on schedule option selected.

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

Using the Manual Mapping

In some cases, the matching accounts attributes may differ. For example, it might happen when you have created some of the accounts manually as a part of initial migration to the new tenant. To handle such environments, you can provide a file with the custom mapping between source and target accounts.

  1. Prepare a comma-separated values (CSV) file with the matched account pairs. The first row defines the names of the source and target attribute used for mapping. Subsequent rows list the matching values of the attributes (one pair per row.) For example:

<sourceAttributeName>,<targetAttributeName>

john.doe@source.domain,jdoe@target.domain

jane.roe@source.domain,jane@target.domain

NOTES:
  • Supported source attributes: userPrincipalName, objectId.
  • File names with non-ASCII characters are not supported.
  • Account pairs in which one of the accounts is a guest account are not supported.
  1. Open Accounts and click More Actions | Map from File. Do not select any accounts from the list – you have already specified them in the file created on Step 1.
  2. Click Browse to open the mapping file created on Step 1.
  3. Browse for file and click Open. Selected file name appears next to the Browse button.
  1. Schedule when the task will be started. See Task Scheduling for details. Click Next to view task summary.
  2. Check selected options. Click Finish to save or start the task depending on schedule option selected.

The task is created. You can track the progress in the Tasks list or view the summary on the Dashboard.

NOTE:

  • The account pairs that do not exist in the source or target tenants as well as the source accounts that are not enumerated during the Discovery are ignored without producing an event.
  • If you import the mapping from file, an active collection, selected accounts, search, and filters are ignored. The matching is always performed for all pairs provided in the file.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating