Best way of changing email addresses for merge migration

[Robert Wen_ReleaseTEAM_]

I'm in the middle of a merge migration, where I have moved over project data using Copy Product Data.  

For users and groups, I've moved one affected site onto a Jira DC instance and am looking at user management.

For 57 active users, what's the best approach to changing their email addresses?  I'm looking at using REST API or DB calls, but manually changing the emails works too, yes?

[Ed Letifov _TechTime - New Zealand_ · Accepted solution]

Hello, @Robert Wen_ReleaseTEAM_ 

1) Yes manually works too, but doing it via ScriptRunner script is the easiest option

2) I am not sure if splitting the merge into product data copy and users will somehow work. How are you planning to push the updated users back to Cloud? JCMA matches users by their email i.e. if you data is already linked to user records with old emails – you will just create duplicate user records not linked to any data? If re-keying like this you should really push project data from DC to Cloud with JCMA

3) The alternative is a bit cumbersome but could be done directly in Cloud if you control both domains. If you are in control of the old domain you can just change their emails in Cloud without the need to go to DC.

[Robert Wen_ReleaseTEAM_]

Option 3 may sound like the way.  That seems to suggest managed accounts.  What if we haven't set up Atlassian Access yet?  Would manually performing "suggest new email addresses" work?

[Ed Letifov _TechTime - New Zealand_]

@Robert Wen_ReleaseTEAM_ 

You don't really have to "set up" Access – you just need to verify the domain and claim accounts. It just requires a TXT record to be added to DNS and takes minutes.

Until accounts are managed you (as an org admin) can't change emails for users – they are under control of the user.