nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Split Jira Software from 1 instance to two

milan.shah

There is a lot of info available about "merging" jira instances, eg I want A & B into C.

My issue is the reverse. We have a single large instance that has grown over time in the company.

Due to governance, and cost allocations, especially for plugins, we would like to separate, ie go from C to A & B.

The dcoumentation suggests using the Backup/Restore function, but that is not working. it assumes on restoration that I have the same number of users, and that I wish to trash all the links on the "original" site as I am now in a "restoration" activity.

Anyone else had this same problem or any advise on how to proceed.

Accepted answers

All comments

Hernan Halabi - Elite IT Consulting Group

Hello @milan_shah duplicating the environment and then removing from each of them the information and users that don't apply to them is the fastest way. If the backup size is too big, I wouldn't suggest you try to edit it, I've done that in the past to update URLs before restoring in order to point to the new instance but the bigger it is, the harder it gets to edit and the more likely that an error will be made.

Another option is to do project imports in a server environment and then once all are migrated you move them all to the cloud. This is far more tedious and it's not that you have a big benefit, you can just pick what to bring instead of bringing all and then deleting.

Nic Brough -Adaptavist-

There are two ways to split a Jira instance into two:

The obvious (and easier) one is to copy the current system to a new one, and then run through deleting the projects you don't want from each one separately. Then remove the users who should not have access.

The more complex, but cleaner one is to export everything from C, then import only the projects you need into A and B. You'll need to add your users and project setups manually in A and B (although there are apps available to help), and you'll need to be doing this on Server versions of Jira, getting them into a shape where you can migrate their backups back into Cloud systems.

No matter what you do, the links back to a target system are going to be trashed, because they will be invalid.

milan.shah

Hi Nic. Thanks for the response.

I tried to copy and restore...and it fails. Error msg on users. restore_user failure.PNG

The cleaner option is to export and then import. I suppose that means filter by project and then csv/xml. the csv option is only avail if I filter the issues. I want to try that, but at the moment, my new target site has now been "locked" and can only be unlocked if I re-do the restore :-(

You also mention tools...can you suggest which ones as the ones I have come across assume I am NOT on cloud.

I also came across https://community.atlassian.com/t5/Atlassian-Cloud-Migration/Would-like-to-Merge-2-projects-from-one-Cloud-JIRA-install-to/qaq-p/1269090 where it seem the suggestion is that to move jira Cloud 1 > Jira Server > Jira Cloud 2, ie migrate from cloud to server and then back to another cloud....

milan.shah

Hi herman. i tried editing, and you are correct, it was too big and started creating errors.

What you say about using Jira Server as a staging env for migration from one cloud to another cloud seems like the guaranteed way, but that is such a pain as we dont have any on-prem space...and the hassle of configuring a Jira Server just so that I can use it momentarily....

Hernan Halabi - Elite IT Consulting Group

What I'm saying is the same thing that @Nic Brough -Adaptavist- suggested as well. Project import isn't the same as CSV import, that one will be the one with bigger chances of losing data as part of the migration. I wouldn't recommend that.

I believe that project configurator can help you with the project import option

https://marketplace.atlassian.com/apps/1211147/project-configurator-for-jira?hosting=datacenter&tab=overview

Nic Brough -Adaptavist-

I'd use Project Configurator, but mainly because I'm surrounded by people who know it a lot better than I do, as I work for the vendor. The other one I'd reach for is Configuration Manager.

But you are right, they are all server based. For Cloud, there isn't much option beyond going through a server system as an intermediate step.

milan.shah

Thanks Nic. The will to separate is getting less and less..these plugins will add to the cost of separation, but I will look into them.

milan.shah

thanks Hernan, already looking at Project Connector.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software