Best Practice Jira server migration to AWS EC2 server deployment

[Nathaniel Laughlin]

We are planning to migrate our Jira/confluence/bitbucket instances to AWS EC2. With this, we will also be switching from a AD user directory, to a SAML created Jira internal directory. I am wondering if there is an easy way to ensure that ticket assignments etc remain the same, however I am guessing there is no way to do this. I was also wondering on that same line, if there is a way to automate this process of reassigning everything. 

[Richard White _TechTime_]

Hi Nathaniel,

We have done similar renaming procedures for some of our customers. The general procedure we have been following is this:  

- Bulk move the users from your AD user directory to Jira / Confluence / BB internal directory. We use a feature of our User Management App (available on Jira, Confluence and Bitbucket) to achieve this, although there are other solutions available.

- Bulk rename the users in the internal directory to match those provided by your SAML IDP., For example, sAMAccounName to email. We have been using internally developed ScriptRunner scripts to achieve this so far. Feel free to reach out to our 24x7 Support team, if these might be useful for you.

- Restart the jira instance and test thoroughly before migration.

Note: I highly recommend to try in test environments first.