Migration from JIRA Server to JIRA Cloud (and Confluence)

I am trying to put together a business case to migrate from JIRA server to JIRA cloud.  The obvious benefit being on the latest and greatest version of JIRA at all times.  Is there any additional information out there on pro/con?  Any risks we should consider?  Are there any pains of being on the Cloud version? 

I would also like to consider doing the same with Confluence - are there size restrictions that we need to be aware of? Pro/Con?


3 answers

1 accepted

0 votes
Accepted answer

Thanks to everyone for the feedback!!!  Based on plugin limitations (only 35% of our current plugins are supported on the cloud) it's highly unlikely that we'll move to the cloud.

Hi Wendy,

You aptly describe one of the benefits of Cloud, being able to take advantage of new features right away. Sometimes Atlassian even tries new features on Cloud first (which is pretty cool) using the feedback from customers to determine what changes to perhaps make before launching it into an upcoming release of Server.

Speaking of Confluence only (that's the application I'm most familiar with), the pro of staying on the Server version for us (larger company, 8000 users) is that we can take advantage of some key plugins that are only offered for Server, and can manage/decide when to launch new features for employees.  For the latter, we sometimes prepare special communications to give them an understanding of the features before it's available, and can launch the communications at a suitable time in advance. I don't believe there are size restrictions.

Hope that helps, good luck in your decision process.

The main "con" for moving from server to Cloud is the loss of flexibility on addons and limitation on some functions. For example, you can't use external user directories on Cloud (only the internal accounts or Google apps). The list of addons you can use is strictly limited to the ones Atlassian are willing to support. Before you think about moving either application, have a look at the plugins you've installed and check if they are valid for Cloud. If not, then you'll have to think about replacing them or dropping them. Your question about size is relevant - it's not users, issues or pages, though, it's disk. Your maximum data allowance is 25Gb - to include the databases and attachments. I believe Atlassian are looking at increasing this and/or charging more if you go over it, but I've not heard much about it recently.

Nic, thanks for educating us about the 25GB limit on Cloud.


Tom beat me to the punch to say essentially exactly the same thing so you have two votes in favor of staying server rather than cloud for pretty much the same reasons.

Many are the days where I think that cloud is the way to go for the reasons you cite but mostly on days where I just wish somebody else was looking after this dang thing. Thankfully, those days are few and far between and the cool factor of always automatically having the latest Confluence under my data would be the biggest pro.

That said, and to echo Tom's comments, I have a lot of plugins on my server based instance that aren't able to be loaded in the cloud based version and were just the ticket to solve some problem we needed to get past as we move more and more to centralized content that can be used in our increasingly automated environment.

If Atlassian ever got it so that, for plugins of my choice available regardless of whether or not I was cloud or server based, I'd go cloud in a heartbeat. I wouldn't even think once.

Ok... I'd likely have to think at least once (over and over again) as I would meet with security, IP protection boffins, etc. etc. etc. etc. to validate and convince them that our content is safe in the cloud but if the cloud variant acted and operated in the same manner as the server variant but I wouldn't have to do the daily care and feeding I'd take the short term pain of roughly 1,346 discrete meetings to get there.

Good luck. Hope my $0.02 helps.

I'd forgotten that point about data rights - the Cloud servers are located in the US, are subject to the Patriot Act and hence you need to think about the impact of that on your data. Most of the time, it's fine, but if you store any personal information on individuals, you're pretty much guaranteed to break European data laws. So you'll need to assess your exposure on that!

Not to mention export controls where one works with stuff that is export controlled. Gets even weirder when that is in the mix.

Oh heck, yes. I've not really run into it directly with Atlassian stuff, but from my career before I found Jira 2, yes, that gets very odd. Stuff you can happily export to one country with a simple label can't go to the country next door without 200 process checks. It's not even stuff you'd associate with risks - military or hazardous stuff, it's more like paper clips and loom bands.

Good read! Thanks Nic, Mike and Tom for sharing this! Says much more than technical comparison cloud vs server

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,544 views 15 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