It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Jira Cloud to Jira Cloud export/import - Can you export specific projects/users?

We have a Jira Cloud account and are looking to export specifc projects/users out into a new separate Jira Cloud instance. 

Is this possible? 

I've reviewed this 

And using that method it appears to be ALL or None.

2 answers

2 accepted

0 votes
Answer accepted
Joe Pitt Community Leader Jan 22, 2020

JIRA has never supported exporting individual projects. There is a paid for plugin, Project Manager I believe is the name, in the Marketplace. However it isn't allowed in the cloud so it would be an involved process:

first make sure all JIRA instances are the same version. 

Install JIRA on a server 1

Install JIRA on Server 2 

export a current backup of the cloud and stop using it and the new instance

Install the backup on server 1

Download and install Project Manager per directions

use Project manager to migrate the project to server 2

Backup server 2

Import the backup from server 2 into the new cloud instance. This import will overwrite the cloud instance

0 votes
Answer accepted

Hi @Jeremy Seavey

this article also gives you a (really short) description what you can do:

  1. Prepare a full export of your backup with attachments using the Jira Backup Manager as per Exporting issues.
  2. Import the backup generated above to your new cloud site as per Importing issues.
  3. Delete any unwanted projects.
  4. Disable users which are not needed (as it will import all users from the destination instance) by removing them from all groups and application access.

With the steps 3 and 4, you can choose to delete data again, so that effectively you will only import some projects/users.

An alternative approach could be the following, depending on the complexity of your projects.

  1. Create a new project in your destination Jira
  2. Manually migrate your configuration schemes (workflow, permission, notification, etc.)
  3. Invite the users manually in the new Cloud instance and assign them to the project team
  4. Synchronize the issues with an issue sync app

The first approach is more a one-time migration when your other Cloud instance is empty. The other approach would enable a continuous integration between your Cloud instances and allows a softer migration approach.


PS: I'm working in a team for one of the issue sync apps, Backbone Issue Sync.

Suggest an answer

Log in or Sign up to answer

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you