
All figures use public list prices read on 12 October 2026 and the Reserve Bank's 9 October 2026 exchange rates (A$1 = US$0.6979 and £0.5270). Your quotes will differ, especially on the ServiceNow side, so use the model to frame the decision. It doesn't replace a quote. For a feature-by-feature view of the two platforms, read our Jira Service Management vs ServiceNow comparison.
What does each platform charge for, and who needs a licence?
The two vendors license different people, which matters more than the headline price per seat.
- Jira Service Management charges per agent. Atlassian now prices JSM under its Service Collection plans. You pay for agents, the people who work on requests. Customers who raise requests are unlimited and free. Approvers don't need a licence either: Atlassian's approvals documentation says they only have to be customers of the service space.
- ServiceNow charges per fulfiller, plus paid approver roles. Fulfillers are the users who work on records. Requesters are generally not charged in ITSM. But users who approve requests and view reports, without resolving anything, need a Business Stakeholder licence. Vendr's ServiceNow buying guide notes that fulfillers are typically the most expensive licence type.
So a ServiceNow estate with 100 fulfillers and 40 managers who only approve changes and purchases pays for 140 people. The same team on JSM pays for 100.
How much does Jira Service Management cost in AUD?
Atlassian publishes its prices. The cloud pricing tables list annual Service Collection prices by agent tier. These took effect on 13 October 2026 (Pacific time). Converted at the RBA rate, before GST:
| Agents | Standard (USD/yr) | Standard (A$/yr) | Premium (USD/yr) | Premium (A$/yr) |
|---|---|---|---|---|
| 50 | 11,000 | 15,760 | 28,000 | 40,120 |
| 100 | 21,000 | 30,090 | 55,000 | 78,810 |
| 200 | 34,500 | 49,430 | 90,500 | 129,670 |
At 100 agents, Premium works out to about A$66 per agent per month. The Enterprise plan starts at a 300-agent tier, at US$185,000 a year. Three points affect the AUD number you budget:
- Atlassian bills cloud in US dollars. Its purchasing FAQ says it can't quote or invoice AUD for orders that contain cloud products. Atlassian adds 10% GST, and exchange-rate moves flow straight into your budget. A partner can invoice you in AUD instead. That is part of our Atlassian licensing service.
- Usage above your allowance is metered from 3 December 2026. Service Collection Standard includes 3,000 automation steps and 250 Rovo credits per agent per month. Premium includes 6,500 steps and 700 credits. Atlassian's usage-based pricing page lists the meters. Our guide to Atlassian Cloud pricing in AUD explains how to model them.
- Some capacity is priced separately. The pricing tables list extra Assets objects at US$1,000 a year per 5,000 objects. Extra virtual service agent conversations cost US$0.30 each for the first 12,000 on monthly billing. Marketplace apps are extra, and their user tier must match your agent tier.
How much does ServiceNow ITSM cost?
ServiceNow doesn't publish prices. Its ITSM pricing page now lists three packages, Foundation, Advanced and Prime, each with a "Get Custom Quote" button. That makes any public figure a reference point, not a quote.
The most detailed public price list we found is a UK government G-Cloud price list. It was lodged by the reseller SCC on the UK Digital Marketplace in June 2025 and uses ServiceNow's earlier package names. It lists base prices per fulfiller user of £80 for ITSM Standard, £120 for ITSM Professional and £180 for ITSM Enterprise, and £28 for a Business Stakeholder user. The list doesn't state the billing period. Read as monthly per user, which is how ServiceNow subscriptions are usually expressed, it converts to:
| Licence | Per user per month (A$) | 100 users per year (A$) |
|---|---|---|
| ITSM Standard fulfiller | 152 | 182,160 |
| ITSM Professional fulfiller | 228 | 273,240 |
| ITSM Enterprise fulfiller | 342 | 409,870 |
| Business Stakeholder (approver) | 53 | 63,760 |
ServiceNow ITSM Professional is the closest match to JSM Premium. Both include change management, problem management and a virtual agent. Real contracts come in below list. Vendr reports a median ServiceNow annual contract value of US$129,871 across 109 purchases, ranging from US$43,245 to US$702,488. It also says buyers who evaluate alternatives such as Jira Service Management tend to get better discounts. Even at a 50% discount, though, 100 ITSM Professional fulfillers would list at about A$137,000 a year. That is well above JSM Premium for the same 100 agents.
What does it cost to run each platform?
After licences, the next biggest line is the people who administer and change the platform. ServiceNow work usually needs a developer with ServiceNow-specific skills. JSM is mostly configured without code by an Atlassian administrator, although integrations and scripted automation still need technical skills.
SEEK's salary data, refreshed on 1 October 2026, puts the average ServiceNow developer salary at A$115,000 to A$135,000. SEEK has no Jira administrator category. The closest is systems administrator, at A$95,000 to A$115,000. SEEK notes that some advertised salaries include superannuation and some don't. Adding the 12% super guarantee to each midpoint gives about A$140,000 for a ServiceNow developer and A$117,600 for an administrator, before other on-costs.
Team size depends more on how customised your ServiceNow instance is than on agent numbers. Count the custom tables, scripted business rules and integrations you would need to rebuild. That count drives both your run cost today and your migration cost.
What does a three-year TCO look like for 100 agents?
Here is a worked example for an Australian organisation with 100 agents and 40 managers who approve requests but don't work tickets. It compares ServiceNow ITSM Professional at three discount levels with JSM Premium at list price. The model assumes one platform specialist on each side, at the salary midpoints above. That is our assumption, so replace it with your own headcount.
| Annual cost (A$, ex GST) | ServiceNow, list | ServiceNow, 25% off | ServiceNow, 50% off | JSM Premium, list |
|---|---|---|---|---|
| Agent or fulfiller licences | 273,240 | 204,930 | 136,620 | 78,810 |
| Approver licences (40) | 25,500 | 19,130 | 12,750 | 0 |
| Platform specialist (1 FTE incl. super) | 140,000 | 140,000 | 140,000 | 117,600 |
| Annual run cost | 438,700 | 364,100 | 289,400 | 196,400 |
| Three-year run cost | 1,316,000 | 1,092,000 | 868,000 | 589,000 |
| Three-year gap vs JSM | 727,000 | 503,000 | 279,000 | n/a |
The bottom row is the number that matters. It is the most you can spend on migration, overlap licences and change management and still break even within three years. At a 50% ServiceNow discount, that budget is about A$279,000. A migration that rebuilds heavy customisation could use most of it. At list price, the case is much stronger.
The model leaves out JSM metered usage above allowances, Marketplace apps, ServiceNow add-ons (Discovery and Integration Hub transactions are licensed separately) and exchange-rate movement. Add the ones that apply to you before you take a number to finance.
Which migration costs get missed?
The one-off costs sit outside the run-cost model, and they decide whether the gap is real. Budget for each of these:
- Licence overlap. You will run both platforms during build, testing and cutover. Check your ServiceNow order form for the term, auto-renewal date and notice period, then plan cutover to land before renewal. Vendr reports that most ServiceNow contracts auto-renew, often on three-year enterprise terms.
- Process redesign, not just data mapping. Rebuilding every ServiceNow workflow as it is copies years of workarounds. Decide which request types, approval steps and SLAs you actually need before anyone builds them.
- Custom applications. Custom tables and scoped apps on ServiceNow have no direct JSM equivalent. Each one needs a decision: rebuild in JSM, move to Jira, replace with a Marketplace app or retire.
- CMDB and assets. Moving configuration items and relationships into JSM Assets is often the hardest data migration. Check your object count against your plan's allowance and the extra-object pricing above.
- Integrations. Identity, monitoring, HR, procurement and chat integrations all need re-pointing. Price each one, because they are where timelines slip.
- Ticket history. Decide how much history to migrate and how much to archive in a read-only, searchable store. Migrating everything costs more and rarely helps agents.
- Training and adoption. Agents, approvers and requesters all see a new interface. Plan knowledge base migration and portal design as part of the change, not after it.
Our Atlassian Cloud migration guide covers the Australian hosting, data residency and IRAP questions that also apply when you move service management to Atlassian Cloud.
When is staying on ServiceNow the cheaper choice?
A lower licence bill doesn't always mean a lower total cost. ServiceNow is likely to stay cheaper over three years when:
- ITSM is one module among many. If HR service delivery, security operations, ITOM and custom apps all run on the same instance, moving only ITSM leaves you paying for the platform anyway, plus a second tool.
- Customisation is deep and still needed. Hundreds of scripted rules and custom tables can push migration cost past the three-year gap.
- You have just signed a multi-year term. If you are in year one of three, the overlap cost alone can cancel the saving. Use the time to prepare and run the model again before renewal.
- Your negotiated price is already far below list. Run the model with your actual price per fulfiller, not the list figures above.
Some organisations run both, with ServiceNow for central IT and JSM for software and business teams. That can work, but you pay for two platforms and the integration between them.
How do we build our own TCO case?
Take these numbers from your own systems and contracts, then run the model:
- Active fulfillers and Business Stakeholder users over the last 90 days, from ServiceNow's subscription management, compared with what you pay for.
- Your actual price per fulfiller and approver, contract end date and renewal notice period.
- Modules and add-ons in use beyond ITSM.
- Count of custom tables, scripted business rules, integrations and catalogue items.
- CMDB size in configuration items, to check against JSM Assets allowances.
- Monthly automation runs and virtual agent conversations, to estimate JSM metered usage.
- Platform team headcount and cost, including contractors.
Often the first finding is that you are paying for inactive fulfillers. Fixing that cuts the ServiceNow side of the model, so do it first and compare like with like.
Frequently asked questions
Is Jira Service Management cheaper than ServiceNow?
On licences, yes, by a wide margin at list prices: about A$79,000 a year for 100 JSM Premium agents against about A$273,000 for 100 ServiceNow ITSM Professional fulfillers. Total cost depends on your negotiated ServiceNow price, how much customisation must be rebuilt, and whether other modules share the instance.
Do approvers need a Jira Service Management licence?
No. Atlassian's documentation says approvers don't need a JSM licence, provided they are customers of the service space. On ServiceNow, approvers who aren't fulfillers typically need a Business Stakeholder licence.
Is Jira Service Management priced in Australian dollars?
Not by Atlassian. It bills cloud subscriptions in US dollars and adds 10% GST for Australian customers. Buying through an Atlassian partner can give you an AUD invoice with the currency risk handled.
Get a TCO model built on your numbers
Great Minds is an Atlassian Silver Solution Partner based in Sydney. We design and implement Jira Service Management, run migrations to Atlassian Cloud and handle licensing with AUD invoicing. For a global appliance manufacturer, we ran three proof-of-concept builds in a sandbox, tested against agreed success criteria, before taking Jira and Confluence live.
If your ServiceNow renewal is within the next 12 months, talk to us about a cost model. We'll build the three-year comparison from your fulfiller counts, contract terms and customisation inventory, so you can decide before the renewal notice date.


