jira upgrade/migrate

We are getting ready to upgrade JIRA. We are currently using version 4.1.2. We are installing the latest version and will be doing it on a different server, VM, than current server. Can we make the upgrade/new install on new server without an interim version? Can all screens, workflows, custom fields, etc be imported to new version? Any info/tips in regards to this is greatly appreciated.

1 answer

1 accepted

0 votes
Accepted answer
There is no easy answer to that. If you are using no plugins, then you are almost certainly going to be fine. If you are using plugins, then the only way to be sure is to test. In all caese, yes, all the config and data will be preserved, although some behaviours will change. The important things are to read the release notes and test.

I've done 4.0 to 6.2 in one step, and I've worked with many Jira systems that have gone through varying levels of 4 -> 6 without significant problems. Some have run into minor bugs, fixed in minor releases by Atlassian, but I've yet to run into one that's been a problem

Except for the plugins. The paragraph above only applies for plain Jira. Plugins have caused us all sorts of problems on upgrade. I'd seriously consider stepping through major releases (4.0 -> 5.2 -> 6.3) if you've got the Agile plugin alone, and for any non-atlassian plugins too, do extensive testing.

Jessica, I am in a similar position. I am upgrading from 4.0 to 6.2. I completed the upgrade by backing up the 4.0 instance and restoring directly into a fresh 6.2 instance.
We have some issues with some plugins no longer being supported so we will need to rewrite some functionality.

The data and configurations (screens, workflows, customfields) look good and we are in the process of testing the new instance functionality.

But I too am concerned about skipping interim versions. I have been warned that this will only lead to problems down the road. So I would like to know from anyone who has completed the direct upgrade approach, Are interim upgrades necessary?



Thank you Nic for your advice, it's really appreciated. Yes we have some complex workflows with a number of plugins (not the Agile plugin). We are conducting testing now, so really hoping we don't hit anything too significant.


Focus on the plugins that write data. Plugins that only read are less likely to be a problem - if they fail, then you can't do stuff, but they won't do any damage (Reports, calculated custom fields, validators and conditions on workflows for exampl). Plugins that write are the ones that can block you because they could potentially damage your data.

Thanks for the input!

Did either of you do a test version before moving directly to production?

I've always tested stuff before jumping to production. Always. Ok, so it may be quite light testing when I know "it will work", but that takes some experience. And testing :-)

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Jan 08, 2019 in Jira

How to Jira for designers

I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...

1,193 views 5 10
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