Methodology: built from BMC and BMC Helix support-lifecycle tables, support policies, product pages and documentation, plus G2 and Gartner Peer Insights listings, all checked on 1 Oct 2026. No vendor reviewed or paid for this article. We did not run hands-on tests.
BMC Remedy is now BMC Helix ITSM. BMC Helix calls it "the next generation of Remedy" (BMC Helix, as of 1 Oct 2026). If you still run Remedy on your own servers, the date to watch is 3 December 2026, when BMC Helix ITSM OnPrem 23.3.04 and 25.2.01 reach end of version support (BMC, as of 1 Oct 2026).
This guide is for Remedy platform owners: what Remedy is today, which dates matter, what changes on 3 December, and your three routes: upgrade on-premises, move to BMC Helix SaaS, or switch platforms.
Key takeaways
- BMC Helix, the company BMC announced it would split off on 9 Oct 2024, now sells Remedy as BMC Helix ITSM, "the next generation of Remedy" (BMC Helix; BMC Helix, as of 1 Oct 2026).
- Remedy AR System Server 20.02 reached end of version support on 21 Feb 2025 (BMC, as of 1 Oct 2026).
- BMC Helix ITSM OnPrem 23.3.04 and 25.2.01 lose support on 3 Dec 2026; the newest on-premises release, 26.1.01, is supported until 6 Sep 2027 (BMC, as of 1 Oct 2026).
- BMC documents a direct, zero-downtime upgrade to 26.1.01 from 23.3.x and 25.2.01 (BMC docs, as of 1 Oct 2026).
What is BMC Remedy now?
BMC Remedy is the IT service management suite now sold as BMC Helix ITSM: incident, problem, change, release, service request, asset, knowledge and service level management with a CMDB, built on BMC's AR System platform. BMC Helix lists those modules on the page it keeps for Remedy searchers (BMC Helix, as of 1 Oct 2026). Three names changed; the process model stayed.
| What you knew as | What it is called now | What changed |
|---|---|---|
| Remedy ITSM | BMC Helix ITSM | Same ITSM applications, released as BMC Helix versions such as 26.1.01 |
| Remedy Action Request System | AR System, deployed inside BMC Helix Innovation Suite | BMC's docs call AR System "formerly known as Remedy Action Request System"; on-premises installs deploy BMC Helix Innovation Suite as the core platform |
| BMC Software | BMC Helix, Inc. | BMC announced on 9 Oct 2024 that "BMC Helix will be the name of the company for the digital service and operations management business unit" |
Sources: BMC Helix, BMC, BMC docs, BMC docs, BMC Helix, as of 1 Oct 2026.
How BMC Helix ITSM is deployed
It runs as SaaS hosted by BMC Helix or on your own infrastructure. On-premises releases are now "a container deployment of BMC Helix Innovation Suite and Service Management applications" on Kubernetes (BMC docs, as of 1 Oct 2026). Older non-containerized Remedy installs (20.02 and earlier) are what BMC's HOME program exists to move (BMC Helix, as of 1 Oct 2026).
Who still runs Remedy
BMC Helix says "more than 6,500 IT organizations" trust its ITSM solutions (BMC Helix, as of 1 Oct 2026). Gartner Peer Insights now lists the old suite as "BMC Remedy Service Management Suite (Legacy)" (Gartner Peer Insights, as of 1 Oct 2026). On G2, BMC Helix ITSM rates 3.7/5 from 297 reviews (G2, as of 1 Oct 2026).
In one sentence: Remedy did not disappear, it was renamed and containerized, and its support clock now runs release by release.
BMC Remedy support dates that matter in 2026
BMC publishes support dates per version, not for the product line. These are the ones a Remedy owner acts on.
| Version | End of version support | Status on 1 Oct 2026 |
|---|---|---|
| Remedy AR System Server 20.02 | 21 Feb 2025 | Ended |
| BMC Helix ITSM OnPrem 23.3.04 | 3 Dec 2026 | Limited support |
| BMC Helix ITSM OnPrem 25.2.01 | 3 Dec 2026 | Limited support |
| BMC Helix ITSM OnPrem 26.1.01 (newest) | 6 Sep 2027 | Full support |
Sources: Remedy AR System Server versions and BMC Helix ITSM OnPrem versions, as of 1 Oct 2026.
The releases in between, 25.3.01 and 25.4.01, end on 3 Mar 2027 and 20 May 2027 (BMC, as of 1 Oct 2026), so they buy less time than 26.1.01. Our ServiceNow vs Remedy comparison has the full version table.
BMC Remedy end of life: what changes on 3 December 2026
Nothing switches off on 3 December 2026. What ends is BMC's support for two releases. BMC's policy for containerized BMC Helix products gives each release 1 year of full support from general availability, then 6 months of limited support, then end of support (BMC, as of 1 Oct 2026).
| Support stage | What BMC provides | For 23.3.04 and 25.2.01 |
|---|---|---|
| Full support | Patches, hotfixes or workarounds for functional issues and security vulnerabilities | Ended 3 Jun 2026 |
| Limited support | Fixes for critical security vulnerabilities and major defects only; no enhancements | Now, until 3 Dec 2026 |
| End of support | "No new sustaining releases, enhancements, patches, or hotfixes" | From 3 Dec 2026 |
Sources: BMC support policy and BMC Helix ITSM OnPrem versions, as of 1 Oct 2026.
Your system keeps running, but gets no new fixes. If your security policy requires vendor-supported software, that policy sets your real deadline. The policy adds up to 18 months per release, and every 25.x and 26.x release in BMC's table follows it (BMC, as of 1 Oct 2026), so staying on-premises means upgrading at least that often.
Your options: upgrade BMC Helix on-premises, move to BMC Helix SaaS, or switch
You have three routes, and switching splits by platform.
| Option | What it involves | Choose this if |
|---|---|---|
| Upgrade to BMC Helix ITSM OnPrem 26.1.01 | In-place upgrade from 23.3.x or 25.2.01; supported until 6 Sep 2027 | Data must stay on your infrastructure and your customizations still fit |
| Move to BMC Helix ITSM SaaS | BMC Helix hosts it; migration with BMC Helix Data Manager from 20.02 or later | You want the Remedy process model without hosting the platform |
| Switch to ServiceNow | New implementation, plus mapping and migrating history | IT, HR and facilities should share one platform (ServiceNow vs Remedy) |
| Switch to Jira Service Management or Freshservice | New implementation, plus mapping and migrating history | IT is the main scope and you will redesign processes (Jira Service Management alternatives, Freshservice vs ServiceNow) |
Sources: BMC docs, BMC, BMC docs, as of 1 Oct 2026.
If self-hosting matters, check the target still sells it. Atlassian stopped selling Data Center to new customers on 30 Mar 2026, and Jira Service Management Data Center goes read-only on 28 Mar 2029 (Atlassian, as of 1 Oct 2026).
The verdict: if your Remedy customizations still earn their keep, staying within BMC Helix is the shorter path. If they mostly work around old processes, a switch is the moment to drop them.
BMC Remedy alternatives
The usual shortlist is ServiceNow, Jira Service Management and Freshservice. See our top ITSM tools for 2026, ServiceNow alternatives and our guide to choosing ITSM software. Neither BMC Helix nor ServiceNow publishes list prices; BMC Helix offers "Request Pricing" and ServiceNow a custom quote (BMC Helix; ServiceNow, as of 1 Oct 2026). Our ServiceNow pricing guide explains how those quotes are built.
What BMC's upgrade and migration tooling covers
BMC documents three tooled paths, one per starting point. All stay inside BMC Helix.
| Path | BMC method and tooling | What moves | What you redo or check |
|---|---|---|---|
| OnPrem 23.3.x or 25.x to OnPrem 26.1.01 | In-place upgrade; zero-downtime by default; upgrade BMC Helix Platform Common Services first | Everything stays in place | Users are logged out when Mid Tier and Smart IT pods restart; 21.3.x and 22.1.x need a step upgrade first |
| Non-containerized Remedy to BMC Helix OnPrem | Fresh containerized install plus data migration; BMC Helix Data Manager for data; Workflow Migration Utility for customizations and overlays | ITSM, Digital Workplace Catalog, Smart IT and Smart Reporting data; customizations and overlays | Integrations not built on AR API, REST API or web services are redesigned |
| Remedy on-premises (20.02 or later) to BMC Helix SaaS | BMC Helix Data Manager, in stages that include initial data migration, delta migration and an emulated cutover | Data from supported forms; customizations and overlays via BMC utilities | No direct-write database access, no direct SQL in workflow, no third-party applications in the cloud, no Base Mode changes |
Sources: BMC docs, BMC docs, BMC docs, as of 1 Oct 2026.
BMC Helix also sells the SaaS path as a service covering standard configurations and up to three integrations; non-standard ones are left to the customer (BMC Helix, as of 1 Oct 2026). Run it as a migration, with test loads and reconciliation.
Switching vendors has no BMC tooling. Incidents, problems, changes, requests, knowledge, people and groups, CIs, relationships and attachments move as data after mapping. Workflows, filters, escalations, business rules, SLA definitions, running SLA timers and the priority matrix are rebuilt, not migrated. Our ITSM migration guide covers the phases; the ServiceNow migration guide covers the most common destination.
A backwards plan from 3 December 2026
On 1 Oct 2026, 63 days remain before 23.3.04 and 25.2.01 lose support (BMC, as of 1 Oct 2026). There is no neutral public benchmark for a Remedy move. BMC Helix's own estimate for its SaaS migration service is 18 to 20 weeks with standard testing and 21 to 24 weeks with comprehensive testing (BMC Helix, as of 1 Oct 2026). By that estimate, a SaaS move started today ends after 3 December.
So the decision before 3 December is narrow: upgrade on-premises first, or run unsupported while a larger move completes. The quarters below are checkpoints tied to BMC's dates, not estimates.
| Window | BMC date in the window | What to have done |
|---|---|---|
| Now to 3 Dec 2026 | 23.3.04 and 25.2.01 end of version support | Version confirmed; bridge upgrade or unsupported running decided and signed off by security; inventory started |
| Q1 2027 | 25.3.01 ends 3 Mar 2027; 26.1.01 full support ends 6 Mar 2027 | Destination chosen, quotes in, history scope agreed, mapping started |
| Q2 2027 | 25.4.01 ends 20 May 2027 | Test migrations reconciled; workflows, SLAs and notifications rebuilt |
| Q3 2027 | 26.1.01 ends 6 Sep 2027 | Cutover with delta sync and go/no-go done, or the next upgrade planned |
Dates: BMC Helix ITSM OnPrem versions, as of 1 Oct 2026.
On Remedy 20.02 or earlier you are already unsupported; use the same checkpoints, with BMC's HOME program in place of the bridge upgrade.
BMC Remedy checklist
- Find your exact release and its end-of-version-support date, and line it up with your BMC renewal and notice period.
- Agree with security and audit owners what running an unsupported release means.
- If staying on-premises, check your Kubernetes platform against the target release's requirements.
- List AR System customizations, overlays and integrations; mark what to retire.
- Check each integration method against BMC's supported list.
- If SaaS is an option, find direct SQL in workflow and direct database writes.
- Count records per form, including closed tickets, attachments, CIs and relationships.
- Decide which history moves, which is archived, and how timestamps are kept. An audit of your legacy help desk data helps.
- Document SLA definitions, business calendars and the priority matrix for rebuild.
- Get quotes for every route you are considering.
- Name a project lead and agree the freeze window, delta sync, reconciliation and go/no-go criteria (ITSM migration checklist).
FAQ
Methodology
We built this guide from BMC's version-support tables and support policy, and BMC Helix product pages and documentation, checked on 1 October 2026. We confirmed helixops.ai is BMC Helix's official site first: BMC's Remedy and documentation URLs redirect there, and it carries the BMC Helix, Inc. copyright. Ratings come from G2 and Gartner Peer Insights. We read pages ranking for "bmc remedy" for gaps but do not cite them.
Disclosure: MigrateX, the publisher of this article, runs ITSM data migrations, including between platforms named here. No vendor reviewed or paid for this article.