Splitting a Jira Agile Cloud account in two


My company has been using a single JIRA Agile account for a number of project over two departments. Due to a fast growth we would now function much better if we could split the existing account in two, one per department, each with its own projects, while keeping all the issues, schemas, workflow, etc.

Is it possible?

Thank you

4 answers

0 votes

Buy a new Cloud instance, export everything from the old one (using the standard backup) and import it into the new one.  Then selectively delete everything you don't want from old and new.

Hi Nic, thanks for your answer. I have a couple of follow-up questions:

  1. Is there a way to export only part of the instance or do I actually need to export the whole thing and then selectively delete the stuff I don't need from both the accounts?
  2. Is there a way to take subsequent backup snapshots of the account while I delete the unwanted stuff, in case something breaks during the process?

Thank you!

  1. No, that's why I said you need to export and import
  2. Yes, although you are limited to taking a backup once every other day.


We're about to buy a new JIRA instance and start the migration, but I have a follow up question:

Our current JIRA is 100 Users, for the new one we need a 25 users instance. What happens with the import process? Is it going to ask to deactivate users during importing? Should we get a bigger instance, then deactivate users and scale it back? How easy is it to scale back from 100 to 25, and does that cost anything?

Thank you!

On Cloud, I'm not actually sure. 

On Server, the import would carry the 100 user licence over, and then go read-only after you apply the 25 user licence until you got the numbers down.  On Cloud, the licence might not be transferred, so I'd expect read-only until you drop the numbers. 

But, Cloud billing is supposed to be "we charge you for the users you had that month", so it may import 100, you get charged for 100 for a month, and then it drops to 25 after you reduce the numbers down

Thanks Nic

So we should be able to get the 10 users licence and it will automatically switch to the 100 tier upon import, then back down after we delete users?

Yes, but if you contact https://support.atlassian.com and tell them what you're doing, you may be able to avoid the switch to 100 user licences.

You could also reduce the users down to 10 before doing the export - that's the most simple route!


We're in the middle of testing the migration and clean-up. I have a follow-up question: it doesn't look like Confluence has been exported as part of the process. Does that need a separate, dedicate migration? Is that the same workflow?

Thank you

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,676 views 18 21
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you