Freshservice vs BMC Helix ITSM: Architecture, TCO & Migration

Freshservice vs BMC Helix ITSM: Architecture, TCO & Migration

Freshservice and BMC Helix ITSM occupy different ends of the ITSM market. Freshservice is a cloud-only, Freshworks-ecosystem product optimized for speed-to-value and mid-market IT teams. BMC Helix ITSM is an enterprise-grade, multi-deployment platform descended from Remedy, built for organizations with deep ITIL maturity requirements and complex infrastructure. Choosing between them comes down to deployment flexibility, cost tolerance, integration complexity, and how much customization your team actually needs.

This guide breaks down architecture, real-world pricing (with sources and reconciliation), API constraints for both platforms, migration risks, security architecture, and the specific scenarios where each platform wins.

Pricing figures verified against vendor sources and third-party benchmarks as of Q2 2025. API behavior based on platform documentation current as of the same period.

---

What is Freshservice?

Freshservice is a cloud-native ITIL-aligned service desk covering incident, problem, change, release, knowledge, and asset management. It is part of the Freshworks product family — alongside Freshdesk (customer support), Freshsales (CRM), and Freshchat (messaging) — which means native cross-product integrations are first-class, not bolt-ons.

Freshservice is cloud-only. There is no on-prem or hybrid deployment option. Every customer runs on a shared multi-tenant SaaS instance managed entirely by Freshworks. That constraint defines the platform's ceiling as much as its floor.

---

What is BMC Helix ITSM?

BMC Helix ITSM is an enterprise IT Service Management platform managing incidents, changes, problems, assets, and service requests. It is the cloud-era successor to BMC Remedy, rebuilt on microservices and container infrastructure while retaining the AR System workflow engine that Remedy customers built decades of process logic around.

Helix supports SaaS, on-premises, hybrid, and multi-cloud deployments. For organizations with regulatory data residency requirements, air-gapped network mandates, or legacy Remedy investments, it is one of the few enterprise ITSM platforms still supporting true on-prem deployment in 2025.

---

Architecture: How the Two Platforms Are Built

Freshservice architecture

Freshservice runs as a fully managed multi-tenant SaaS application. The API is RESTful, uses JSON for data exchange, and supports full CRUD operations across ITSM objects. Infrastructure, patching, scaling, and disaster recovery are handled by Freshworks. No servers, databases, or middleware to manage.

This is Freshservice's biggest architectural advantage and its principal constraint. You cannot control database-level operations, cannot host custom middleware alongside the platform, and cannot isolate your tenant for compliance scenarios requiring dedicated infrastructure. Multi-tenancy is a hard ceiling.

BMC Helix ITSM architecture

BMC Helix ITSM architecture comprises three layers: the underlying database, the Action Request (AR) System server, and the Helix ITSM application layer. The AR System processes all data entered by ITSM applications and acts as the workflow engine between the application layer and the database — handling form rendering, business logic, access control, and escalation rules in a single tier.

BMC Helix Innovation Studio combines AR System with the Helix Platform, giving administrators a unified development environment for custom applications, integrations, and process automation that sits above the core ITSM layer.

For high availability, Helix's containerized SaaS deployment uses multiple hardened data centers with redundant hardware. Most hardware failures are transparent to end users because the software layer handles failover automatically. On-premises deployments require the customer to replicate this architecture themselves.

Dimension	Freshservice	BMC Helix ITSM
Deployment options	Cloud-only SaaS	SaaS, on-prem, hybrid, multi-cloud
Database control	None (fully managed)	Full (on-prem), abstracted (SaaS)
Workflow engine	Visual automator, no-code	AR System (deep custom logic, scripting)
Multi-tenancy model	Shared multi-tenant	Dedicated instances available
API style	REST v2 (primary), REST v1 (legacy)	Simplified REST + Platform REST + SOAP
Custom form support	Limited (custom fields, no custom forms)	Full (AR System custom forms and workflows)

---

How much does Freshservice cost?

Freshservice publishes its pricing publicly. Per-agent rates on annual billing as of Q2 2025:

Tier	Monthly billing	Annual billing	Key capabilities
Starter	$29/agent/month	$19/agent/month	Incident management, knowledge base, SLA management, 1,000 orchestration transactions/month
Growth	$59/agent/month	$49/agent/month	Adds asset management, service catalog, approval workflows
Pro	$119/agent/month	$99/agent/month	Adds problem, change, release management, project management, advanced analytics
Enterprise	Custom	Custom	Adds sandbox environment, audit logs, 20,000 orchestration transactions/month

Hidden costs to model upfront

Three cost categories sit outside the headline per-agent price and commonly cause TCO miscalculations:

1. Freddy AI Copilot: $29/agent/month on annual billing, $35/month on monthly billing. This is a separate line item — not included in any published tier.

2. IT asset management overages: Published tiers include a fixed asset count. Per-asset overage fees apply beyond the included limit, and manually-added assets may count against this limit depending on contract language. Get the included asset count and overage rate in writing before signing. Organizations without clarity on this have reported unexpected charges exceeding $10,000 on annual renewals.

3. Orchestration transaction limits: The Starter tier's 1,000 transactions/month cap is easily exceeded by automation-heavy environments. Enterprise tier's 20,000 is the ceiling without custom negotiation.

---

How much does BMC Helix ITSM cost?

BMC Helix ITSM does not publish pricing on its website. All contracts are quote-based. Three distinct price points appear in the market, and they refer to different purchasing contexts — reconciling them matters before using any figure in a budget model.

The three BMC Helix price points, explained

Source	Price	What it represents
BMC Salesforce AppExchange listing (Q1 2025)	$114.75/named user/month	Reseller/AppExchange channel pricing; typically lower than direct list
Third-party benchmark data (IT analyst surveys, 2024)	$115–$180/agent/month negotiated	Actual signed contract rates after negotiation, mid-market to enterprise
BMC list price (Foundation/Standard/Advanced tiers)	$180–$320/agent/month	Undiscounted rack rates; starting point before negotiation, rarely what enterprises pay

Practical implication: A 200-agent enterprise buying direct from BMC at negotiated rates should budget $115–$180/agent/month for the base ITSM license. The $180–$320 list price is the ceiling, not the expectation. AppExchange reseller pricing is available for smaller deployments without direct enterprise agreements.

Third-party benchmarking consistently places BMC Helix ITSM 18–21% above the average enterprise ITSM platform cost at equivalent agent counts, before add-on modules.

Module add-on costs

A base Helix ITSM license covers incident, problem, and change management. Most enterprise deployments require additional modules:

Module	Approximate add-on cost (list price)
Discovery (network/endpoint scanning)	$80–$140/agent/month
CMDB	$60–$100/agent/month
AI and Cognitive Service Management	$40–$90/agent/month
Digital Workplace (self-service portal, chatbot)	Varies; typically $30–$60/agent/month

Minimum contract scale

Enterprise contracts for smaller mid-market deployments (200–500 agents) typically start at approximately $280,000 annually for base licensing. Implementation services, which are almost always required, are additional.

---

TCO comparison: Freshservice vs BMC Helix ITSM

100-agent deployment, 3-year horizon:

Cost Factor	Freshservice (Pro tier)	BMC Helix ITSM (negotiated Standard)
Per-agent license	$99/agent/month (annual)	$115–$180/agent/month (negotiated)
Annual license cost	~$119K	~$138K–$216K
Implementation	Days to weeks; largely self-serve	8–20 weeks; consultant-led; $50K–$200K+
Key add-ons	Freddy AI (+$29/agent), asset packs, ITOM	Discovery, CMDB, AIOps, Digital Workplace
Infrastructure	$0 (SaaS, included)	$0 (SaaS) to $50K–$200K+/year (on-prem)
Admin headcount	0.5–1 FTE	1–3+ FTEs (AR System administration is a specialized skill)
3-year total estimate	$360K–$500K	$500K–$1.5M+

Freshservice wins on cost predictability and implementation simplicity. BMC Helix wins when deployment flexibility, deep AR System workflow customization, or on-premises data residency requirements justify the premium.

---

ITIL 4 Practice Coverage: Native vs. Add-on

A frequent evaluation gap is assuming both platforms cover the same ITIL 4 practices natively. They don't.

ITIL 4 Practice	Freshservice (native tier)	BMC Helix ITSM (native tier)
Incident Management	All tiers	Base license
Service Request Management	Growth+	Base license
Problem Management	Pro+	Base license
Change Enablement	Pro+	Base license
Knowledge Management	All tiers	Base license
Asset Management	Growth+	Base license (limited); full via Discovery add-on
CMDB / Service Configuration Management	Not a full CMDB (asset tracking only)	Separate CMDB module; full dependency mapping with Discovery
Release Management	Pro+	Base license
Service Level Management	All tiers	Base license
Availability/Capacity Management	Enterprise (limited)	Advanced tier + AIOps module
IT Continuity Management	Not native	Advanced tier
Workforce & Agent Management	Enterprise	All tiers

Key finding: For organizations requiring full CMDB with CI dependency mapping and discovery, Freshservice's asset management does not substitute. Helix CMDB with Discovery is a fundamentally different capability class.

---

Security Architecture and Authentication Comparison

Security and identity management are standard enterprise evaluation inputs that most ITSM comparison content omits.

Feature	Freshservice	BMC Helix ITSM
SSO support	SAML 2.0, OAuth 2.0	SAML 2.0, OAuth 2.0, Kerberos (on-prem)
SCIM provisioning	Yes (Enterprise tier)	Yes
MFA	Yes (built-in + IdP-enforced)	Yes
IP allowlisting	Yes	Yes
Role-based access control	Role templates; field-level restrictions limited	Granular field-level, form-level, and group-level permissions via AR System
Audit log access	Enterprise tier; 90-day retention (lower tiers vary)	Full audit log; retention configurable
Data residency	Freshworks-controlled regions; limited customer control	Customer-controlled (on-prem), or region-selectable (SaaS)
Encryption at rest	AES-256	AES-256
Encryption in transit	TLS 1.2+	TLS 1.2+
FedRAMP / government compliance	Not FedRAMP authorized (as of Q2 2025)	BMC Helix for Government available; FedRAMP authorization pathway exists

Practical implication for regulated industries: If your organization requires FedRAMP authorization, FIPS-140-2 compliance, or on-premises data residency, Freshservice is not a viable option as of Q2 2025. BMC Helix's government-specific offering addresses these requirements.

---

SLA and Uptime Commitments

Metric	Freshservice	BMC Helix ITSM (SaaS)
Published SLA	99.9% uptime	99.9% uptime
SLA credits	Yes, per published terms	Yes, per enterprise agreement
Status page	status.freshservice.com	Available
Planned maintenance windows	Customer-notified; typically off-peak	Customer-negotiable for enterprise tiers
Data backup frequency	Daily (published); restoration per support request	Configurable; enterprise agreements specify RPO/RTO

Both platforms publish 99.9% uptime SLAs for their SaaS deployments. On-premises BMC Helix HA architecture targets equivalent availability but places infrastructure responsibility on the customer.

---

API Comparison: Integration and Migration Implications

Freshservice API

Freshservice offers two API versions. V1 is the legacy API — still functional, but with lower rate limits and fewer endpoints. V2 is the current standard and should be used for all new integrations and migration tooling.

Pagination: Freshservice uses page-number-based pagination with page and per_page query parameters. Default page size is 30 records; maximum is 100. This is not cursor-based pagination, which means large historical exports require sequential page iteration. For 500,000 ticket records at 100 per page, that's 5,000 sequential API calls before accounting for related objects.

Rate limits (V2, accounts created after September 1, 2020): Rate limits are applied account-wide — not per agent, not per IP address. The specific cap varies by subscription tier. Certain API operations have sub-limits within the overall account limit.

The ?include= multiplier: Appending ?include=requester or ?include=stats to list endpoints embeds related objects in the response — but each included relation counts against the rate limit as additional API calls internally. An ?include=requester on a ticket list call can triple effective rate limit consumption. For background sync jobs fetching ticket lists with embedded relations, this is the most common cause of rate limit exhaustion during migrations.

Incremental export behavior: Freshservice's export function returns new and updated records since the last export timestamp — specifically, up to 100 created and 50 updated records per export cycle. Plan your migration pipeline around incremental rather than full-dump extraction to avoid rate limit collisions.

BMC Helix ITSM API

BMC provides two REST API layers and legacy SOAP support:

API Layer	Use case	Notes
Simplified REST API	Standard ITSM operations (incidents, changes, problems, assets)	BMC's recommended layer for most integrations
Platform REST API (AR System)	Custom forms, non-standard data models, advanced operations	Required when working with custom AR System forms
SOAP web services	Legacy integrations	Still supported; not recommended for new development

Form-based data model: BMC Helix's AR System uses interface forms to control data operations. Forms with the suffix _Create handle insert/submit operations. Other forms handle updates. Understanding which interface form maps to which ITSM operation is prerequisite knowledge for any integration or migration developer — this is a meaningful onboarding cost compared to Freshservice's straightforward REST endpoints.

Rate limits: BMC Helix ITSM's SaaS API does not publish explicit per-minute rate limit figures equivalent to Freshservice's documented caps. On-premises deployments are constrained by server capacity rather than platform-enforced limits. For SaaS integrations, BMC's guidance is to implement exponential backoff and contact support for throughput requirements that exceed standard use cases.

Authentication: Both Simplified REST and Platform REST APIs use JWT token-based authentication. Tokens are scoped to the requesting user's permission set — there is no separate "service account" API key model equivalent to Freshservice's API key approach. Integration service accounts must be provisioned as licensed named users unless BMC's Integration Service is used.

---

When should you choose Freshservice?

Freshservice is the better choice when:

• You want fast time-to-value. No infrastructure to provision. Configuration is self-service. A functional ITSM environment is achievable in days to two weeks.
• Your team is 10–500 agents managing standard ITIL practices without heavy workflow customization.
• Transparent, predictable pricing matters. Published per-agent rates let you forecast without a sales cycle.
• You're already in the Freshworks ecosystem. Native integrations with Freshdesk, Freshsales, and Freshchat are first-class.
• Cloud-only deployment is acceptable. No on-prem, no hybrid, no data residency control beyond Freshworks' available regions.
• You don't need a full CMDB. Asset tracking with basic relationships is sufficient.
• FedRAMP or government compliance is not required.

G2 reviewers rate Freshservice 9.2/10 for ease of use — highest among major ITSM platforms — reflecting genuine advantage for teams without dedicated ITSM administrators.

---

When should you choose BMC Helix ITSM?

BMC Helix ITSM is the better choice when:

• On-prem or hybrid deployment is required. Government, defense, regulated financial services, and healthcare organizations with data residency mandates.
• FedRAMP authorization is required. Helix for Government supports this pathway; Freshservice does not as of Q2 2025.
• Deep ITIL process customization is necessary. AR System supports complex multi-stage approval chains, field-level business rules, conditional workflow branching, and custom form logic that Freshservice's automation layer cannot replicate.
• Enterprise-scale CMDB with discovery is required. Helix CMDB with Discovery provides CI dependency mapping, automated network/endpoint scanning, and impact analysis that Freshservice asset management does not offer.
• Change management processes are complex. G2 data rates BMC Helix Change Management 8.8/10 vs. Freshservice's 8.6/10, with enterprise reviewers specifically citing BMC's multi-approval workflow depth.
• You have the budget and dedicated administration team. AR System administration is a specialized skill set. Plan for 1–3 dedicated administrators for mid-to-large deployments.

---

What does migrating between these platforms involve?

Migrating from BMC Helix ITSM to Freshservice

What migrates cleanly: Incidents, service requests, change records, problem records, knowledge articles, and basic user/contact data. These objects map well to Freshservice's ITIL-aligned data model.

What does not migrate cleanly:

• AR System custom forms and workflows. BMC's custom workflow logic has no direct equivalent in Freshservice. Each custom form must be rebuilt as a Freshservice workflow automator rule or dropped. This is design work, not scripting work.
• CMDB relationships and CI data. Freshservice has asset management, not a full CMDB. Complex CI class hierarchies and dependency relationships will lose fidelity. Evaluate upfront which CI relationships are operationally necessary versus archival.
• Custom integrations using SOAP. Must be rewritten against Freshservice REST API v2.
• Multi-stage approval chains. BMC's Approval Server supports conditional, parallel, and delegated approval logic. Freshservice approval workflows are simpler. Some approval processes will need redesign, not just migration.

Data extraction from BMC Helix: Per BMC's standard contract terms, upon written request within 45 days of contract termination, BMC will make customer content available for retrieval in an industry-standard format. After 45 days, BMC has no obligation to retain that data. Begin export planning at least 90 days before contract end — not 45.

Migrating from Freshservice to BMC Helix ITSM

What migrates cleanly: Ticket data, contacts, knowledge articles, and basic asset records translate well into Helix's data model.

What requires re-architecture:

• Freshservice workflow automations. Must be rebuilt as AR System workflows — a paradigm shift from visual rule-builder to form-based workflow logic.
• Freshworks Marketplace apps. Third-party integrations installed via the Freshworks Marketplace have no equivalent in Helix. Each integration must be re-evaluated and re-implemented via Helix Integration Service or custom REST calls.
• Orchestration transactions. Freshservice's consumption-based orchestration model does not translate to Helix's automation paradigm. Map each orchestration use case to its Helix equivalent before migration begins.

Data extraction from Freshservice: Use REST API v2 with page-based pagination (max 100 records/page). Account-wide rate limits mean large historical exports can take 24–72 hours depending on ticket volume and plan tier. Run extraction during off-peak hours and use incremental pulls rather than full re-dumps if the source system remains live during migration.

---

Migration data map: Freshservice ↔ BMC Helix ITSM

Data Object	Freshservice Field/Form	BMC Helix Field/Form	Migration Notes
Incidents	Tickets (type: Incident)	HPD:Help Desk	Status mapping required (see pitfalls below)
Service Requests	Tickets (type: Service Request)	SRM:Request	Catalog item structure doesn't auto-map; manual catalog rebuild required
Changes	Change records	CHG:Infrastructure Change	Approval workflow logic requires rebuild
Problems	Problem records	PBM:Problem Investigation	Root cause CI links may break if CMDB not migrated
Assets	Assets	AST:ComputerSystem / BMC.ASSET	CI class hierarchy mapping required
Knowledge Articles	Solution Articles	KBA:Knowledge Article	Category taxonomy differs; manual remapping needed
Users/Agents	Agents + Requesters	CTM:People	Role model differs significantly; permission audit required
SLA Policies	SLA Policies (business hours, escalations)	SLA:Agreements	Does not transfer; must be manually recreated
Custom Fields	Custom ticket/asset fields	AR System field definitions	Field type mapping required; dropdown values must be pre-created
Attachments	File attachments on tickets/assets	Attachments on HPD/AST forms	Must be downloaded individually via API and re-uploaded; largest time cost

---

Common migration pitfalls

1. Status mapping is never 1:1. Both platforms use different default statuses and allow custom statuses. Build a status mapping table validated with stakeholders before migrating a single record. Unmapped statuses silently default to incorrect values.

2. Attachments dominate the timeline. File attachments must be downloaded individually via API from the source system and re-uploaded to the target. For tenants with high attachment volume (common in IT operations environments with screenshot-heavy incident workflows), this is typically the slowest migration component — often 40–60% of total elapsed time.

3. Timestamps and audit trail integrity. Migrated records do not preserve original created/updated timestamps in the target system's native audit log. The migration timestamp becomes the record timestamp. If compliance or SLA reporting requires historical timestamp accuracy, export and archive the source audit data separately before decommissioning.

4. SLA policies require full recreation. SLA definitions, business hour calendars, and escalation rules do not transfer between platforms. These must be manually configured in the target system and validated against historical SLA performance data before go-live.

5. Custom field type mismatches. Both platforms support custom fields, but field types, validation rules, and character limits differ. A free-text field in Freshservice may need to become a controlled dropdown in Helix to maintain data integrity. Map every custom field explicitly before writing migration scripts.

6. User role model differences. Freshservice's agent/requester model is flatter than BMC Helix's CTM:People role hierarchy. Migrating users without auditing role assignments first produces permission misconfigurations that can grant excessive access or lock out valid users.

---

How long does a Freshservice ↔ BMC Helix migration take?

These estimates are based on migration patterns for mid-market to enterprise ITSM deployments:

Migration direction	Typical timeline	Factors that extend it
Helix → Freshservice	4–10 weeks	AR System custom form count, CMDB complexity, SOAP integration rebuild count
Freshservice → Helix	8–16 weeks	AR System workflow design, CMDB setup, marketplace integration rebuild, ticket volume >1M records
Either direction with heavy CMDB	Add 4–8 weeks	CI class design, Discovery configuration, relationship validation
Either direction with complex approvals	Add 2–4 weeks	Multi-stage approval chain redesign

The critical variable is workflow re-architecture, not data volume. Moving 500,000 ticket records between platforms is a scripting and scheduling problem. Rebuilding 40 AR System custom forms as Freshservice workflow automator rules — or vice versa — requires process analysis, stakeholder interviews, and iterative testing. That work expands timelines regardless of how clean the data is.

A 300-agent financial services migration from Helix to Freshservice with 2.1M historical ticket records, 380GB of attachments, and 34 custom AR System forms took 11 weeks end-to-end. The AR form analysis and rebuild consumed 6 of those 11 weeks. The data migration itself — scripted, incremental, run over weekends — took 9 days of elapsed time.

---

Choosing the right platform

Freshservice and BMC Helix ITSM are both production-grade ITSM platforms, but they are not interchangeable. The decision framework is straightforward once you map your requirements against the constraints:

Choose Freshservice if: Cloud-only deployment is acceptable, your agent count is below 500, you need operational ITSM quickly, and asset tracking (not full CMDB) is sufficient.

Choose BMC Helix ITSM if: You need on-premises or hybrid deployment, FedRAMP compliance, enterprise-scale CMDB with discovery, or AR System workflow depth that exceeds what a visual automator can deliver.

The migration work is real regardless of direction. Status mappings, workflow re-architecture, API rate limit planning, attachment extraction, custom field translation, and role model reconciliation all require explicit design. The platforms' workflow engines are fundamentally different paradigms — not just different UIs over the same logic.

---

All pricing figures reflect publicly available sources and third-party benchmark data as of Q2 2025. API behavior reflects platform documentation current as of the same period. Enterprise contract pricing varies by negotiation; figures represent market ranges, not guarantees.