SAP Solution Manager ITSM retirement: moving the IT service desk to ServiceNow, JSM or Freshservice
Short answer
SAP’s own Solution Manager page says mainstream maintenance for SAP Solution Manager 7.2 is available until the end of 2027, and an SAP News article dates that as December 31, 2027. Customers who take the optional extended maintenance for SAP Business Suite 7 (until the end of 2030) get extended maintenance for SolMan 7.2 too, and SAP lists IT service management among the scenarios that extended maintenance covers. SAP’s successor for application lifecycle management is SAP Cloud ALM, but SAP states plainly that “SAP Cloud ALM does not provide IT Service Management” and that customers who used ITSM in Solution Manager should “plan a transition to a 3rd party ITSM tool.” So the service desk part of SolMan does not migrate to Cloud ALM; it moves to a separate ITSM product. Our view: ServiceNow is the low-friction choice if you already run it, because SAP documents a ready-to-use Cloud ALM integration with ServiceNow Incident Management (ServiceNow is quote-only). Jira Service Management fits SAP teams that already live in Jira (Standard $21.50 / about £15.95, Premium $55.28 / about £41.02 per agent per month at Atlassian’s default 75-agent view). Freshservice is the simplest standalone desk (Pro $99 / £79 per agent per month billed annually, official GBP). Both JSM and Freshservice connect to Cloud ALM through SAP’s generic external-ticket integration, which you configure and map yourself.
Contents
- Who this guide is for
- What SAP actually says about Solution Manager, 2027 and ITSM
- What the SolMan service desk does that you must replace
- How Cloud ALM talks to an external ITSM tool
- ServiceNow vs JSM vs Freshservice for the SAP service desk
- Published pricing for the three destinations (checked Nov 9, 2026)
- A phased plan from SolMan ITSM to the new desk
- Best for, and wrong choice when
- Frequently asked questions
Who this guide is for
This guide is for SAP basis leads, SAP CoE managers and IT service managers whose SAP support desk runs in SAP Solution Manager 7.2 IT Service Management: incidents raised by key users, service requests, the message flow to SAP support, and in many shops the link between incidents and change control. If that describes you, you have probably been told “Solution Manager is going away” and “Cloud ALM replaces it.” Only the first half of that is roughly right for ITSM.
We stick to what SAP says on its own pages, checked on Nov 9, 2026: the SAP Solution Manager 7.2 page on SAP Support Portal, the SAP “Transition to SAP Cloud ALM for Implementation” page, the SAP “Transition to SAP Cloud ALM for Operations” page, the SAP Cloud ALM “Integration with External Ticket Systems” page and the SAP News article on the transition to SAP Cloud ALM (June 2026). Prices come only from vendor pricing pages checked the same day: the ServiceNow ITSM pricing page (quote-only), the Atlassian Service Collection / Jira Service Management pricing page and the Freshservice pricing page. Opinions about which destination suits which SAP organisation are ours, from service desk work, and are labelled as such.
What we will not do
We do not estimate ServiceNow prices: ServiceNow publishes packages, not numbers. We do not name an SAP “official ITSM partner”, because none of the SAP pages we checked designates one; they mention ServiceNow and Jira as examples of external systems. And we do not quote SAP maintenance fees, which depend on your SAP contract.
What SAP actually says about Solution Manager, 2027 and ITSM
Four statements on SAP’s own pages matter for the service desk. We quote them closely because the internet is full of paraphrases that drift.
| Topic | What SAP states (checked Nov 9, 2026) | Where |
|---|---|---|
| Mainstream maintenance | “Mainstream maintenance for SAP Solution Manager 7.2 is available until the end of 2027.” SAP News gives the date as December 31, 2027, with maintenance details referred to SAP Notes 52505 and 3255311. | SAP Solution Manager page; SAP News, June 2026 |
| Extended maintenance | Customers who choose optional extended maintenance for SAP Business Suite 7 (until end of 2030) receive extended maintenance for SolMan 7.2 at no additional cost. Extended maintenance only includes requirements management, project management, process management, test suite, change control management, IT service management (ITSM) and landscape management. | SAP Solution Manager page |
| SAP’s recommendation | “SAP recommends all customers to transition to SAP Cloud ALM before the end of 2027.” | SAP Solution Manager page |
| ITSM in Cloud ALM | “IT Service Management functionality is not in scope.” “SAP Cloud ALM does not provide IT Service Management, therefore no transition is required. If customers have used ITSM in SAP Solution Manager, SAP recommends to plan a transition to a 3rd party ITSM tool.” | Transition to SAP Cloud ALM for Implementation |
Read the extended-maintenance line carefully. It does give an organisation that buys Business Suite 7 extended maintenance a longer runway for the SolMan ITSM scenario, to the end of 2030. It does not make SolMan ITSM a long-term platform: SAP still recommends moving to Cloud ALM before the end of 2027, and Cloud ALM will never host the service desk. In practice extended maintenance buys time to migrate calmly. It does not change where you end up.
The operations transition page adds one more detail that matters for IT task management. SAP says IT Task Management in Solution Manager “is based on IT service management functionality, which is not part of SAP Cloud ALM”, and that an integration between Cloud ALM and “external task management systems like JIRA or ServiceNow” can be established through the existing and planned event-to-task interface. Those are examples SAP gives, not an endorsement, and we treat them that way.
What the SolMan service desk does that you must replace
In most SAP shops the Solution Manager service desk is more than a ticket list. Before you compare destinations, write down which of these you actually use. The list is the scope of the project; the ticket count is not.
| SolMan ITSM job | What the destination must do | Watch out for |
|---|---|---|
| Key-user incident intake | Portal and email intake, with SAP component or module as a field, routed to the right support group | Key users who raise tickets from inside SAP GUI or Fiori today will need a new, equally short path |
| Message processing with SAP support | A documented way to log and track cases with SAP itself | SAP’s implementation transition page describes SolMan’s central message management as allowing you to “connect to an external help desk, set up service connections, and access SAP Service & Support”. Plan how your team will raise and track SAP cases after the move, and keep that separate from internal tickets |
| Service requests | A catalogue for SAP authorisations, user creation, transport requests and similar | Approvals tied to SAP roles often live in custom SolMan workflow and need rebuilding |
| Monitoring alerts to tickets | Create incidents from SAP alerts, then keep the status in sync | In Cloud ALM this is Intelligent Event Processing forwarding events to an external ticket system |
| Link to change control | Incidents and requests that lead to SAP changes | SAP moves change control and deployment to Cloud ALM, not to the ITSM tool. Decide where the approval record lives |
| Non-SAP IT tickets | Some customers run part of general IT in SolMan | Use the move to put SAP and non-SAP IT on one desk if the rest of IT already has one |
The last row is often the deciding one. If the rest of the organisation already runs ServiceNow, JSM or Freshservice for IT, the cheapest and least risky answer is usually to bring SAP support onto that desk as its own group, with its own categories and SLAs. Buying a separate “SAP-only” ITSM tool makes sense only when SAP support is organisationally separate from the rest of IT, and it usually stays that way.
How Cloud ALM talks to an external ITSM tool
Your new desk still needs to receive SAP operational events: a failed job, a broken interface, a system that has gone down. SAP’s SAP Cloud ALM “Integration with External Ticket Systems” page describes how Cloud ALM forwards events to external ticket systems to create incidents or cases. Three points from that page shape the destination choice.
- ServiceNow has a ready-made path. SAP says Cloud ALM “provides a ready-to-use integration with ServiceNow Incident Management including a pre-defined API mapping”; you maintain a destination with authentication and can adjust the mapping file. SAP also says this solution is “intended to enable a rapid prototyping and as baseline for customer specific implementations” and “does not consider the back communication from ServiceNow to SAP Cloud ALM.” Even on ServiceNow, budget for building the return path.
- Other ticket systems use the generic route. “Any ticket system can be connected to SAP Cloud ALM using the provided External API Integration capabilities.” The target must expose REST APIs for incidents, take one payload per operation, return the ticket number or ID on create, and be reachable from the Cloud ALM BTP account. If one API call is not enough, SAP says the extra logic has to live in an integration system.
- It is always two-way. SAP states that “the integration to ticket systems is always bi-directional and requires status updates from the ticket system back to SAP Cloud ALM.” Whoever owns the ITSM tool must own that status sync.
Jira Service Management and Freshservice both publish REST APIs for creating and updating tickets, so both fit the generic pattern. What you do not get on either is SAP’s pre-built mapping. Somebody maps fields, priorities and status values, and somebody tests what happens when an event closes in Cloud ALM while the ticket is still open in the desk. That is a few days of careful integration work, not a reason to rule either tool out. It is a real difference from ServiceNow, though, and you should plan for it.
ServiceNow vs JSM vs Freshservice for the SAP service desk
| ServiceNow ITSM | Jira Service Management | Freshservice | |
|---|---|---|---|
| Cloud ALM event integration | Ready-to-use mapping for Incident Management documented by SAP; return path is yours to build | Generic External API integration; you build the mapping and status sync | Generic External API integration; you build the mapping and status sync |
| Mentioned on SAP transition pages | Yes, as an example external task system | Yes (“JIRA”), as an example external task system | Not named |
| Public pricing | Quote-only: ITSM Foundation, Advanced, Prime | Free (3 agents), Standard, Premium published; Enterprise via sales | Starter, Growth, Pro published with official GBP; Enterprise contact-sales |
| Change management | In the ITSM packages (confirm placement in your quote) | Premium tier on Atlassian’s page | Pro and Enterprise |
| Best fit for | Enterprises already on ServiceNow, or with heavy governance needs across SAP and non-SAP | SAP teams that already run development, transports or projects in Jira | Mid-sized IT that wants one simple desk for SAP and non-SAP support |
ServiceNow: least integration friction, highest commercial uncertainty
If ServiceNow is already the enterprise IT desk, moving SAP support onto it is the obvious move: SAP documents the Cloud ALM incident integration, your fulfillers already have licences, and the CMDB may already hold SAP systems. If ServiceNow is not already in place, buying it only to replace SolMan ITSM is a big commitment. ServiceNow sells ITSM as Foundation, Advanced and Prime packages on the ServiceNow ITSM pricing page with no list prices, and you will be quoted per fulfiller. We do not estimate that number.
Jira Service Management: right when SAP development already lives in Jira
Many SAP CoEs already run their development backlog, transports or project work in Jira. Putting the SAP service desk in JSM keeps incidents next to the work items developers already use, and SAP names “JIRA” as an example external task-management system. The trade-off is the Cloud ALM integration: you build it against Atlassian’s REST API rather than starting from an SAP-supplied mapping. Change management, which most SAP organisations want, sits on JSM Premium.
Freshservice: right when SAP support should just be another IT group
Freshservice suits organisations where SAP support is a few groups inside a mid-sized IT department and nobody wants to run a platform. It has the most straightforward published pricing of the three, with official GBP. The Cloud ALM integration uses the same generic route as JSM. Freshservice is the wrong pick if your SAP change process needs heavy, audited workflow across many approvers, or if SAP support is large enough to deserve its own platform team.
Published pricing for the three destinations (checked Nov 9, 2026)
Every number below comes from the vendor’s own pricing page on Nov 9, 2026. Prices are per agent (fulfiller) per month; end users who only raise tickets are not licensed as agents on any of the three. Taxes and VAT are extra.
| Product and plan | USD (per agent / month) | GBP (per agent / month) | Billing and notes |
|---|---|---|---|
| ServiceNow ITSM Foundation / Advanced / Prime | Quote-only | Quote-only | No list prices on the ServiceNow pricing page; we do not estimate |
| JSM Free | $0 (up to 3 agents) | £0 | Atlassian’s page |
| JSM Standard | $21.50 | about £15.95 (indicative) | Monthly price at Atlassian’s default 75-agent view; pricing is progressive by agent count |
| JSM Premium | $55.28 | about £41.02 (indicative) | Same basis as Standard; change management sits here |
| JSM Enterprise | Contact sales | Contact sales | Annual billing only |
| Freshservice Starter | $19 annual / $29 monthly | £15 annual / £25 monthly (official) | No service catalogue, SLA or assets on Starter |
| Freshservice Growth | $49 annual / $59 monthly | £40 annual / £45 monthly (official) | Adds catalogue, SLAs, assets |
| Freshservice Pro | $99 annual / $119 monthly | £79 annual / £95 monthly (official) | Adds problem, change, release, major incident |
| Freshservice Enterprise | Contact sales | Contact sales | The page hides the Enterprise price; we do not quote it |
Indicative GBP conversions use the Bank of England daily spot rate (series XUDLUSS) of US$1.3476 per £1 for 5 Nov 2026, which was still the latest published figure when we re-checked the Bank of England series on Nov 9, 2026. They are not official UK prices: the vendor does not publish a GBP list price for these items, and your invoice currency, rate and VAT treatment may differ. Freshservice GBP figures are Freshworks’ own GBP list prices; JSM GBP figures are our indicative conversion because Atlassian’s public page switches between USD and JPY, not GBP.
A worked example for a 15-agent SAP support desk
Fifteen SAP support agents on Freshservice Pro at the annual rate cost $99 × 15 × 12 = $17,820 / £14,220 a year in licences (official GBP: £79 × 15 × 12). We do not publish a 15-agent JSM total: Atlassian prices progressively by agent count and only shows per-agent figures for its default view, so multiplying $21.50 by 15 would understate or overstate your real quote. ServiceNow is quote-only. If those 15 agents join an existing desk on any of the three, the real cost question is whether your current licence count already has room, not the list price.
A phased plan from SolMan ITSM to the new desk
Phase 0 — Decide the scope with SAP’s dates in front of you
Confirm with your SAP account team which maintenance option you hold (mainstream to end-2027, or Business Suite 7 extended maintenance to end-2030) and when your Cloud ALM tenant will be live. Write down which SolMan ITSM scenarios you actually use: incidents, service requests, message flow to SAP, IT task management, or ChaRM links. That list is the project.
Phase 1 — Choose the destination by where the rest of IT lives
If IT already has a desk, the default is to bring SAP support onto it. Choose a new product only if there is no enterprise desk, or SAP support is deliberately separate. Do not buy a platform for the SAP desk alone without pricing it against moving those agents onto the existing one.
Phase 2 — Build SAP categories, groups and SLAs empty
Create SAP support groups, a component/module field, priorities that match your SAP support agreement, and the catalogue items your key users raise most: authorisations, user locks, transport requests, master data fixes. Import nothing yet.
Phase 3 — Wire Cloud ALM events and prove the return path
On ServiceNow, start from SAP’s ready-to-use mapping and build the back-communication SAP says it does not cover. On JSM or Freshservice, build the mapping through the generic External API integration and test create, update, status polling and close. Prove that an event closed in Cloud ALM and a ticket closed in the desk both end up in the same state.
Phase 4 — Move open work, archive the history
Move open incidents and requests with their latest notes. For closed history, decide whether auditors need it in the new tool or whether a read-only export with a clear retention owner is enough. In our experience most SAP teams need a searchable archive, not a full historic import into the new desk.
Phase 5 — Cut over key users, then retire SolMan ITSM
Switch the key-user entry points and email addresses, run both systems read-only/read-write in parallel for a short, dated window, then switch off SolMan ITSM. Keep the SolMan scenarios that are still in use (and still under maintenance) on their own plan towards Cloud ALM.
Things SAP teams forget
- Key users who log tickets from inside SAP today: give them a link, a Teams or Slack route, or an email alias on day one.
- Support-agreement priorities and response targets that are written into contracts with SAP partners or AMS providers.
- How your team raises and tracks cases with SAP itself after SolMan’s message processing is gone.
- Who owns the Cloud ALM-to-desk integration once the project team leaves.
- Reports that management reads every month from SolMan ITSM.
Best for, and wrong choice when
ServiceNow is the right home when
It already runs enterprise IT, or you need one governed platform across SAP and non-SAP services with a heavy CMDB. You get SAP’s ready-to-use Cloud ALM incident mapping as a starting point.
ServiceNow is the wrong choice when
You would be buying it only for a small SAP support desk. Without a quote you cannot compare, and the platform overhead is out of proportion to a 10 to 20 agent SAP team.
JSM is the right home when
SAP development, transports or AMS work already runs in Jira, and you want incidents and changes next to that work. Budget for building the Cloud ALM mapping yourself.
JSM is the wrong choice when
Nobody in IT administers Jira today, or your SAP change governance needs deep audited workflow that you are not prepared to configure on Premium.
Freshservice is the right home when
SAP support is a few groups inside a mid-sized IT department, you want published per-agent prices with official GBP, and you want the simplest admin model.
Freshservice is the wrong choice when
SAP support is large and governance-heavy, or you depend on a pre-built SAP integration; Freshservice uses the generic Cloud ALM route like JSM.
Whatever you choose, do not leave the decision until 2027. The SolMan dates are fixed on SAP’s pages; the length of your procurement cycle is not.
Frequently asked questions
When does SAP Solution Manager 7.2 maintenance end?
SAP’s Solution Manager page says mainstream maintenance for SolMan 7.2 is available until the end of 2027, and an SAP News article gives December 31, 2027. Customers who choose optional extended maintenance for SAP Business Suite 7 (until the end of 2030) receive extended maintenance for SolMan 7.2 at no additional cost, limited to specific scenarios that include ITSM. Checked on SAP pages on Nov 9, 2026.
Does SAP Cloud ALM replace Solution Manager ITSM?
No. SAP’s transition page states that SAP Cloud ALM does not provide IT Service Management and that customers who used ITSM in Solution Manager should plan a transition to a third-party ITSM tool.
Which ITSM tool does SAP recommend instead of Solution Manager?
The SAP pages we checked do not name a single recommended product. SAP mentions JIRA and ServiceNow as examples of external task management systems, and documents a ready-to-use Cloud ALM integration with ServiceNow Incident Management. Any ticket system with suitable REST APIs can be connected through Cloud ALM’s external API integration.
Can Jira Service Management or Freshservice receive SAP Cloud ALM alerts?
Yes, through SAP’s generic external ticket integration, as long as the tool exposes REST APIs for incidents and returns a ticket ID. You build and maintain the mapping and the status updates back to Cloud ALM yourself; SAP’s pre-defined mapping is for ServiceNow.
How much does ServiceNow cost to replace SolMan ITSM?
ServiceNow does not publish prices. Its ITSM pricing page lists Foundation, Advanced and Prime packages and asks you to request a quote. We do not estimate it.
How much do JSM and Freshservice cost per agent?
On Nov 9, 2026 Atlassian showed JSM Standard at $21.50 (about £15.95, indicative) and Premium at $55.28 (about £41.02, indicative) per agent per month at its default 75-agent view. Freshservice listed Starter $19 / £15, Growth $49 / £40 and Pro $99 / £79 per agent per month billed annually, with official GBP. Taxes are extra.
Should we stay on SolMan ITSM under extended maintenance?
Only as a bridge. Extended maintenance (where you have it) keeps SolMan ITSM supported to the end of 2030, but SAP still recommends moving to Cloud ALM before the end of 2027, and Cloud ALM has no ITSM. Use the time to migrate calmly, not to defer the decision.
Do we need to migrate all historic SolMan tickets?
Usually not. Move open work and recent history that agents actually search, and keep a read-only, searchable archive of the rest with a named retention owner. Check with audit and compliance before you decide.