When doing a cloud migration and performing user renmaing as a part of the cloud migration, I can map the following:

OnPrem User: John.Doe@customer.dk to Cloud User: John.Doe

..all is good and the migration tool will now rename the username "in reverse" to update related tables where that username is attached to entries. This means that my entries, registers etc. now have John.Doe@customer.dk assigned and not Joh.Doe as expected. Furthermore the user is also renamed to the OnPrem username John.Doe@customer.dk but on the positive side I have an alignment between username and entries.

The problem that new users being imported into BC, after the migration, will have a different usernaming syntax than the re-named cloud users as they will come in as: New.User.

Customers do not like usernames created with different syntaxes hence the only way to align usernames is by re-renaming the cloud migratrated users back to their "old" cloud username - and it works but takes time and must be done manually 1 by 1.

So this request is to enable the posibility to do a batch post rename operation, trigger manually, re-using the already defined user mapping from earlier in the cloud migration process.