Migrate users to new instance / Change of Full name and User Name

[Daniel Schillig]

Hello, My customer is migrating his projects to a new Jira instance.

We are using the Configuration Manager for Jira for this. At the same time, the user names and full names are being changed in Azure. The users' email addresses remain unchanged. An SSO is realised (with the SAML plugin from resolution).

The users are moved with the help of the CMJ when the projects are moved and are stored in the Jira internal directory, at least that is my understanding so far.

I am looking for suggestions on how I can implement the scenario without each user having to log in so that their username and full name are reset.

Thank you!

[Kelsey LaMastres _Appfire_]

Hi @Daniel Schillig

Are you performing a DC to DC migration or DC to Cloud? If DC to Cloud (and ultimately if you need to do this Cloud to Cloud), you can customize the user mapping during the analysis in CMJ. Currently this is done through a JSON file, and soon we will release the ability to customize user mapping (and all configurations) through the UI.

Here's the documentation about managing users for a DC to Cloud migration with CMJ: https://appfire.atlassian.net/wiki/spaces/CMT/pages/578519507/User+management 

Either way, I encourage you to reach out to our support team with any questions you have about using CMJ. You can create a ticket here: https://appfire.atlassian.net/servicedesk/customer/portal/11 

Best,

Kelsey at Appfire

[Daniel Schillig]

Hello Carla,
Thank you very much for this detailed message.
I need some time to work out the scenarios for the tests. I will then post here how it went.
Best regards!
Daniel

[Carla Ann Rowland]

Hi Daniel:

It has been a while since I worked with SSO so bear with me and I hope I am interpreting the scenario correctly: 

do the user choose their own Jira name? If so that is going to be rough.

"Use case" currently user Jane Doe goes by JanieD and her email is Jane.Doe@xyz.com.

Since the emails are not changing I would update the emails before migrating the data to avoid duplicates created by the CMJ: if in project old user name is JanieD and new project import user name is Janie.d then CMJ will make a internal directory entry of janied@noplay.com and you will have two profiles for same user.

Then I would configure the new user name to be a parsing the full name off the email. so JanieD would be Jane.Doe.

That way the users who know their own email would be able to log in.

Then I would send an email to the users via Jira email blast informing them in broad strokes of the change not providing details, I would split up the change notification and emails into sub groups to manage any issues in smaller segments. Do last name A's only or the smallest segment first.

Also don't forget employees that have duplicate full name potentials:

so if email is john.james38@xyz.com

then the end user name is going to end up being John.James38.

------------------

I would see if I could change a test profile to see if this solution would work for one or two people.

my 2 cents.