Why Cloud?

[Dominika Kuraś-Moskwa [Deviniti]]

Hello Community!

I have a question for those who used to be team Server. Why did you decide to migrate to Cloud? What was a game changer for you? Share your thoughts with me!

[Ben Ernest-Jones]

Because Atlassian is stopping support for Server. That's the only reason. And the equivalent (Data Center) is too expensive.

[Dominika Kuraś-Moskwa [Deviniti]]

Thanks for sharing. Yeah, I noticed that the price greatly impacts this decision. 

[Bryant Browning]

Same here - since Atlassian will no longer be supporting Server version, we have no choice but to consider Cloud version. We are considering Data Center, but again the cost is a concern. However to be totally honest, Cloud version does seem to work a bit better, and the portability for us to share spaces with our vendors is a bit easier.

One question does arise, though...if switching to Data Center, will it be a matter of time before this is no longer supported also? Just wondering....  

[Andrew Culver]

If you're happy with Server, you'll be happy with Cloud. One big advantage for us was it eliminated our team needing to perform application upgrades.

[Haddon Fisher]

There are some nice things about Atlassian Cloud, most of which boil down to "not having to support a Java application".

As most people already said, the main impetus to move to Cloud is that Server is not supported and DC is too expensive. I'd add that, while it seems like Atlassian will keep DC around for the government agencies and other enterprise-sized holdouts, I've read in their investor letters and been told informally that it won't get much attention besides security and big bug fixes; if you want new stuff, you're kind of stuck migrating.

Cloud is a game-changer, but I would say it changes the game from chess to checkers. There's a lot of issues with Cloud (both strategic and tactical) but there are two major ones that hurts the most:

When something on Server didn't function the way you wanted it to (or at all), you could generally find an add-on to fix it; you could even build or contract your own if you really wanted. Cloud add-ons are significantly limited both in resources and access, so there aren't just more problems but there are also less possible solutions.

The other one is that, as a SaSS application, you're stuck with whatever Atlassian is rolling out and when. For example, a current thing that is happening are the changes to the Automation utilization limits. They've made some minor concessions to cushion the blow, but this type of Product and\or change management fail is fairly common.

[Warren Kent]

Can echo what was said below - Because support for server hosted clients was soon to be EOL.

Nice thing though, is that upgrades are applied when CVE's are identified. Server hosted clients would need to schedule upgrades once the fixes were announced.

Additionally, new features and bugs are released and upgrades are seamless and without any downtime.

Been on cloud for a year and although its costly, its been good.