ServiceNow vs Remedy 2026: BMC Helix Support Dates and What Moves
ServiceNow vs Remedy for 2026: BMC Helix support dates and the 3 Dec deadline, G2 scores, AI, cost and what moves if you switch. See which fits.
Published Updated 15 min read

On this page
- ServiceNow vs Remedy: the short answer
- What changed in 2026: Remedy support dates, AI and ownership
- ServiceNow vs BMC Helix capabilities side by side
- Data model differences: Remedy forms vs ServiceNow tables
- AI compared: Now Assist and Otto vs HelixGPT
- ServiceNow vs BMC Helix pricing and total cost of ownership
- BMC Remedy vs ServiceNow: which should you choose?
- Migrating from Remedy to ServiceNow
- ServiceNow vs Remedy evaluation checklist
- ServiceNow vs Remedy FAQ
ServiceNow vs Remedy is now a choice between ServiceNow and BMC Helix ITSM, which BMC Helix calls "the next generation of Remedy." Choose ServiceNow for one cloud platform shared across departments and higher G2 reviewer scores. Stay on BMC Helix to keep your Remedy process model and the option to run it on your own infrastructure. If you own a Remedy or BMC Helix platform, the trigger is support: two BMC Helix ITSM on-premises versions reach end of version support on 3 December 2026 (BMC support site, as of 20 Oct 2026).
ServiceNow vs Remedy: the short answer
| Decision factor | Choose ServiceNow if... | Stay on BMC Helix if... |
|---|---|---|
| Hosting | You want a vendor-run cloud platform | You need ITSM in your own data center |
| Remedy investment | You are ready to redesign processes and retire AR System customizations | Your Remedy workflows and integrations still fit the business |
| Scope | HR, facilities, legal and IT should share one platform | IT service and operations is the main scope |
| Admin skills | You can hire or train ServiceNow admins | Your team already knows AR System administration |
The verdict in one line: ServiceNow wins on breadth and reviewer scores, while BMC Helix wins on continuity and hosting choice.
What changed in 2026: Remedy support dates, AI and ownership
Three things changed: BMC's on-premises support clock, AI packaging and Remedy's owner. On 9 Oct 2024, BMC announced it would split in two, with "BMC Helix" as the name of the company for its service and operations management business (BMC Helix blog, letter from the CEO).
The 3 December 2026 deadline
If you run BMC Helix ITSM OnPrem 23.3.04 or 25.2.01, your version reaches end of version support on 3 Dec 2026, 44 days after this update (BMC support site, as of 20 Oct 2026). Both are already in limited support, which BMC defines as fixes for critical security vulnerabilities and major defects only. After end of support, "No new sustaining releases, enhancements, patches, or hotfixes" are made (BMC containerized products support policy, updated 1 Jan 2025).
The fastest way to stay covered is an in-family upgrade: 25.2.01 and 23.3.x upgrade directly to 26.1.01 (BMC 26.1.01 upgrade docs, as of 20 Oct 2026). A move to ServiceNow cannot finish before 3 December, so decide now whether to upgrade first or run an unsupported version during the switch.
| Version | Full support ends | End of version support | Status (20 Oct 2026) |
|---|---|---|---|
| Remedy AR System Server 20.02 | 21 Feb 2024 | 21 Feb 2025 | Ended |
| BMC Helix ITSM OnPrem 23.3.04 | 3 Jun 2026 | 3 Dec 2026 | Limited support |
| BMC Helix ITSM OnPrem 25.2.01 | 3 Jun 2026 | 3 Dec 2026 | Limited support |
| BMC Helix ITSM OnPrem 25.3.01 | 3 Sep 2026 | 3 Mar 2027 | Limited support |
| BMC Helix ITSM OnPrem 25.4.01 | 20 Nov 2026 | 20 May 2027 | Full support |
| BMC Helix ITSM OnPrem 26.1.01 | 6 Mar 2027 | 6 Sep 2027 | Full support |
Source: BMC support site version pages, as of 20 Oct 2026.
AI and analyst news
ServiceNow said on 9 Apr 2026 that AI, data, security and governance "are now in every ServiceNow offering," not a separate purchase, and on 5 May 2026 introduced ServiceNow Otto, which combines "Now Assist, Moveworks, and AI Experience" (ServiceNow newsroom). BMC Helix release 25.2 added HelixGPT Agent Builder for custom agents (BMC Helix newsroom).
ServiceNow said it was named a Leader in the 2026 Gartner Magic Quadrant for IT Service Management Platforms, in its Workflow news post "ServiceNow is a Magic Quadrant Leader in ITSM. Here's why that matters." (29 Jul 2026). BMC Helix said it was named a Leader in the same report "for the 10th time," in its press release "BMC Helix Named a Leader in the 2026 Gartner Magic Quadrant for IT Service Management Platforms" (3 Aug 2026). With two Leaders in one report, placement will not settle this choice; hosting, process fit and what you can carry across will.
ServiceNow vs BMC Helix capabilities side by side
Both platforms cover the core ITIL processes; they differ in how ServiceNow tiers them and where BMC Helix can run. Entries come from the BMC Helix ITSM product page and the ServiceNow ITSM pricing page unless noted, as of 20 Oct 2026.
| Capability | BMC Helix ITSM | ServiceNow ITSM |
|---|---|---|
| Incident management | Core | Foundation |
| Problem management | Core | Advanced |
| Change and release | Core | Change in Advanced; Digital Product Release in Prime |
| Service catalog and requests | BMC Helix Digital Workplace | Foundation |
| Asset management and CMDB | Core | Foundation |
| Deployment | SaaS, or a container deployment on Kubernetes on-premises (BMC docs) | Cloud service; a ServiceNow employee describes a self-hosted "Private Stack" (ServiceNow Community, 1 May 2026) |
| List price | Not published | Not published |
"Core" means BMC Helix lists the capability on its ITSM product page without a tier.
What G2 reviewers say about ServiceNow and BMC Helix
G2 reviewers score ServiceNow higher on every compared measure, and both draw mostly enterprise reviewers, so company size does not explain the gap.
| G2 signal (as of 20 Oct 2026) | BMC Helix ITSM | ServiceNow ITSM |
|---|---|---|
| Rating (reviews) | 3.7/5 (301) | 4.5/5 (2,001) |
| Ease of use / setup / admin | 7.2 / 7.1 / 7.2 | 8.6 / 8.2 / 8.6 |
| Meets requirements | 8.0 | 8.9 |
| Quality of support | 7.5 | 8.6 |
| Enterprise reviewers | 74.1% | 72.8% |
| Most-mentioned con | No theme above 5 mentions; G2's summary says the interface "can feel outdated" | Steep learning curve (72 mentions) |
Source: G2 comparison and product review pages.
Data model differences: Remedy forms vs ServiceNow tables
Remedy stores ITIL records in AR System forms tied to shared Foundation data; ServiceNow uses task-based tables. That difference decides what survives a migration.
How BMC Helix (Remedy) structures ITSM records
BMC Helix ITSM keeps Remedy's AR System model, where records live in forms. Incidents sit in the HPD:Help Desk form, and their work information is a related work log reached through an association (BMC Helix ITSM REST API docs). Underneath every ticket sits Foundation data: companies, organizations, locations, support groups and people, among others (BMC Helix success catalog).
In the CMDB, CIs use the base class BMC_BaseElement and its subclasses, and "relationships are modeled as a base relationship class (BMC_BaseRelationship) with subclasses for different types of relationships" (BMC Helix CMDB docs 26.3). SLA results are measurement records, and request-based compliance is "the total count of service targets met divided by all the resolved measurement records for that review period" (BMC Service Level Management docs 26.3).
How ServiceNow structures ITSM records
In ServiceNow, incidents, problems and changes extend the Task table, and the Task SLA table holds a record per SLA on a task, including breach time and original breach time. CI relationships live in the CI Relationship [cmdb_rel_ci] table as a parent CI, a child CI and a relationship type, and the Identification and Reconciliation Engine prevents duplicate CIs (ServiceNow docs). Our ServiceNow CMDB guide covers classes and relationships in more depth.
How Remedy concepts map to ServiceNow
| Remedy / BMC Helix | ServiceNow equivalent | Mapping decision |
|---|---|---|
| Incidents (HPD forms) with work info | Incident, work notes and comments | Split each work info entry into internal or customer-visible |
| Change requests (CHG forms) and CI associations | Change Request with affected CIs | Rebuild change models and approvals; carry CI links as data |
| Service requests and tasks | Requests, requested items, catalog tasks | Catalog items and variables are rebuilt |
| Foundation data | Users, groups, companies | Load first; every ticket references these |
| 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 type and direction |
| SLA measurement records | Task SLA [task_sla] | History moves as data; definitions and running timers are rebuilt |
AI compared: Now Assist and Otto vs HelixGPT
Both vendors bundle AI with ITSM; the differences are tiers and hosting.
| AI capability | ServiceNow | BMC Helix |
|---|---|---|
| Packaging | AI "now in every ServiceNow offering" (ServiceNow newsroom) | HelixGPT "is not licensed as a separate SKU" (BMC docs 26.3) |
| Assist for agents and employees | Now Assist and Moveworks in every ITSM package (ServiceNow pricing page) | Employee Navigator for all BMC Helix ITSM users (BMC Helix newsroom) |
| Packaged AI agents | AI Agents for ITSM and L1 Service Desk AI Specialist in Prime (ServiceNow pricing page) | Catalog Curator through BMC Helix Virtual Agent (BMC docs 26.3) |
| Build your own | Net-new agents at Prime; out-of-the-box agents configurable at Foundation and Advanced (ServiceNow docs, updated 10 Sep 2026) | HelixGPT Agent Builder (BMC Helix newsroom) |
| On-premises | Not part of the standard cloud service | ITSM OnPrem entitlement lists Employee Navigator and Insight Finder (BMC docs 26.3) |
All rows as of 20 Oct 2026.
The AI verdict: ServiceNow keeps net-new agents for Prime, and BMC Helix names fewer HelixGPT features on-premises, so check your license. 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: ServiceNow shows "Get Custom Quote" and BMC Helix "Request Pricing" (vendor pages, as of 20 Oct 2026). What you can compare in advance is upgrade cadence, hosting, skills and the move itself.
For a public benchmark, Vendr reports a median ServiceNow contract of $129,871 a year across 109 purchases (Vendr, last updated Feb 2026, as of 20 Oct 2026). That covers all ServiceNow products, not ITSM alone; our ServiceNow pricing guide covers the packages and renewal levers. We found no comparable public benchmark for BMC Helix ITSM.
| Cost factor | ServiceNow | BMC Helix |
|---|---|---|
| Upgrades | Releases ship in named families, and an upgrade moves your instance to a new family (ServiceNow docs, updated 10 Sep 2026). Confirm each family's support window with ServiceNow | On-premises: an upgrade at least every 18 months to stay supported, and direct upgrades only from the last two releases (BMC policy, updated 1 Jan 2025) |
| Infrastructure | Vendor-hosted | On-premises runs on Kubernetes that you operate (BMC docs) |
| Skills | 72 G2 reviewers cite a steep learning curve | Existing AR System skills carry over |
| Cost complaints | 60 G2 reviewers cite high licensing and implementation costs | No cost theme on G2 |
G2 figures as of 20 Oct 2026; review volumes differ, so read mention counts as themes, not rates.
Switching cost belongs in every option. A move within BMC is still a migration: BMC's Remedy-to-SaaS service costs 120 or 300 success credits and leaves non-standard configurations and integrations for you to remediate (BMC Helix success catalog, updated 30 Sep 2026). Line up your renewal date with the support table and decide before your notice period starts.
BMC Remedy vs ServiceNow: which should you choose?
A Remedy shop has three supported destinations, and BMC Helix runs programs for the first two.
| Option | What it involves | Choose this if |
|---|---|---|
| BMC Helix on-premises | The 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 |
| BMC Helix SaaS | BMC's service moves Remedy on-premises (20.02 or later) to BMC Helix ITSM 26.1 with BMC Helix Data Manager; BMC estimates 14 to 20 weeks (BMC Helix success catalog, updated 30 Sep 2026) | You want the Remedy process model without running infrastructure |
| ServiceNow | A new implementation, plus mapping and migrating your history | You want one platform across departments |
Five questions to decide
- Which release are you on? If it is 20.02 or earlier, you are past end of version support. If it is 23.3.04 or 25.2.01, your date is 3 Dec 2026 (BMC support site, as of 20 Oct 2026).
- Must ITSM data stay on your own infrastructure? If yes, BMC Helix on-premises is the clearest fit; budget for an upgrade inside each 18-month window, or ask ServiceNow whether a self-hosted option applies.
- How much Remedy customization still earns its keep? If most AR System workflow works around old processes, 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.
- 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.
Mostly "stay close to what we have" points to BMC Helix; mostly "one platform, fresh design" points to ServiceNow. To compare more platforms, see our enterprise service desk software guide.
Migrating from Remedy to ServiceNow
A Remedy to ServiceNow migration moves ticket history as data and rebuilds process logic. Our BMC Remedy to ServiceNow migration guide covers the full plan; here is what is specific to the pair.
| 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 | Catalog items and variables | Original created and resolved timestamps |
| CIs, relationships and attachments | Assignment rules, notifications, priority matrix | Internal vs public work info |
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 (BMC Remedy 19.02 tuning docs, as of 20 Oct 2026), so extraction needs paging. On the ServiceNow side, import sets stage rows and transform them into the target; with no coalesce field, "all imported rows are treated as new records" (ServiceNow docs). Attachments default to a 1,024 MB maximum (ServiceNow Attachment API docs, as of 13 Oct 2026). If each record carries its Remedy ID as the coalesce key, a delta load updates records instead of duplicating them, which is how late changes in the freeze window get picked up.
Run the move as a controlled change:
- Discover: forms, record counts, Foundation data, CI classes, integrations.
- Map: states, priority matrix, categorization, groups, every relationship subclass.
- Test migration: a full copy in sub-production, reconciled.
- Cutover with delta sync: freeze Remedy, load the final delta, run go/no-go.
- Reconcile: counts, links, attachments and timestamps per record type.
- Hypercare: watch rebuilt SLAs, routing and notifications.
ServiceNow vs Remedy evaluation checklist
- Confirm your version's end-of-support date on BMC's support site; if it is 3 Dec 2026, decide this month whether to upgrade first.
- Note your BMC renewal date and notice period, and work back from them.
- Export Foundation data counts: companies, people, support groups, categorization tiers.
- Export CI class and relationship subclass lists, and mark which drive impact analysis.
- Count records per form, including closed tickets and attachments.
- 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, then get quotes for all three options.
- Agree a freeze window, a reconciliation method and go/no-go criteria, with one named owner.
Facts checked October 20, 2026 from ServiceNow ITSM pricing, BMC Helix, ServiceNow newsroom and Vendr. No vendor paid for this article. How we research
ServiceNow vs Remedy FAQ
Is BMC Remedy the same as BMC Helix?
Largely, yes. BMC Helix describes BMC Helix ITSM as "the next generation of Remedy" (BMC Helix, as of 20 Oct 2026). Current releases carry the BMC Helix ITSM name, keep the AR System foundations, and run as SaaS or as a container deployment on-premises.
Is BMC Remedy still supported?
Not in its Remedy-numbered releases. Remedy AR System Server 20.02 reached end of version support on 21 Feb 2025. Its successor, BMC Helix ITSM, is supported per version: on-premises 23.3.04 and 25.2.01 end on 3 Dec 2026, 25.3.01 on 3 Mar 2027, 25.4.01 on 20 May 2027 and 26.1.01 on 6 Sep 2027 (BMC support site, as of 20 Oct 2026).
Which is better, ServiceNow or BMC Helix?
It depends on what you value. On G2, ServiceNow ITSM rates 4.5/5 from 2,001 reviews against 3.7/5 from 301 for BMC Helix ITSM (G2, as of 20 Oct 2026). ServiceNow suits a multi-department platform. BMC Helix suits teams that value continuity and on-premises hosting.
Can you move Remedy ticket history to ServiceNow?
Yes, with mapping and testing. Incidents, problems, changes, requests, knowledge, Foundation data, CIs and relationships can all move as data. Workflows, business rules, SLA definitions and running SLA timers do not migrate; they are rebuilt on ServiceNow. Use a coalesce key such as the Remedy ID so delta loads update records instead of duplicating them.
How long does a Remedy to ServiceNow migration take?
There is no neutral public benchmark. Duration depends on record and attachment volume, how much AR System customization you rebuild, how cleanly Foundation data and relationship subclasses map, and how many test migrations reconciliation takes. For a different move, Remedy on-premises to BMC Helix SaaS, BMC Helix estimates 14 to 20 weeks for its own service (BMC Helix success catalog, updated 30 Sep 2026).
Gartner does not endorse any vendor, product or service depicted in its research publications, and does not advise technology users to select only those vendors with the highest ratings or other designation. Gartner research publications consist of the opinions of Gartner's research organization and should not be construed as statements of fact. Gartner disclaims all warranties, expressed or implied, with respect to this research, including any warranties of merchantability or fitness for a particular purpose. GARTNER and MAGIC QUADRANT are registered trademarks of Gartner, Inc. and/or its affiliates in the U.S. and internationally.
Written by
Ayush BothraFounding Member, MigrateX
Ayush writes about ITSM platforms, pricing and what it takes to move a service desk to a new platform without losing its history.


