How to migrate Projects between AD domains, while keeping permissions?

Question

We have recently acquired a company who were running their own JIRA server, that authenticates against their company's Active Directory server, so logins and permissions on all their JIRA Projects use (jsmith@company-a.com)

Our company has consolidated all of our corporate engineering under our own Atlassian stack (including JIRA) that uses "jsmith@company-b.com" for logins and permissions. Each user in company A, now has their own Active Directory account defined in company B's Active Directory (i.e. joe.smith@company-b.com).

The two company's are network connected but the AD domain's have not yet been joined.

The question is, is there a way for us to be able to export/import JIRA projects from the old company to our new Atlassian stack, while getting each user's 'new' AD account permissions to associate with the imported Projects?

Craig Castle-Mead_20fp9z · Answer

Add a local Crowd directory and add it as a lower priority in the application setup.

Create your existing users in the Crowd local directory (sql is easy way to export and then use the UI import). You’ll then have a directory you can edit the users for. Adjust the directory order so the Crowd directory takes precedence over your AD connector.

rename the users in the Crowd local data as and Jira should flow this change through and reassociate all history.

**** test in a non production environment First ****

OneTech IT · Answer

If I add the same Crowd directory source that feeds my target JIRA server, to my current JIRA server, how do I 'rename' the user accounts on the current JIRA server to match their Crowd equivalents?

Craig Castle-Mead_20fp9z · Answer

If you go through an interim directory (JIRA or Crowd) connected to your current JIRA ( jsmith@company-a.com username format) and then rename everyone to their @company-b.com address (manual or api script depending on the number of users), you’ll then be able to export the instance and import in to your combined instance with the right usernames.

CCM