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.
- Prepare a comma-separated values (CSV) file with account pairs. The first row contains the names of the source and target attribute used for mapping (might be different.) Subsequent rows list value pairs for those attributes (one pair per row.) For example:
- You can use userPrincipalName and objectId source attributes for mapping.
- File names with non-ASCII characters are not supported.
- The example above, customTargetAttribute, will need to be changed to a valid attribute that you are using for matching in the target environment, such as userPrincipalName.
- Open Accounts and click Map from File. Do not select any accounts from the list – you have already specified them in the file created on Step 1.
- Click Browse to open the mapping file created on Step 1.
- Browse for file and click Open. Selected file name appears next to the Browse button.
- Schedule when the task will be started. See Task Scheduling for details. Click Next to view task summary.
- 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.
- The account pairs that do not exist in the source and/or target tenants and 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.