Which is the best ITSM system?

It depends on the size and process maturity of the organisation. For mid-sized Nordic IT organisations, Freshservice offers the best balance of ITIL support and simplicity. If you need full process coverage without an enterprise budget, HaloITSM is strongest. For large groups with an in-house platform team the choice is between ServiceNow and BMC Helix. In the public sector you will most often meet TOPdesk, and if budget is decisive, ManageEngine is cheapest on the licence line.

What is the difference between an ITSM system and a project tool?

They solve entirely different problems. An ITSM system manages IT services and requests according to ITIL – incidents, problems, changes, requests and assets. A project management tool such as Asana, Monday.com or Linear manages projects, tasks and collaboration. They have different vendors and should not be compared against each other. A common procurement mistake is mixing requirements from both categories.

Is Jira Service Management cheaper than Freshservice?

On the licence line yes – JSM Standard sits at roughly half of Freshservice Pro at public list price. But Standard lacks change management, CAB, risk assessment and an uptime SLA, so the tier matching an ITSM requirement is Premium. On top of that, Atlassian’s own Forrester study assumes at least 1.5 FTE in ongoing operations, SSO via Atlassian Guard is billed across every user in your whole Atlassian estate, and Marketplace apps are billed on the site’s user count. Compare at the tier that meets your requirements, plus labour – not on the base licence.

Is ServiceNow worth the price?

For organisations that actually use the breadth, yes. ServiceNow becomes expensive when it is bought for a requirements list and then used as a ticketing system – then you pay for a platform and get a tool. Two things make the calculation hard: modules are priced in different metering units, and the subscription is combined with consumption. Ask for a written price based on your own volumes, and calculate total cost including operations over three years before comparing against HaloITSM and Freshservice.

Do we need ITIL to implement an ITSM system?

No. ITIL is a framework of good practice, not a requirement. Most organisations get a long way with incident and request management, and should introduce problem, change and configuration management only once someone owns those processes. Activating the whole framework from day one is the most common reason a rollout stalls.

What does an ITSM system cost?

These systems are usually priced per agent and month, and the range between the mid-market tools and the enterprise platforms is very wide. List price says little, however: asset management, ESM modules and AI are usually add-ons, and enterprise agreements are negotiated individually. Calculate total cost over three years including implementation and operations – we are happy to produce a comparison in SEK.

How long does it take to implement an ITSM system?

A basic implementation with a request flow, categories and a self-service portal takes two to four weeks in Freshservice, and considerably longer in the larger platforms. Full ITIL coverage with asset and change management takes closer to two or three months, and a ServiceNow or BMC rollout in a large organisation is measured in quarters rather than weeks.

Can we switch ITSM system without losing our history?

Yes. Requests, categories, users, assets, attachments and comments can normally be migrated in a structured way. What requires most thought is mapping current statuses, fields and categories to the new system’s structure. We always run the migration in a test environment first so nothing is lost.

ITSM systems 2026: 8 tools compared

We compare eight ITSM systems on strengths, weaknesses, public list prices – and on what a quote rarely states: how much in-house operations effort they need and how long they take to go live.

Quick answer

An ITSM system supports the IT organisation’s processes for incidents, problems, changes, requests and assets. ServiceNow, BMC and Ivanti dominate the enterprise segment but require an in-house platform team. For mid-sized Nordic IT organisations, Freshservice offers the best balance of ITIL support and simplicity, while HaloITSM goes deepest on process coverage and TOPdesk is most common in the public sector.

What decides the choice of ITSM system?

How mature your processes actually are. A tool with full ITIL coverage delivers nothing if nobody owns the processes. Buy for the maturity you will have in twelve months, not the one you wish you had.
Whether you have an in-house platform team. ServiceNow, BMC and Ivanti effectively assume someone works full time on the platform. Without that resource they cost more than the price tag suggests.
Asset management and the CMDB. This is where the differences are largest and the costs hide. Check whether asset management is included or a separate module before comparing prices.
Should ITSM cover only IT, or the whole business? Enterprise service management – HR, finance and facilities in one tool – is the strongest argument for ServiceNow and the weakest reason to pick a narrower tool.
Data residency and procurement requirements. For the Swedish public sector, data residency, contract language and the vendor’s local presence often decide which systems can even be evaluated.

“The most expensive mismatch we see is an organisation buying enterprise ITSM because the requirements list said ITIL, then using ten per cent of it. The tool was not wrong – the requirements list described a process that was never introduced.”
— Scaly’s ITSM consultants

Comparison table: eight ITSM systems at a glance

System	Fits	Strengths	Weaknesses	Included vs extra	Operations and time to live	Public list price
ServiceNow	Groups with an in-house platform team and ambitions to take service beyond IT.	Unmatched platform depth – ITSM, ITOM, ITAM, HR and security in one engine No CIO is questioned for choosing it Scales to tens of thousands of users Strong Swedish partner network	Modules are priced separately – what is included elsewhere is its own licence here Priced in several different metering units depending on module, so two quotes rarely compare directly Subscription is combined with usage meters – cost is hard to forecast before volumes are known Business approvers are their own user type with their own cost	Portfolio management and integration platform: separate licences Several parallel metering units per module Consumption on top of the subscription	Assumes a platform owner, analyst and developer Implementation measured in quarters and consulting budget Upgrades are projects	No public price ask for a written quote
BMC Helix ITSM	Operations-heavy organisations with complex, mixed infrastructure – manufacturing, banking, telecom.	Links incidents to actual service impact, not just to tickets Deep CMDB and discovery AIOps genuinely used in operations Handles mainframe and legacy systems	Implementation measured in quarters The interface feels a generation behind the cloud-native tools Almost no partner presence in the Nordics Skills hard to recruit in Sweden	CMDB, discovery and AIOps included Modules beyond ITSM priced separately	Dedicated team 6–12 months to live You are effectively on your own in the Nordics	No public price
Jira Service Management	IT and support teams close to development, where Jira is already running and developers keep it.	Developers are already there – one tool fewer to roll out Standard is roughly half of Freshservice Pro at list price Up to 300 help centres per site on Premium Knowledge base without a Confluence licence, and Assets Discovery is free	Standard lacks change management, CAB, risk assessment and an uptime SLA – processes require Premium Multiple parallel identity providers require Enterprise, which has no public price and an unpublished minimum size SSO via Atlassian Guard is billed on all unique users across your entire Atlassian estate Marketplace apps are billed on the site’s user count, not the app’s	Assets caps: Standard 5,000 objects, Premium 50,000 Guard (SSO): USD 4.20/user/month Virtual agent: 1,000 conversations/month, then USD 0.30 each	Atlassian’s own Forrester study: at least 1.5 FTE ongoing, verbatim one employee focused on JSM Same study: 9-month implementation with four FTEs Licence = 46% of three-year cost, labour 54%	Standard USD 10,300/yr Premium USD 26,000/yr (26–50 agents)
HaloITSM	Heavy ITIL requirements, on-premise requirements, or a customer wanting everything configurable in detail.	Everything in a single tier – no feature split to negotiate Extremely configurable for those with time and skills Handles on-premise and special hosting requirements Nordic implementation via Scaly	Configurability costs time – custom reports require SQL knowledge Onboarding is mandatory per the vendor’s own pricing page, at a quoted price The virtual agent runs via a third party, not natively Smaller product organisation than the listed competitors	One tier, everything included Onboarding is extra, quote-based Virtual agent via third party	Process owner + part time 4–8 weeks to live SQL skills needed for custom reports	GBP 69/agent/month single tier
Freshservice	Internal IT and service desks with 3–50 technicians wanting ITIL support without starting a platform project.	Only agents are licensed – everyone who submits a request is free SSO and SAML included, up to 99 parallel SSO configurations Change, problem and release already on Pro Nordic implementation and support via Scaly	Live translation requires Freddy Copilot at USD 29/agent/month – it is not included Asset management on Pro holds 100 ITAM units; a server counts as four. Larger needs are quote-based The portal cap follows the workspace cap, normally 25 – not unlimited Freddy AI Agent, sandbox and audit logs are Enterprise	SSO, requesters and change included Orchestration: 5,000 transactions/month on Pro, then USD 250 per 1,000 Freddy Copilot: USD 29/agent/month	Part time is enough 2–4 weeks to live Upgrades happen without you doing anything	Starter 19 · Growth 49 Pro USD 99 (EUR 84 in EU) Enterprise on request
Ivanti	IT departments that bought a broader suite where ticket handling was one module among several.	Broad reach into endpoint management and security Established in larger IT organisations with existing agreements Strong licence and asset management Cloud or self-hosted	The service desk is rarely the best part of the package Configuration changes often require a consultant Module-based – assets and tickets connect less well than in a unified platform Support and maintenance are added as separate services	Modular suite, parts priced individually Professional services often necessary	Longer implementations A learning curve that consumes consulting time Thin Nordic partner presence	Quote-based
TOPdesk	Swedish municipalities, schools, property companies or healthcare-adjacent operations – often ten years in the same system.	Established and safe, with a long Nordic track record Broader than IT – property and facilities often sit in the same system Local presence and a well-known model in the public sector Low perceived risk in renewing	Self-service and the employee experience feel dated AI and automation are thin next to the leaders Cross-system orchestration, such as automated on- and offboarding, is weak If facilities sit in the same instance, a switch is organisational rather than technical	Facilities and property can share the system Module split varies by agreement	Often already staffed after many years The switch is bigger than the ITSM question if facilities are included	No public list price
ManageEngine ServiceDesk Plus	Technically driven IT teams on a limited budget wanting a lot of capability for little money.	Lowest price in the comparison, and they are transparent about it A long feature list covering most of what a requirements spec asks for A broad surrounding IT suite with monitoring and endpoint management Cloud or self-hosted	Cross-system automation is built in the vendor’s own scripting language rather than with ready-made connectors The system is effectively owned by one technician who gains a second job Upgrades are repeatedly described as a source of disruption No Nordic partner taking responsibility for the rollout	Public price list Automation requires your own scripting The broad suite is bought module by module	Count hours per week × 52 × hourly cost – that line never appears in the quote Key-person risk: one person knows the system	Public price list, lowest in the comparison

List prices are the vendors’ own public annual-billing prices, checked 2026-08-19 – verify the current price before deciding. Several vendors publish no price at all, which is itself a procurement question. <strong>Operations effort and time to live draw on published sources where they exist</strong> (for Jira Service Management, on Atlassian’s own Forrester study) and otherwise on Scaly’s estimates from Nordic implementations. It is the line item most often missing from a business case.

The eight ITSM systems in detail

ServiceNow – the enterprise standard

ServiceNow is the reference point in the category and the system others are compared against. The Now Platform reaches far beyond IT: HR, finance, legal and facilities can run as services in the same tool, with shared governance and reporting. For a group wanting one platform for all internal service, nothing matches the breadth.

Bäst för: large organisations with an in-house platform team and ambitions to take ITSM further into enterprise service management.

Tänk på: the cost is in a class of its own, and it shows up not only in licensing but in operations. Without at least one person working full time on the platform, ServiceNow quickly becomes an expensive disappointment. See our <a href="/en/servicenow-alternative">ServiceNow alternative</a>.

BMC Helix ITSM – for operations-heavy estates

BMC comes from the world of operations monitoring, and it shows. Helix ITSM is strongest where the infrastructure is complex and heterogeneous – mainframe alongside cloud, thousands of configuration items, and a need to link incidents to actual service impact. Discovery and the CMDB are among the best on the market, and the AIOps side is genuinely mature.

Bäst för: manufacturing, banking and telecom with heavy, complex infrastructure and existing BMC history.

Tänk på: complexity is high in both implementation and operations, the interface feels heavier than the cloud-native competitors, and Nordic partner presence is thin – expect to run it internally or through an international partner.

Ivanti Neurons for ITSM – ITSM and endpoint management in one

Ivanti’s distinguishing feature is that ITSM and endpoint management come from the same vendor. If you already run Ivanti for client operations, patching and licence management, the link to ticket handling is tighter than an integration can give – the assets in the CMDB are the same assets endpoint management actually controls.

Bäst för: IT organisations wanting to consolidate ITSM and endpoint management with one vendor.

Tänk på: the portfolio grew through acquisitions and feels uneven across product areas. Ivanti has also had publicised security incidents in parts of its portfolio other than ITSM – for the public sector that is worth raising in vendor assessment: not disqualifying, but not to be overlooked either.

HaloITSM – the deepest coverage per krona

HaloITSM covers virtually the whole ITIL framework and has very strong contract, asset and SLA management. The difference from the enterprise alternatives is that most of it is in the base licence rather than sold as modules, which makes total cost predictable for organisations that genuinely need the breadth but lack an enterprise budget.

Bäst för: organisations with formalised IT processes wanting full ITIL coverage without ServiceNow’s price tag.

Tänk på: the power costs configuration time, and without a process owner the system becomes heavier than the problem it was meant to solve. The brand is also less recognised in Swedish procurement, which sometimes requires more internal justification.

Freshservice – the best balance for mid-sized IT organisations

Freshservice is built for internal service desks and covers incident, problem, change and request management plus asset management, without the administrative weight the large platforms bring. An IT department of a few people can handle an entire organisation’s requests, and the self-service portal removes a significant share of the ticket flow before it reaches a technician.

Bäst för: internal IT departments and service desks wanting ITIL support without starting a platform project.

Tänk på: asset management and the more advanced AI features sit in higher tiers, and in very large, process-heavy organisations it reaches a ceiling where Halo, BMC or ServiceNow keep going. Read more about <a href="/en/services/freshservice">Freshservice</a>.

Jira Service Management – natural if you already run Jira

For organisations where development lives in Jira, Service Management is the logical choice: support requests and development work connect in the same tool, making escalation from ticket to bug fix straightforward. Pricing is competitive, particularly for smaller teams.

Bäst för: IT and support teams close to the development organisation, above all in tech companies.

Tänk på: outside IT it often feels developer-oriented, asset management is weaker than in the purpose-built ITSM tools, and configuration takes more than it first appears. Scaly is not an Atlassian partner – we include it here because it belongs in the comparison.

TOPdesk – the Nordic classic

TOPdesk has a long Nordic track record, particularly among municipalities, schools, property companies and healthcare-adjacent operations. Many have run it for ten years or more, often with property and facilities in the same instance. That makes it a safe choice rarely questioned – and a switch that becomes organisational rather than technical.

Bäst för: the public sector and property-adjacent operations wanting IT and facilities in one shared system.

Tänk på: self-service and the employee experience are where the gap to the leaders shows most clearly, and AI and cross-system orchestration are thin. If facilities sit in the same instance, the decision also moves outside IT.

ManageEngine ServiceDesk Plus – cheapest, but the time costs

ManageEngine comes from the same house as Zoho and is sold the same way: a lot of capability for little money, with a public price list and a broad surrounding IT suite. For a technically driven IT team on a limited budget it is a rational choice, and most who pick it do so deliberately.

Bäst för: technically driven IT teams on a limited budget, particularly those already using other tools in the same suite.

Tänk på: cross-system automation is built in the vendor’s own scripting language rather than with ready-made connectors, and the system ends up owned by one technician who gains a second job. Count hours per week times 52 times hourly cost – that line never appears in the quote, and there is no Nordic partner to hand it to.

How to choose the right ITSM system

Under 50 technicians and you want to be live within a month: Freshservice is the starting point. Compare against HaloITSM if your processes are already formalised.
Full ITIL coverage but no enterprise budget: HaloITSM gives the most process depth per krona. Just make sure someone owns the processes before you buy.
Over 2,000 users with an in-house platform team: ServiceNow against BMC Helix. Let infrastructure complexity decide – if it is heavy and heterogeneous, BMC holds up well.
You want to consolidate ITSM and endpoint management: evaluate Ivanti, but include the vendor’s security track record in the assessment.
Development already lives in Jira: Jira Service Management is cheapest in practice – but compare asset management carefully against Freshservice.
You are sitting on a ten-year-old TOPdesk agreement: compare on self-service and orchestration, not on the feature list – that is where the gap sits. If facilities share the instance, the switch is organisational, not technical.
Requests come from customers, not your own employees: then what you need is not ITSM but a customer service system.

ITSM system, ticketing system or project tool – which is which?

Three categories that get confused in procurement and that have completely different vendors. An ITSM system supports the IT organisation’s ITIL processes – incidents, problems, changes and assets. That is this page, and the vendors are ServiceNow, BMC, Jira Service Management, Halo, Freshservice, Ivanti, TOPdesk and ManageEngine. A ticketing system is the broader term that also covers requests from customers and business flows – see our ticketing system comparison. Project management tools are an entirely different category: Asana, Monday.com, ClickUp and Linear handle projects and tasks, not IT services, and do not belong in an ITSM comparison – we compare those in Jira alternatives and Monday.com alternatives instead. A common mistake in requirements gathering is mixing the three; the result is a list no vendor can answer straight.

Procuring an ITSM system?

We review your process maturity, volumes and integrations and give you a straight answer on which system fits – including when the answer is one we do not sell. The consultation is free and takes about 30 minutes.

Book a free consultation Take a free ITSM assessment

Read on

Frequently asked questions about ITSM systems

Which is the best ITSM system?: It depends on the size and process maturity of the organisation. For mid-sized Nordic IT organisations, Freshservice offers the best balance of ITIL support and simplicity. If you need full process coverage without an enterprise budget, HaloITSM is strongest. For large groups with an in-house platform team the choice is between ServiceNow and BMC Helix. In the public sector you will most often meet TOPdesk, and if budget is decisive, ManageEngine is cheapest on the licence line.
What is the difference between an ITSM system and a project tool?: They solve entirely different problems. An ITSM system manages IT services and requests according to ITIL – incidents, problems, changes, requests and assets. A project management tool such as Asana, Monday.com or Linear manages projects, tasks and collaboration. They have different vendors and should not be compared against each other. A common procurement mistake is mixing requirements from both categories.
Is Jira Service Management cheaper than Freshservice?: On the licence line yes – JSM Standard sits at roughly half of Freshservice Pro at public list price. But Standard lacks change management, CAB, risk assessment and an uptime SLA, so the tier matching an ITSM requirement is Premium. On top of that, Atlassian’s own Forrester study assumes at least 1.5 FTE in ongoing operations, SSO via Atlassian Guard is billed across every user in your whole Atlassian estate, and Marketplace apps are billed on the site’s user count. Compare at the tier that meets your requirements, plus labour – not on the base licence.
Is ServiceNow worth the price?: For organisations that actually use the breadth, yes. ServiceNow becomes expensive when it is bought for a requirements list and then used as a ticketing system – then you pay for a platform and get a tool. Two things make the calculation hard: modules are priced in different metering units, and the subscription is combined with consumption. Ask for a written price based on your own volumes, and calculate total cost including operations over three years before comparing against HaloITSM and Freshservice.
Do we need ITIL to implement an ITSM system?: No. ITIL is a framework of good practice, not a requirement. Most organisations get a long way with incident and request management, and should introduce problem, change and configuration management only once someone owns those processes. Activating the whole framework from day one is the most common reason a rollout stalls.
What does an ITSM system cost?: These systems are usually priced per agent and month, and the range between the mid-market tools and the enterprise platforms is very wide. List price says little, however: asset management, ESM modules and AI are usually add-ons, and enterprise agreements are negotiated individually. Calculate total cost over three years including implementation and operations – we are happy to produce a comparison in SEK.
How long does it take to implement an ITSM system?: A basic implementation with a request flow, categories and a self-service portal takes two to four weeks in Freshservice, and considerably longer in the larger platforms. Full ITIL coverage with asset and change management takes closer to two or three months, and a ServiceNow or BMC rollout in a large organisation is measured in quarters rather than weeks.
Can we switch ITSM system without losing our history?: Yes. Requests, categories, users, assets, attachments and comments can normally be migrated in a structured way. What requires most thought is mapping current statuses, fields and categories to the new system’s structure. We always run the migration in a test environment first so nothing is lost.