Prices, plan contents and review scores are as of 25 September 2026 unless stated otherwise.
Jira vs ServiceNow is rarely a like-for-like choice. ServiceNow is a workflow platform that treats IT service management (ITSM) as one module among many. Jira Service Management (JSM) is Atlassian's service desk, now sold inside the Atlassian Service Collection and built to sit next to Jira and Confluence. This ServiceNow vs Jira Service Management comparison uses public, dated sources for both products, so you can see where each fits and what a move between them involves. It also answers "Jira Service Desk vs ServiceNow" and "Atlassian vs ServiceNow" searches. In November 2020 Atlassian described JSM as "the next generation of Jira Service Desk" (Atlassian). For the wider market, see our ITSM tools compared hub.
Key takeaways
- ServiceNow's ITSM is quote-only. It now comes in Foundation, Advanced and Prime tiers, and Problem and Change sit in Advanced (ServiceNow, as of 25 Sep 2026).
- JSM lists its prices publicly: $20 per agent per month on Standard and $51.42 on Premium, where Problem and Change live (Atlassian, as of 25 Sep 2026).
- The CMDB models are different. ServiceNow uses a class hierarchy with reconciliation rules. JSM Assets uses flexible object schemas. Plan the mapping before you plan the migration.
- SLA timers and audit history do not transfer cleanly in either direction. Treat them as a design decision, not an afterthought.
The short answer
Verdict: ServiceNow suits large enterprises that run formal ITIL processes across many departments and can fund a platform team. Jira Service Management suits organisations whose service desk works closely with Jira-based development teams and that want published per-agent pricing and faster setup. Both cover core ITSM. The real differences are cost model, data model and how much governance you need.
| Factor | Choose ServiceNow if… | Choose JSM if… |
|---|---|---|
| Organisation size | You are a large enterprise with a dedicated platform team and many service domains (IT, HR, security, facilities) | You are small to mid-size, or a larger company that wants to scale on per-agent pricing (up to 100,000 agents on paid plans) |
| ITIL maturity | You need Problem, Change, Major Incident and CMDB governance under central control | You follow ITIL loosely or are formalising processes step by step |
| Dev integration | Development runs on several tools and IT is the centre of gravity | Engineering already lives in Jira and Confluence |
| Compliance and control | You need fine-grained control over data reconciliation and a single audited record across departments | Atlassian Cloud's certifications and data-residency options meet your requirements (Data Center is no longer sold to new customers) |
What changed in 2026
Both vendors repackaged in the last 12 months, so comparisons written before 2026 are out of date on pricing and AI.
- Atlassian Service Collection. Announced on 7 October 2025, it "unites Jira Service Management, Customer Service Management, and Assets" with Rovo AI agents (Atlassian). JSM is now priced through the collection.
- ServiceNow Foundation / Advanced / Prime. ServiceNow now sells ITSM in three tiers (ServiceNow). A June 2026 analysis by The Cloud People reports that the tiers replaced the legacy Standard, Pro, Pro Plus, Enterprise and Enterprise Plus packages on 9 April 2026. Existing customers keep their current SKUs until a renewal or contract change (The Cloud People, June 2026).
- Jira Data Center end of life. New customers could not buy Data Center subscriptions after 30 March 2026. Existing customers can expand until 30 March 2028. Data Center products, JSM Data Center included, become read-only on 28 March 2029 (Atlassian). If you need a self-managed Atlassian ITSM, that option is closing.
- ServiceNow releases. ServiceNow's latest-release page shows Australia as the current release (ServiceNow, as of 25 Sep 2026). A ServiceNow employee in the Community confirmed Brazil early access for mid-September 2026 and general availability for early November 2026 (ServiceNow Community).
- Moveworks. ServiceNow completed its acquisition of Moveworks on 15 December 2025 (ServiceNow). Moveworks now appears in every ITSM tier.
Jira vs ServiceNow, side by side
Plan contents below come from ServiceNow's ITSM packaging page and Atlassian's Service Collection pricing page, both as of 25 Sep 2026.
| Capability | ServiceNow ITSM | Jira Service Management |
|---|---|---|
| Incident management | Foundation and up; Major Incident and On-Call in Advanced | All plans; "advanced incident" management in Premium |
| Request and catalog | Service Catalog and Request Management in Foundation | Request types, portal, email and chat on all plans |
| Problem management | Advanced and up | Premium and up |
| Change management | Advanced and up; DevOps Change Velocity in Prime | Premium and up (change calendar, risk assessment) |
| Knowledge | Knowledge management on the platform | Embedded knowledge base; Confluence for fuller knowledge |
| SLAs | SLA definitions with start, pause, resume, stop, reset and cancel conditions (ServiceNow docs) | SLA goals by JQL, with calendars and start/pause/stop conditions (Atlassian docs) |
| Reporting | Platform Analytics Advanced and Process Mining in Advanced | Built-in reports; Atlassian Analytics and Data Lake in Enterprise |
| Portal | Service portal and catalog | Help center, custom-branded from Standard |
| Asset / CMDB | Asset Management and CMDB in Foundation | Assets (see the CMDB section for plan differences) |
| Price | Quote only | $0 / $20 / $51.42 per agent per month, Enterprise by quote |
What the table hides. Both products handle the ITIL basics. The gap is depth and governance. ServiceNow puts ITSM, HR, security operations and custom apps on one data model, so a change record can reference the same CI and the same user record that HR or security use. That breadth is why reviewers praise it and why they complain about it. On G2, ServiceNow ITSM scores 4.5/5 from 1,985 reviews. Ease of use and incident management are the most-cited strengths, and the learning curve, cost and complexity are the most-cited drawbacks (G2, as of 25 Sep 2026).
JSM's strength is its closeness to engineering. It runs on the same platform as Jira, so an incident can be linked directly to the Jira work item that fixes it. On G2, JSM scores 4.3/5 from 986 reviews. Reviewers cite ease of use, integrations and automation as strengths, and the learning curve and setup complexity as drawbacks (G2, as of 25 Sep 2026). Both products draw complaints about learning curves, so neither is simple at enterprise scale.
Note the tier gating. Since Atlassian's 2024 repackaging, problem and change management moved to Premium. On ServiceNow they sit in Advanced. If you need full ITIL, compare JSM Premium with ServiceNow Advanced, not the entry tiers.
ServiceNow CMDB vs JSM Assets
This is where the two platforms differ most, and where a migration needs the most design work. If you are looking for the Jira Service Management CMDB, Assets is it.
ServiceNow CMDB is class-based. CIs live in a table hierarchy in which child classes inherit attributes from parent classes. ServiceNow's own example is "a laptop class exists that extends the computer class", which in turn extends the base CI class (ServiceNow docs). A relationship is a parent CI, a child CI and a typed relationship such as Runs On or Depends On, stored in the cmdb_rel_ci table (ServiceNow docs). The Identification and Reconciliation Engine (IRE) uses identification rules to prevent duplicates. Its reconciliation rules decide which data source may update which attribute (ServiceNow docs).
JSM Assets is schema-based. An object schema is "a top-level container or blueprint structure to store assets". It holds object types and objects, which carry attributes and link to each other through references (Atlassian). You design this structure yourself. Atlassian also offers a Common Data Model to standardise that structure. Discovery is basic, detecting "IP-enabled assets". Atlassian points to Lansweeper and Flexera for advanced discovery, and Assets Data Manager to "consolidate, cleanse, and reconcile" data from over 30 import adapters (Atlassian).
| ServiceNow CMDB concept | Closest JSM Assets equivalent | Mapping note |
|---|---|---|
| CI class (e.g. cmdb_ci_server) | Object type | Inherited attributes must be flattened or recreated per object type |
| Class hierarchy | Object type hierarchy within a schema | Decide how deep to go; very deep trees are harder to maintain in Assets |
| CI attribute | Object attribute | Map data types (reference, date, choice) one by one |
| Relationship (cmdb_rel_ci, typed) | Reference attribute with a reference type | Direction and type names need an explicit mapping table |
| IRE identification and reconciliation rules | Data Manager cleansing and reconciliation | Rules do not migrate; rebuild source precedence |
| Discovery / Service Graph Connectors | Basic discovery, Lansweeper, Flexera, import adapters | Re-point discovery before cutover, or the data goes stale |
Plan limits matter too. Atlassian's pricing page lists asset and configuration management from Standard. Its plan-comparison doc lists Assets capacity only for Premium (up to 50,000 objects) and Enterprise (up to 500,000 objects), with add-ons for more (Atlassian, as of 25 Sep 2026). Confirm your object count against the plan you are quoted.
AI compared: Now Assist and AI Agents vs Rovo
Both vendors now include AI in their base ITSM tiers and meter heavy usage.
| ServiceNow | Jira Service Management | |
|---|---|---|
| Entry tier | Now Assist, Virtual Agent and Moveworks for ITSM Foundation | Rovo agents, search and chat from Standard |
| Mid tier | Now Assist and Platform AI Advanced; AI Voice Agents | Virtual service agent (1,000 assisted conversations a month) and AIOps in Premium |
| Top tier | Prime: AI Agents for ITSM, L1 Service Desk AI Specialist, custom AI agents | Enterprise: highest Rovo allowance |
| Usage unit | "Assists" | Rovo credits |
Sources: ServiceNow ITSM packaging; Atlassian pricing; both as of 25 Sep 2026.
ServiceNow. ServiceNow's documentation says AI skills are available at every tier. Building "net-new agents from natural language instructions" requires Prime (ServiceNow docs). Advisory firm UpperEdge reports that Now Assist usage is metered in "assists". Each user gets an annual allotment, and extra packs cost more. UpperEdge also notes that overage pricing is rarely spelled out in standard order forms (UpperEdge, September 2025).
Atlassian. Service Collection plans include 250 Rovo credits per user per month on Standard, 700 on Premium and 1,500 on Enterprise, pooled across the organisation. The credit model took effect on 31 August 2026, and overage billing starts on 3 December 2026 (Atlassian, as of 25 Sep 2026).
The practical point: both vendors now charge for heavy AI use. Model your expected AI volume before you compare licence quotes.
Pricing and total cost of ownership
Jira Service Management pricing is published. As of 25 Sep 2026, Atlassian lists these Service Collection plans, with a 17% saving for annual billing (Atlassian):
| Plan | Price (monthly billing) | Notes |
|---|---|---|
| Free | $0 | Up to 3 agents |
| Standard | $20 per agent per month | Rovo, asset and configuration management, Customer Service Management |
| Premium | $51.42 per agent per month | Problem, change, advanced incident, virtual service agent |
| Enterprise | Contact sales | Annual billing only; Atlassian Analytics, up to 150 sites |
In 2024 Atlassian introduced usage-based charges for Assets objects and virtual agent conversations above included allowances (Atlassian, 29 Oct 2024). Ask for current overage rates in your quote.
ServiceNow pricing is quote-only (ServiceNow). The only public benchmark we use is Vendr's buyer data: a median annual contract value of $129,871 across 109 purchases, ranging from $43,245 to $702,488 (Vendr, last updated February 2026). That figure covers all ServiceNow purchases, not only ITSM, so treat it as context rather than a quote. Our ServiceNow pricing guide goes deeper.
List prices are only part of the cost. Build your total cost of ownership from these factors:
- Licences: agents or fulfillers, tier, AI usage (assists or Rovo credits), Assets object volume.
- Implementation: partner fees, process design, data migration, integration build.
- Admin headcount: ServiceNow estates typically need platform developers and admins. JSM needs Jira admins and automation owners. Reviewers of both products cite the learning curve, so budget for training either way.
- Add-ons: discovery tools, Marketplace or Store apps, extra environments, analytics.
- Change over time: upgrade testing, renewal uplifts, and legacy-SKU transitions on ServiceNow.
ServiceNow vs Jira: which should you choose?
Answer these five questions in order. The first two usually decide it.
- How many service domains will share the platform? If IT, HR, security and facilities all need one record system with shared data, ServiceNow's breadth is the point. If the need is mainly IT and engineering support, JSM covers it with less overhead.
- Where does engineering work? If developers are already in Jira, JSM links incidents and changes to the work that resolves them without integration work.
- How strict is your ITIL practice? Formal Change Advisory Boards, major incident runbooks and CMDB governance with reconciliation rules favour ServiceNow Advanced or Prime. Lighter-touch practices fit JSM Premium.
- What can you staff? A ServiceNow estate usually needs a platform team. If you cannot staff one, factor partner costs into the comparison.
- What does the three-year cost look like? Compare JSM Premium list prices × agents against a real ServiceNow quote, plus the TCO factors above.
If neither product fits, see our ServiceNow alternatives roundup, or Zendesk vs Jira for customer-facing support.
Migrating between ServiceNow and JSM
Moves happen in both directions. The usual reasons are cost, closeness to Jira-based engineering, or the need for broader platform coverage. JSM Data Center customers facing the 2029 read-only date also have a decision to make. Either way, the work falls into three buckets.
| ServiceNow → JSM | JSM → ServiceNow | |
|---|---|---|
| Usually transfers | Incidents, requests, problems, changes as work items; comments and work notes (as public or internal comments); attachments; users and groups; KB articles to the JSM knowledge base or Confluence | Work items to incident, request, problem and change records; comments to comments and work notes; attachments; users; Confluence pages to Knowledge articles |
| Must be rebuilt | Flow Designer flows and business rules → Jira Automation rules; SLA definitions → SLA goals and calendars; assignment groups → teams and queues; approvals → approval steps in workflows | Automation rules → Flow Designer or business rules; SLA goals → SLA definitions; queues → assignment groups; approval steps → approval rules |
| At risk | Full audit history; running SLA timers; CI class hierarchy and relationship types; record links between incidents, problems, changes and CIs | Issue history and changelog; SLA elapsed time; Assets reference attributes that must become typed CMDB relationships |
Why SLAs and history are the hard part. JSM calculates SLAs from issue history. Atlassian's own knowledge base notes that "Jira Service Management calculates SLA based on the issue history". Imported issues have no history beyond creation, so SLAs on closed imported issues can keep counting until you exclude them or transition them again (Atlassian). ServiceNow attaches task SLA records when start conditions are met on a live record (ServiceNow docs). In both directions, historical SLA results usually need to be kept as data (fields or an archive), not recalculated.
What drives effort. We do not give a timeline, because no neutral source supports one. Partner claims vary widely: one Atlassian partner states "under 2 months" to go live on JSM against "5 to 18 months" for ServiceNow, and cites no sources for either (Deviniti, 8 Jul 2025). What actually drives effort:
- Record volume and years of history in scope.
- Number of custom tables, fields and scripted business rules.
- CMDB size, class depth and relationship count.
- Number of integrations (monitoring, HR, identity, CI/CD).
- Whether audit history must be kept in the new system or can stay in an archive.
Migration checklist
- Inventory record types, custom fields, tables and volumes by year.
- Decide what history is in scope and what goes to a read-only archive.
- Write the CMDB-to-Assets (or Assets-to-CMDB) mapping: classes, attributes, relationship types.
- Map users, groups, roles and assignment logic.
- Rebuild SLA policies and calendars. Decide how historical SLA results are stored.
- Rebuild automations, approvals and notifications, and test them against real cases.
- Migrate knowledge articles and fix internal links.
- Run at least one full trial migration and reconcile record counts and links.
- Agree a freeze window, cutover runbook and rollback criteria.
- Re-point integrations, email channels and discovery on cutover day.
- Run hypercare and reconcile again before retiring the old platform.
FAQ
Methodology
This comparison uses only public sources: vendor pricing and documentation pages, vendor announcements, the ServiceNow Community, G2 review data, Vendr buyer data and one named advisory firm. All were checked on 25 September 2026. We did not run hands-on tests for this article. Vendor claims are attributed to the vendor or partner that made them. No vendor reviewed or sponsored this article. Prices and plan contents change often, so check the named source before you rely on a figure.