This is the essence of a report I wrote up for one of my customers, with recommendations on what to do about Atlassian's move to Cloud.
I make this available because a lot of companies are having to evaluate the alternatives right now, and may benefit from seeing a worked example that includes short-term discounts. This company is on 2000-user Jira and Confluence, and interacts with their customers through Jira, so some of the considerations, like splitting off a separate JSD, won't apply to non-public Jiras.
If you spot any factual errors or flaws in my logic, please let me know. I regret I cannot make available the spreadsheet the numbers are based on because it contains a Partners-only pricing table. Please contact me if you'd like a similar analysis done for your business.
Atlassian are discontinuing their 'Server' (self-hosted) product line in favor of the Cloud alternatives. This affects us, as we are using both Jira Server and Confluence Server.
Atlassian's timeline is:
Atlassian is pushing the majority of customers to Cloud. The 'Data Center' (DC) product line, a clustered edition for large instances, will still be available, but its price will be increasing by 15-180%.
In 2020 we paid about $49,910 in licensing fees:
These prices were artificially low, as we are on an 'advantaged' (grandfathered) plan that escaped the 2019 price increases.
The three options Atlassian make available to us are:
Here are the anticipated prices for each option, taking into account projected user growth and various short-term discounts. There are two DC rows because the price for DC will be different (for a while) if we act before Feb 1, 2021 and get on a 'grandfathered' / advantaged plan to escape the 15-180% price hike coming then.
We are in for an 8x-13x price increase over the next 6 years
The least disruptive move would be to move to Data Center, assuming we can afford it (the 'DC, after Feb 1, 2021' column). Moving early will get us on the discounted 'advantaged plan' for a while. Just be aware that DC is an annual subscription, not a perpetual license like Server, and that DC won't last forever (see blog post Betting on Atlassian DataCenter?). As happened with Server, DC is likely to undergo constant price increases to 'squeeze' larger customers onto Cloud.
If we don't want to jump to DC or Cloud just yet, my suggestion is lock down Jira and wait for better alternatives. There are no good options now, we have no pressing need to move, so let's just batten down the hatches, save some money and see what alternatives emerge.
This "lock down and wait" approach can be realised in 4 steps:
One more upgrade buys us license slot headroom beyond 2022:
Do not pay for further Server renewals. Atlassian haven't added any serious feature improvements in years, and certainly won't do so now. Bug fixes are nice, but after 18 years of development there aren't many bugs left that affect us and that Atlassian are willing to fix. Atlassian support on its own isn't worth paying for.
On the other hand, we do need ongoing security patches if we are to run a public-facing instance. Which is why:
Implement a new public-facing system for customer support. Perhaps Jira Service Desk (JSD) Cloud where non-agents are free, or ServiceNow.
If we break our Jira active users into employees and customers, we see that employees are growing linearly, whereas customer accounts are increasing non-linearly:
|Employee Jira Users||Customers|
Moving customer support to JSD Cloud means that non-linear growth isn't a problem: we don't pay for customers, only for 'agents'. Moving our customers to a Cloud product should be a net win for security.
Jira averages about 1 'critical' security vulnerability every 6 months (generally a CSRF). If we stop paying Atlassian maintenance fees, or run Jira beyond 2024, we need to mitigate security vulnerabilities ourselves, which we can only realistically do by locking down Jira. Either:
We could further lock down Jira by adding a WAF like mod_security or Cloudflare, so that security vulnerabilities we learn of can be mitigated at the HTTP layer.
With customers out of the picture and Jira locked down to employees, we can take our time evaluating Jira Server alternatives.
Realistically, Jira Cloud might still end up being our best option. Even if that turns out to be the case, I'd argue that waiting a few years can only benefit us. Today Jira Cloud is an immature, over-priced product, with poor performance, a weak plugin ecosystem and unclear GDPR compliance prospects. Many ecosystem vendors (notably Tempo) are still scrambling to sort out their Server-to-Cloud migration pathways. Yet Atlassian are betting hard on Cloud, and in 5 years' time Jira Cloud will be much more compelling, and the migration process much smoother.
Also, in 5 years time there may be decent competitors. I've been impressed with https://wiki.js.org and xwiki.org as Confluence alternatives. Good Jira alternatives are much scarcer, but there is Youtrack, Gitlab and a host of SaaSes (Asana, Clubhouse). Even Request Tracker is looking less 90s these days and may be an option. I and others will be keeping tabs on alternatives via https://www.goodbyeserver.org/
We now show how the numbers above are derived. Note: the primary source of calculations is a spreadsheet, which I unfortunately cannot publish due to containing Partners-only information:
Before considering costs, we need to know how many users we expect to cater for in future.
Jira has a 2000 User license, with 1463 license slots used as of . License use is increasing each year (despite automatic deactivation after 6 months' inactivity).
This shows that if current growth continues we will hit our 2000-user license limit in early-2022, and will be forced into Jira's next user tier, 10,000 users.
Confluence is also on a 2000 user license, with 650 license slots used as of . Growth appears linear. No 'deactivate inactive user' process is being run yet.
We are on 'advantaged' plans, and we know price increases are coming for 'advantaged' plans on 2/Feb/2021.
Jira's renewal date would be July 2021, and Confluence's would be February 2021.
But, but renewing early before the price increase, we can save a bit of money. This is "Option 3: Renew on server early and lock in your existing price".
So prior to Feb 2, 2021 we should:
Jira will be due for renewal in May 2022, and Confluence in Aug 2022.
We expect we'll need to upgrade our user tier from 2,000 users to 10,000 in 2022. However, Atlassian plan to stop selling such license upgrades after Feb 2, 2022!
So once again we must jump in early, upgrading our user tier before Feb 2, 2022 so we're not stuck on the 2,000 user tier forever.
As for pricing, our 'advantaged' status will have ended on Feb 2, 2021, so the 'New price for advantaged plans' prices from the Future server pricing tables page applies:
The costs in Jan 2022 would thus be:
A user tier upgrade resets the maintenance clock, so our 100-user licenses would expire in Jan 2023. We would again pay:
(assuming Atlassian don't increase the prices again – something we might want to protect against by renewing for 24 months in 2022)
Our licenses last right up to Jan 2024, after which Atlassian end all support.
After 2/Feb/2024 all Server support ends, and we'd have to purchase Data Center licenses annually, at the 'New Atlassian list price' from the future DC pricing tables:
For Jira (3100+ user tier) this means $210,000+. For Confluence (1200 user tier) it means $84,000+.
Plugin licensing for Server will increase by 50% as we move from the 2,000 to 10,000 user tier, followed by a jump as we move to DC:
If we upgrade our licenses to Data Center before 2/Feb/2021, then:
So prices would be:
|Jira||$91,100 assuming 2000-3000 users|
|Confluence||$16,000 ($30,000 current 1001-2000 user DC license of less crossgrade discount of $10,480)||$34,500 assuming 501-1000 users|
Is it worth moving to DC now just to get on the 'advantaged' license plan?
It appears not. We would need to retain our 'advantaged' price tier until 2026 to break even, and it is unlikely to last that long. Atlassian's stated goal with the 'advantaged' tier is to "ease users into list prices over time". I have questioned how long the easing process will go for, but have received no reply.
Atlassian have 4 tiers in their Cloud products: Free, Standard, Premium and Enterprise (see the Pricing page):
The differences between tiers are seen in the business end of the feature table:
The first question to address is whether Jira and Confluence need to comply with GDPR regulations. If so, the only 'tier' of Cloud that could work is Enterprise, which offers 'Data residency'. Even with Enterprise, GDPR compliance is doubtful, as the Standard Contractual Clauses Atlassian depend on may soon be invalidated for the same reasons the EU-US-Privacy Shield was invalidated in July. Someone more versed in our GDPR needs and GDPR in general will need to make a call here.
Jira uses 413Gb of disk space, over the 250Gb limit for Cloud 'Standard', so we'd need a 'Premium' Cloud subscription.
Cloud pricing can be obtained from Atlassian's Cloud pricing calculator for Jira and Confluence. There is no equivalent pricing table that I can find (the Future cloud pricing tables 'New Price New License' column would apply, but there is no table for Cloud Premium). It is best to pick 'Annual' billing cycle, as this works out cheaper per year and also is required for 'loyalty discounts' (more on them below).
Atlassian is offering a Cloud loyalty discount for users migrating from Server or DC to Cloud. The discount schedule is:
thereafter full price.
So our yearly pricing with Cloud would be:
|Year||Discount||Jira Tier||Jira Base Cost||Jira Cost||Confluence Tier||Confluence Base||Confluence Cost||Access Cost||Total|
(Note: figures are from Atlassian's spreadsheet. Prices for Access diverge slightly from the website)
The table below shows the plugins we currently have, and whether there are Cloud equivalents.
Note that Cloud editions of plugins are often limited vs. their Server counterparts. Our biggest plugin worry is ScriptRunner for Jira. Although technically available on Cloud, ScriptRunner is so drastically limited on Cloud that most of our ScriptRunner-based customizations will not be possible.
Also, each plugin available in Cloud will have its own migration story. E.g. Tempo currently has no data importer.
| || ||In Cloud?|
|Trello Connector for Jira Server|
|JIRA Watcher Field||✗|
|JIRA Component Watcher||✗|
|Customer Satisfaction Survey for JIRA||✗|
|eazyBI Reports and Charts for Jira||✗|
|Email This Issue||✓|
|Adaptavist ScriptRunner for JIRA||✓(limitations)|
|TestRail for JIRA Test Management||✓|
|Secure Login for JIRA||✗|
|CucumberStudio - BDD and Test Management for Jira||✓|
|Excel-like Issue Editor for Jira||✓|
|JavaMelody Monitoring Plugin||✗|
|Natural Searchers for JIRA||✗|
Cloud plugins are generally more expensive than Server. E.g. our 2021 plugin spend would go from $19,310 to $89,148:
Atlassian Access is Atlassian's centralized user database for Cloud. It is required if we wish to sync with existing LDAP. Access also provides 2FA, SSO, SAML and other advantages.
Please see the summary at the beginning for comparison of these three options, and my recommendations.