User Map File Schema
The user map file specifies how the users are mapped between ClearQuest and Team Foundation. ClearQuest has its own user database and Team Foundation Server uses Windows user names for users. User names in ClearQuest and Windows might not match and the user mapping file gives you chance to specify appropriate mappings. You do not have to specify user mappings. If you do not specify any mappings, the converter will put the user names from your ClearQuest database into the Team Foundation work items. The converter can do that because it runs in a "Rules Relaxed" mode. After migration, when you start editing those work items, some fields might have users who are not valid in Team Foundation. If you have rules on that field that say that the field should contain only valid users, then you will have to supply a valid user in that field before you can save the work item.
To decide what you have to do, consider the following scenarios:
ClearQuest and Team Foundation Windows user names are the same. You do not have to specify any mappings.
ClearQuest and Team Foundation Windows user names are different. You have several choices:
Map the ClearQuest users to Team Foundation users in this file and the converter will do the mappings at migration time.
Elect not to specify the mappings at migration time. If you have rules about some fields having only valid users, you will have to provide valid users when you edit those work items post migration .
Elect not to specify any mappings, and delete the rules that say that a field must contain only valid users. This is not recommended.
Elect not to specify any mappings, but you can add <ALLOWEXISTINGVALUE/> to specify that fields having some existing values should be allowed to retain the existing values even if they violate some rules.
Not mapping users can cause some confusion. Your migrated work items would contain the ClearQuest user names and new work items, or the work items that people edit, would show Team Foundation Server user names. The recommended choice is to provide mappings wherever the ClearQuest user name has an associated, different Windows logon user name, and leave any user names that do not have associated Windows logon user names.
User Map File Schema
The nodes and attributes that you can use in this file are as follows:
<UserMappings> Top level node that contains all the mappings. Only one instance of this node per file.
<UserMap> Child node of <UserMappings>. Specifies one user mapping. Use multiple nodes to specify multiple mappings. The mappings are specified as attributes of this node. The attributes are:
From The user name in ClearQuest. Fill in the name in from ClearQuest that you want to map to a different Team Foundation user name.
To The user name in Team Foundation. Fill in the Team Foundation user name to which the specified ClearQuest name should be mapped.