Methodology: built from BMC Helix and ServiceNow product pages, documentation, support-lifecycle tables and press releases, G2 and Gartner Peer Insights ratings, and one attributed Vendr benchmark, checked 29 Sep 2026. No vendor reviewed or paid for this article. We did not run hands-on tests.
ServiceNow vs Remedy is now a choice between ServiceNow and BMC Helix ITSM, which BMC calls "the next generation of Remedy." Pick ServiceNow for one cloud platform shared across departments and stronger G2 reviewer scores. Pick BMC Helix to keep your Remedy process model and the option to run on your own infrastructure. For Remedy platform owners and Heads of Service Management, the real trigger is support. Remedy 20.02 is already out of support, and two BMC Helix on-premises versions lose support on 3 December 2026 (BMC; BMC, as of 29 Sep 2026).
Key takeaways
- BMC describes BMC Helix ITSM as "the next generation of Remedy" (BMC Helix, as of 29 Sep 2026). Remedy AR System Server 20.02, the newest non-containerized Remedy release, reached end of version support on 21 Feb 2025 (BMC; BMC Helix, as of 29 Sep 2026).
- BMC Helix ITSM OnPrem 23.3.04 and 25.2.01 reach end of version support on 3 Dec 2026. The newest on-premises release, 26.1.01, is supported until 6 Sep 2027 (BMC, as of 29 Sep 2026).
- Both vendors say they were named Leaders in the 2026 Gartner Magic Quadrant for IT Service Management Platforms (BMC Helix, ServiceNow, as of 29 Sep 2026).
- Neither vendor publishes list prices. ServiceNow sells ITSM as Foundation, Advanced and Prime on a custom quote (ServiceNow, as of 29 Sep 2026), and BMC Helix offers "Request Pricing" (BMC Helix, as of 29 Sep 2026).
- On G2, ServiceNow ITSM rates 4.5/5 from 1,986 reviews and BMC Helix ITSM 3.7/5 from 297 reviews (G2 ServiceNow, G2 BMC Helix, as of 29 Sep 2026).
ServiceNow vs Remedy: the short answer
For most Remedy shops, staying supported now means an ITSM migration of some kind: to containerized BMC Helix on-premises, to BMC Helix SaaS, or to ServiceNow.
| Decision factor | Choose ServiceNow if… | Choose BMC Helix (Remedy) if… |
|---|---|---|
| Hosting | You want a vendor-run cloud platform | You need to keep ITSM in your own data center or private cloud |
| Existing Remedy investment | You are ready to redesign processes and retire AR System customizations | Your Remedy workflows, forms and integrations are deep and still fit the business |
| Scope beyond IT | HR, facilities, legal and IT should share one platform | IT service and operations management is the main scope |
| Admin skills | You can hire or train ServiceNow admins and developers | Your team already knows AR System and Remedy administration |
| Reviewer experience | Ease of use and admin scores weigh heavily in your decision | Continuity matters more than interface scores |
The verdict in one line: ServiceNow wins on breadth and G2 reviewer scores, while BMC Helix wins on continuity and hosting choice.
What changed in 2026: Remedy support dates, AI and ownership
Three things changed for Remedy shops: BMC's on-premises support clock, AI packaging at both vendors, and Remedy's owner. On 9 Oct 2024, BMC announced it would split into two companies: "BMC Helix will be the name of the company for the digital service and operations management business unit," with the transition starting in early 2025 (BMC Helix, as of 29 Sep 2026).
Remedy and BMC Helix on-premises support dates
BMC publishes support dates per version.
| Product and version | Released | Full support ends | End of version support | Status (29 Sep 2026) |
|---|---|---|---|---|
| Remedy AR System Server 20.02 | 21 Feb 2020 | 21 Feb 2024 | 21 Feb 2025 | Ended |
| BMC Helix ITSM OnPrem 25.1.01 | 11 Mar 2025 | 11 Mar 2026 | 11 Sep 2026 | Ended |
| BMC Helix ITSM OnPrem 23.3.04 | 3 Dec 2024 | 3 Jun 2026 | 3 Dec 2026 | Limited support |
| BMC Helix ITSM OnPrem 25.2.01 | 3 Jun 2025 | 3 Jun 2026 | 3 Dec 2026 | Limited support |
| BMC Helix ITSM OnPrem 25.3.01 | 3 Sep 2025 | 3 Sep 2026 | 3 Mar 2027 | Limited support |
| BMC Helix ITSM OnPrem 25.4.01 | 20 Nov 2025 | 20 Nov 2026 | 20 May 2027 | Full support |
| BMC Helix ITSM OnPrem 26.1.01 | 6 Mar 2026 | 6 Mar 2027 | 6 Sep 2027 | Full support |
Sources: BMC Remedy AR System Server versions and BMC Helix ITSM OnPrem versions, as of 29 Sep 2026. BMC Service Level Management 9.1.04, an older Remedy module, reached end of version support on 5 Dec 2022 (BMC, as of 29 Sep 2026).
Every 25.x and 26.x on-premises release listed reaches end of version support 18 months after release, so staying on-premises means a standing upgrade program. We found no BMC end date for the on-premises product line itself, only per-version dates.
Other changes in 2025 and 2026
| Date | Vendor | Change | Why it matters |
|---|---|---|---|
| 7 May 2025 | BMC Helix | Release 25.2 adds HelixGPT Agent Builder for no-code custom agents, plus Ops Swarmer and Catalog Curator (BMC Helix) | Agentic AI inside BMC Helix ITSM |
| 9 Apr 2026 | ServiceNow | AI, data, security and governance are "now in every ServiceNow offering" and "not a separate purchase" (ServiceNow) | AI is part of the package price |
| 5 May 2026 | ServiceNow | ServiceNow Otto combines Now Assist, Moveworks and AI Experience (ServiceNow) | AI features may carry a new name |
| 3 Aug 2026 | BMC Helix | Named a Leader in the 2026 Gartner Magic Quadrant for ITSM Platforms (published 27 Jul 2026) "for the 10th time" (BMC Helix) | Both vendors claim Leader in the same report |
All rows as of 29 Sep 2026.
ServiceNow vs BMC Helix capabilities side by side
Both platforms cover incident, problem, change, request, service level and CMDB management; they differ in how ServiceNow tiers them and where BMC Helix can run. BMC Helix entries come from its product page and ServiceNow entries from its ITSM pricing page unless another source is shown. All cells as of 29 Sep 2026.
| Capability | BMC Helix ITSM | ServiceNow ITSM |
|---|---|---|
| Incident management | Core | Foundation |
| Problem management | Core | Advanced |
| Change and release | Change and release management | Change in Advanced; Digital Product Release in Prime |
| Service catalog and requests | Service requests through SRM forms (BMC docs); HelixGPT Catalog Curator (BMC Helix) | Foundation |
| Service level management | Core; SLA outcomes kept as measurement records (BMC docs) | Task SLA records per ticket (ServiceNow docs) |
| Asset management and CMDB | BMC Helix CMDB, asset management | Foundation ("Asset Management and CMDB") |
| Deployment | SaaS, or containerized on-premises on Kubernetes platforms such as Red Hat OpenShift (BMC Helix blog) | Cloud service; docs also refer to self-hosted customers (ServiceNow docs) |
| US public sector | DoD IL5 provisional authorization on AWS GovCloud (BMC Helix) | FedRAMP High P-ATO and DoD IL4 for Government Community Cloud; IL5 for National Security Cloud (ServiceNow) |
| Custom AI agents | HelixGPT Agent Builder (BMC Helix) | Prime only (ServiceNow docs) |
| List price | Not published ("Request Pricing") | Not published (custom quote) |
"Core" means BMC lists the capability on its ITSM product page without a tier. For the wider market, see the top ITSM tools for 2026.
What reviewers say about ServiceNow and BMC Helix
The two review sites disagree. G2 reviewers favor ServiceNow on every score. Gartner Peer Insights rates BMC Helix ITSM 4.4 from 280 ratings and ServiceNow ITSM 4.3 from 2,028 in the ITSM platforms market (Gartner Peer Insights, as of 29 Sep 2026).
| G2 signal (as of 29 Sep 2026) | BMC Helix ITSM | ServiceNow ITSM |
|---|---|---|
| Rating (reviews) | 3.7/5 (297) | 4.5/5 (1,986) |
| Ease of use | 7.1 | 8.5 |
| Ease of setup | 7.0 | 8.2 |
| Ease of admin | 7.2 | 8.6 |
| Meets requirements | 8.0 | 8.9 |
| Quality of support | 7.5 | 8.6 |
| Share of enterprise reviewers | 74.8% | 72.8% |
| Most-mentioned con | Outdated user interface (12 mentions) | Steep learning curve (70 mentions) |
Scores and segments come from the G2 comparison page; ratings and cons from each product's review page (BMC Helix, ServiceNow). Both draw mostly enterprise reviewers, so size does not explain the gap.
Data model differences: Remedy forms vs ServiceNow tables
Remedy and ServiceNow store the same ITIL concepts in very different shapes: AR System forms tied to shared Foundation data in Remedy, task records in ServiceNow. That difference decides what survives a migration.
How BMC Helix (Remedy) structures ITSM records
BMC Helix ITSM keeps Remedy's AR System model, where data lives in forms such as HPD:WorkLog for incident work info and CHG:Associations for CIs linked to changes (BMC docs, as of 29 Sep 2026).
Underneath every ticket sits Foundation data: company, organization, people, support groups and categorization (BMC docs, as of 29 Sep 2026). In the CMDB, each Common Data Model class "equates to a database table or a AR System form" (BMC docs, as of 29 Sep 2026). CIs build on BMC_BaseElement, and relationships are "a base relationship class (BMC_BaseRelationship) with subclasses for different types of relationships" (BMC docs, as of 29 Sep 2026).
SLA results are measurement records; request-based compliance is "the total count of the met measurement records, divided by all the resolved measurement records in that review period" (BMC docs, as of 29 Sep 2026).
How ServiceNow structures ITSM records
In ServiceNow, incidents, problems and changes are task records. The Task SLA table "stores Task SLA records for the SLAs attached to particular tasks," with fields such as breach time, business elapsed time and original breach time (ServiceNow docs, as of 29 Sep 2026).
In the ServiceNow CMDB, CI relationships live in the CI Relationship [cmdb_rel_ci] table as a parent CI, a child CI and a relationship type. The Identification and Reconciliation Engine uses dependent relationships to identify CIs and prevent duplicates (ServiceNow docs, as of 29 Sep 2026).
How Remedy concepts map to ServiceNow
| Remedy / BMC Helix | ServiceNow equivalent | Mapping decision |
|---|---|---|
| Incidents (HPD forms) with work info (HPD:WorkLog) | Incident, with work notes and comments | Split each work info entry into internal work notes or customer-visible comments |
| Change requests (CHG forms), CI links in CHG:Associations | Change Request with affected CIs | Rebuild change models and approval rules; carry CI links as data |
| Problem investigations (PBM forms) | Problem | Keep links from problems to incidents and known errors |
| Service requests (SRM) and tasks (TMS) | Requests, requested items and tasks | Catalog items and variables are rebuilt, not copied |
| Foundation data: people, support groups, companies | Users, groups, companies | Load first; every ticket references these |
| Operational and product categorization | Category fields, services or CIs | Decide whether tiers become choices or references |
| CI classes (BMC_BaseElement subclasses) | CMDB CI classes | Map class by class; some merge |
| Relationships (BMC_BaseRelationship subclasses) | CI Relationship [cmdb_rel_ci] | Map each subclass to a relationship type and direction |
| SLA measurement records | Task SLA [task_sla] | History moves as data; SLA definitions and running timers are rebuilt |
In short, Foundation data and relationship subclasses need a deliberate mapping before any ticket moves, because data fidelity in a migration depends on them.
AI compared: Now Assist and Otto vs HelixGPT
Both vendors now bundle AI with ITSM instead of selling it as a separate product. The differences are in tiers and hosting.
| AI capability | ServiceNow | BMC Helix |
|---|---|---|
| Packaging | AI "now in every ServiceNow offering" (ServiceNow) | HelixGPT "is not licensed as a separate SKU" (BMC docs) |
| Agent and employee assist | Now Assist in Foundation, Advanced and Prime (ServiceNow) | Employee Navigator for all ITSM users since 25.2 (BMC Helix) |
| Packaged AI agents | AI Agents for ITSM and L1 Service Desk AI Specialist in Prime (ServiceNow) | Ops Swarmer and Catalog Curator agents (BMC Helix) |
| Build your own | Custom AI skills and agents in Prime only (ServiceNow docs) | HelixGPT Agent Builder, no-code |
| Self-hosted or on-premises | Some AI features unavailable to self-hosted customers and FedRAMP, IL5 and IRAP-Protected data centers (ServiceNow docs) | ITSM OnPrem entitlement lists Employee Navigator and Insight Finder (BMC docs) |
All rows as of 29 Sep 2026.
The AI verdict: ServiceNow reserves custom agents for Prime, while BMC Helix offers a no-code Agent Builder but names fewer HelixGPT features for OnPrem, so check your entitlement. Either way, AI that reads past tickets works better when that history comes with you.
ServiceNow vs BMC Helix pricing and total cost of ownership
Neither vendor publishes list prices, so the costs you can compare in advance are upgrade cadence, hosting and skills. ServiceNow names its Foundation, Advanced and Prime packages and offers a custom quote (ServiceNow, as of 29 Sep 2026). BMC Helix shows no prices or editions on its ITSM product page and links to "Request Pricing" (BMC Helix, as of 29 Sep 2026).
For a public benchmark, Vendr reports a median ServiceNow contract of $129,871 per year across 109 purchases (Vendr, as of 29 Sep 2026; page last updated February 2026). That figure covers all ServiceNow products, not ITSM alone (see our ServiceNow pricing guide). We found no comparable public benchmark for BMC Helix ITSM.
Cost factors that don't show on a quote
| Cost factor | ServiceNow | BMC Helix |
|---|---|---|
| Upgrades | About one upgrade a year to stay on a supported release family, since ServiceNow supports the current and previous families (ServiceNow) | On-premises: an upgrade at least every 18 months to stay supported (BMC). SaaS: confirm upgrade scheduling with BMC |
| Infrastructure | Vendor-hosted for cloud customers | On-premises needs a supported Kubernetes platform (BMC Helix blog) |
| Skills | 70 G2 reviewers cite a steep learning curve (G2) | 8 G2 reviewers cite setup complexity (G2) |
| Cost complaints | 59 G2 reviewers cite high costs (G2) | 4 G2 reviewers cite high costs (G2) |
All rows as of 29 Sep 2026. Review mention counts reflect very different review volumes, so read them as themes, not rates.
Switching cost belongs in every option: a move within BMC is still a migration project, with the same help desk migration risks to plan for. Line up your BMC renewal date with the support table above and decide before your notice period starts.
Should Remedy shops move to ServiceNow? Your three options
A Remedy shop has three supported destinations. BMC runs programs for the first two.
| Option | What it involves | Choose this if |
|---|---|---|
| Upgrade to BMC Helix ITSM OnPrem | BMC's HOME program helps "migrate non-containerized versions of Remedy (20.02 or earlier) to BMC Helix Service Management on-premises" (BMC Helix) | Data must stay on your infrastructure and your Remedy customizations still fit |
| Move to BMC Helix SaaS | BMC's migration service moves Remedy ITSM on-premises to BMC Helix ITSM 26.1 using BMC Helix Data Manager; the source must be 20.02 or later, and non-standard configurations and integrations fall outside standard scope (BMC Helix) | You want to keep the Remedy process model without running the infrastructure yourself |
| Move to ServiceNow | A new implementation, plus mapping and migrating your history | You want one platform across departments and are ready to redesign processes |
All rows as of 29 Sep 2026.
Five questions to decide
- Which release are you on today? If it is 20.02 or earlier, you are already past end of version support (BMC, as of 29 Sep 2026), so compare all three paths on equal terms.
- Must your ITSM data stay on your own infrastructure? If yes, BMC Helix OnPrem is the clearest fit; ServiceNow's docs mention self-hosted customers, so ask whether that applies to you. Budget for upgrades inside each 18-month support window (BMC, as of 29 Sep 2026).
- How much of your Remedy customization still earns its keep? If most AR System workflow exists to work around old processes, a move to ServiceNow is a chance to drop it.
- Will departments beyond IT share the platform? ServiceNow's case is strongest when HR, facilities and legal will use it too. If IT is the main scope, also weigh the ServiceNow alternatives.
- How much history must you keep, and in what form? Decide early whether closed tickets, SLA records and CI relationships move, get archived, or both. An audit of your legacy help desk data makes that call easier.
Mostly "stay close to what we have" points to BMC Helix. Mostly "one platform, fresh design" points to ServiceNow.
Migrating from Remedy to ServiceNow
A Remedy to ServiceNow migration moves ticket history as data and rebuilds process logic on ServiceNow. The ServiceNow migration guide covers the full plan; this section covers what is specific to Remedy.
| Moves (with mapping) | Rebuilt on ServiceNow | At risk without planning |
|---|---|---|
| Incidents, problems and changes | Workflows, filters and escalations | Links between incidents, problems and changes |
| Service requests and tasks | Business rules and approval flows | CI relationship subclasses and direction |
| Knowledge articles | SLA definitions and running SLA timers | SLA measurement history |
| People, support groups and companies | Service catalog items and variables | Original created and resolved timestamps |
| CIs and relationships | Assignment rules and notifications | Internal vs public work info |
| Attachments | Categorization logic and priority matrix | Operational and product categorization tiers |
On the Remedy side, the AR System Max-Entries-Per-Query setting caps how many requests a search returns, with a default of 2,000 in BMC's Remedy 18.08 tuning guide (BMC docs, as of 29 Sep 2026). Extraction therefore needs paging. On the ServiceNow side, import sets load data into a staging table and transform it into the target. A coalesce field decides whether a row updates an existing record or creates a new one (ServiceNow Developer blog, as of 29 Sep 2026). Attachments default to a 1,024 MB maximum (ServiceNow docs, as of 29 Sep 2026).
If each migrated record carries its Remedy ID as the coalesce key, a delta load updates rather than duplicates, which is how late changes in the freeze window get picked up.
Run the move as a controlled change:
- Discover. Inventory forms, record counts, Foundation data, CI classes and integrations.
- Map. Map states, the priority matrix, categorization, groups and every relationship subclass.
- Test migration. Load a full copy into a sub-production instance and reconcile it.
- Cutover with delta sync. Freeze Remedy changes, load the final delta, then run go/no-go.
- Reconcile. Compare counts, links, attachments and timestamps per record type, as in a zero-loss migration framework.
- Hypercare. Watch rebuilt SLAs, routing and notifications closely after go-live.
SLA timers, priority matrices, workflows and business rules are rebuilt and tested on ServiceNow before go/no-go, never copied.
ServiceNow vs Remedy evaluation checklist
- Confirm your exact Remedy or BMC Helix version and its end-of-version-support date on BMC's support site.
- Note your BMC renewal date and notice period, and work back from them.
- List every module in use: incident, problem, change, release, service request, knowledge, SLM, asset, CMDB.
- Export Foundation data counts: companies, people, support groups, categorization tiers.
- Export CI class and relationship subclass lists, and mark which drive change and impact analysis.
- Count records per form, including closed tickets and attachments, so you can prevent a lost attachment flood at cutover.
- Inventory AR System workflow, filters, escalations and integrations, and mark which to retire.
- Document SLA definitions, business calendars and the priority matrix for rebuild.
- Decide which history moves, which is archived, and how original timestamps are kept.
- Check hosting and compliance needs, including FedRAMP or DoD impact levels.
- Get quotes for all three options: Helix OnPrem, Helix SaaS and ServiceNow.
- Agree a freeze window, a reconciliation method and go/no-go criteria, and name a migration project lead to own them.
ServiceNow vs Remedy FAQ
Methodology
We compared ServiceNow and BMC Helix ITSM using each vendor's own product pages, documentation, press releases and, for BMC, its public version-support tables, all checked on 29 September 2026. Analyst placements are cited to each vendor's announcement. Ratings come from G2 and Gartner Peer Insights on the same date, and ServiceNow spend data comes from Vendr with attribution.
Disclosure: MigrateX, the publisher of this article, runs ITSM data migrations, including between platforms named here. No vendor reviewed or paid for this article.