Why organisations leave ServiceNow
Organisations do not usually replace ServiceNow because it stopped working. They replace it because the commercial model, the jurisdiction, or the fit stopped matching what they actually need.
After thirty years in Nordic IT — including harmonising ServiceNow across seven Nordic countries — I have seen this decision made well and made badly. The organisations that get it right are the ones that name the real reason before they start looking at alternatives.
There are four.
1. Licence cost that grows faster than the value
The pattern is consistent. The initial contract is competitive. Then fulfiller counts grow, more product lines get switched on, and at renewal the number is materially higher than the business case assumed.
What makes this hard to argue against internally is that each individual increase was justified. The problem is cumulative: the platform bill grows on a different curve from the value it returns, and by year four or five the gap is visible to the CFO even if it is not visible to IT.
The question to ask is not "is this expensive?" It is: if we were buying this today, for what we actually use, would we buy this?
2. Lock-in created by your own customisation
This is the one organisations create themselves.
Heavy customisation makes the platform fit the organisation — and simultaneously makes it very hard to leave. Business logic ends up encoded in the platform rather than documented anywhere. Upgrades become projects. The people who understand why a workflow behaves the way it does move on.
The tell is simple: if nobody can describe what a given workflow does without opening the platform to look, the process knowledge lives in the tool, not in the organisation. That is a dependency, and it deepens every year.
3. US jurisdiction and the CLOUD Act
ServiceNow is a US-headquartered company. Under the US CLOUD Act (2018), US authorities can compel US-headquartered providers to produce data under their control, regardless of which region it is stored in. EU data residency does not, by itself, remove that exposure.
For a commercial organisation this may be an acceptable risk. For public sector bodies, healthcare, defence suppliers, critical infrastructure, and anyone in scope of NIS2 or DORA, it is increasingly a question that has to be answered explicitly rather than assumed away.
This is not a hypothetical concern in Europe any more. It is a procurement question that shows up in tenders.
4. Paying for a platform you use a fraction of
ServiceNow is an enterprise platform with very broad capability. Many organisations use a narrow slice of it — incident, request, and change, with some CMDB — while paying for the platform.
That is a perfectly rational trade when the breadth is a roadmap you intend to use. It is a poor trade when the roadmap never arrives, which, in my experience, is more often than anyone admits at contract signature.
How to tell which reason applies to you
The four reasons lead to different answers. Cost pressure alone may be solved by renegotiation or licence hygiene. Jurisdiction cannot be — it requires a different provider. Lock-in has to be addressed regardless of which platform you end up on, because otherwise you will simply recreate it somewhere else.
| Primary driver | Does replacing the platform solve it? | First step |
|---|---|---|
| Licence cost growth | Sometimes | Licence and usage audit before any vendor conversation |
| Customisation lock-in | Only partly | Map which customisations are genuinely in use |
| US jurisdiction | Yes | Define your sovereignty requirement precisely |
| Paying for unused capability | Yes | Establish what you actually consume, by module |
Three of the four start with the same activity: finding out what you actually use. That is not a vendor question. It is an internal one, and it is cheap compared with the decision that follows.
What replacing it actually involves
A ServiceNow replacement is not a tool swap. It is a transformation, and it fails in all the usual ways if it is run as a procurement exercise.
The work divides into five phases — analysis, development, migration, go-live and hypercare — and the first one determines whether the other four are realistic. We describe how we run that in our ServiceNow replacement service.
If the driver is jurisdiction rather than cost, the wider question is which parts of your estate need to sit under European control, and what genuinely European options exist. That is covered in European technology alternatives.
The honest summary
ServiceNow is a good product with a commercial and jurisdictional model that does not fit every organisation. Leaving is a serious undertaking and it is the wrong answer for plenty of organisations who ask the question.
But it is the right answer for some — and the ones it is right for tend to know exactly which of the four reasons above is theirs. If you cannot name yours, you are not ready to start looking at alternatives yet.
Frequently asked questions
- Is ServiceNow a bad product?
- No. ServiceNow is a capable, mature platform and for large enterprises with broad ITSM, ITOM and workflow needs it is often the right choice. Organisations leave for commercial, jurisdictional and fit reasons, not because the product does not work.
- How much does ServiceNow typically cost?
- ServiceNow does not publish list pricing; it is negotiated per customer and driven mainly by fulfiller licence counts, the product lines enabled, and contract term. The pattern that pushes organisations to review alternatives is not the initial price but the renewal, where costs rise as user counts and enabled modules grow.
- What is the main risk of replacing ServiceNow?
- Underestimating the integrations and the process knowledge embedded in existing customisations. The platform is rarely the hard part; the surrounding estate is. Any credible replacement starts by mapping what is genuinely in use, which is often a fraction of what was built.