Tfusermapping Getuserlist restricting for limited users instead of all users

[Lokeshmaxi]

I was planning to migrate tfsteamsettings with tfsusermapping tool with user-mapping.json with two users, but in source org the users count might be above 10k,when running this both, the tfsusermapping is showing logs with GetUserslistfromserver which loads all the users for each run, I want to validate only users in usermapping json in source, is this possible? This becomes difficult during bulk migration

[MrHinsh]

Here is what I think that you said:

• You plan to use tfsusermapping and tfsteamsettings tools together.
• You have a user-mapping.json file that maps only two users.
• The source TFS organisation has over 10,000 users.
• When running the tools, especially tfsusermapping, it calls GetUsersListFromServer, which retrieves all users each time.
• You only want to validate or process the users specified in your user-mapping.json, not all 10,000.
• This full user retrieval makes bulk migration slow and inefficient.

Here is my answer:

You only need users in the mapping file when the system is unable to match them automatically. This happens by default at runtime as wel, items are migrated and an authenticed user field is mapped. It does not load all users at that time.

The only time All Users are obtained from the server is to match the source to the target and see if any mappings are missing before we start.

Are you asking to be able to disable that check for each run as you have a lot of users?

[Lokeshmaxi]

Hi Martin, just think in a way,when we have to map users upto 100 with bulk migration of workitems & with different mail id source: "Martin@abc.com" and target have same user but different mail id "Martin@xyz.com", but actuall users in source have around 10K, it will takes very longer time to complete each run , please make a option to validate users from user-mapping.json source key , my example user-mapping.json: { "Martin@abc.com: Martin@xyz.com"} and also i can use same usermapping json with DisplayName/identity , only request is to enable feature to avoid validating all users from source.

[Lokeshmaxi]

Please correct my understanding, If source users have maid id has "User@abc.com"and target have same users with different mail id such as "User@xyz.com", then I have to use 'usermapping.json' right ? If yes I want to validate only users in usermapping json, since I'm migrating limited user's

…

On Tue, 24 Jun, 2025, 9:01 pm Martin Hinshelwood nkdAgility.com, < ***@***.***> wrote: Here is what I think that you said: - You plan to use tfsusermapping and tfsteamsettings tools together. - You have a user-mapping.json file that maps only *two users*. - The *source TFS organisation has over 10,000 users*. - When running the tools, especially tfsusermapping, it *calls GetUsersListFromServer*, which *retrieves all users* each time. - You *only want to validate or process the users specified in your user-mapping.json*, not all 10,000. - This full user retrieval makes *bulk migration slow and inefficient*. Here is my answer: You only need users in the mapping file when the system is unable to match them automatically. This happens by default at runtime as wel, items are migrated and an authenticed user field is mapped. It does not load all users at that time. The only time All Users are obtained from the server is to match the source to the target and see if any mappings are missing before we start. Are you asking for: "To be able to disable that check for each run as you have a lot of users" — Reply to this email directly, view it on GitHub <#2774 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AVWU7CM6KQ3M7Y4UBWULOLL3FFVMHAVCNFSM6AAAAACAATRBW6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGNJWGM3TMNA> . You are receiving this because you authored the thread.Message ID: <nkdAgility/azure-devops-migration-tools/repo-discussions/2774/comments/13563764 @github.com>