Moving from Vendor's Jira to Company owned Jira

[Mark Hansens]

Hello Peeps.  Our company has a vendor that does our development and we have been maintaining the development backlog in the vendor's Jira instance.  Our company has decided that we want to move this to our own instance of Jira.  I have read through this article about how to do it, but I'm still not sure about the details.  For example, it seems to suggest that one must be Org admin and product admin in both instances.  Am I understanding that correctly?  Would I need to have our vendor temporarily assigned to these roles in order to accomplish this?  I'm a noob to Jira admin, so I have much to learn.

[Valerie Knapp]

Hi @Mark Hansens , welcome to the Atlassian Community and thanks for your question.

Yes, basically someone needs to have org admin access in both instances to facilitate the migration. Of course the other possibility is that you give temporary access to the new instance to your vendor. Either way, someone needs this enablement on both sides to be able to access the correct scope to move and then to move it. 

You can, if you have budget, also engage an Atlassian Partner for this https://partnerdirectory.atlassian.com/ 

Depending on how complex the migration is, this might not be necessary but something to keep in mind. 

Best wishes and good luck to you!

[John Funk]

Hi Mark - Welcome to the Atlassian Community!

Another option is to use a third party app like the Revyz Data Configuration Manager. With it you can clone a single project from one instance to another Cloud instance. 

[Mathew Lederman]

@Mark Hansens welcome to the life of a Jira Admin! 

Yes, you've read the documentation correctly. You will need to give your vendor partner org admin permissions in both your current and future instances. You can find more details here about permissions and things to check before you start the copy: https://support.atlassian.com/organization-administration/docs/before-you-start-copying-product-data/

As a personal recommendation, I would create a sandbox site (or two) and try the copy a few times to ensure you get it right for the Production environment.