BMC Remedy to BMC Helix Migration: Complete Enterprise Guide
👥 Who this guide is for: IT managers, system administrators, enterprise architects, and decision-makers planning to migrate from on-premises BMC Remedy to BMC Helix (cloud/SaaS).
📌 In this guide: Why migrate? | Key differences (Remedy vs Helix) | Migration planning | Data migration | Customizations | 8-12 week timeline | Common pitfalls | How we help
BMC Remedy has been a trusted ITSM platform for decades, but many organizations are now moving to BMC Helix – the cloud-native, AI-powered version. This guide walks you through everything you need to know about the migration.
Why Migrate from BMC Remedy to BMC Helix?
Organizations typically migrate to BMC Helix to:
- Reduce infrastructure costs – No more servers, storage, or backup hardware
- Eliminate manual upgrades – BMC handles all updates automatically
- Leverage AI/ML capabilities – Predictive analytics and automated root cause analysis
- Improve scalability – Add users and modules without provisioning new servers
- Enable remote access – Users can access from anywhere, no VPN required
Key Differences: BMC Remedy (On-Prem) vs BMC Helix (Cloud)
| Aspect | BMC Remedy (On-Prem) | BMC Helix (Cloud) |
|---|---|---|
| Deployment | On your servers | BMC-managed cloud (SaaS) |
| Upgrades | Manual (your team handles) | Automatic (BMC handles) |
| Hardware cost | Servers, storage, backup, DR | No hardware |
| Maintenance | Your team or vendor | BMC managed |
| AI/ML capabilities | Limited | Built-in (Helix AIOps, Predictive Insights) |
| Access | VPN or internal network | Internet (anywhere, any device) |
| Pricing model | Perpetual license + annual maintenance | Subscription (monthly/yearly per user) |
| Disaster recovery | You build and maintain | Built-in, BMC managed |
Migration Process: Step by Step (8-12 Weeks)
Typical 8-12 Week Migration Timeline
Phase 1: Assessment & Planning (Weeks 1-2)
- Inventory current Remedy configuration (customizations, workflows, integrations)
- Identify which modules are used (ITSM, ITOM, Discovery, SRM, etc.)
- Define migration scope, success criteria, and rollout strategy
- Identify stakeholders and create communication plan
Phase 2: Data Analysis & Cleanup (Weeks 2-3)
- Analyze data quality in Remedy CMDB and ticket tables
- Remove duplicate, stale, or inactive records
- Archive historical data beyond retention period
- Map data fields from Remedy to Helix schema
Phase 3: Environment Setup (Weeks 3-4)
- Provision BMC Helix sandbox/development environment
- Configure out-of-the-box modules and foundational data
- Set up integrations with external systems (AD, SSO, etc.)
- Plan custom application migration strategy
Phase 4: Migration Execution – Sandbox (Weeks 4-6)
- Migrate configuration and sample data to sandbox environment
- Recreate custom workflows, active links, and escalations in Helix
- Rebuild custom integrations using Helix REST APIs
- User acceptance testing (UAT) with key users
Phase 5: Migration Execution – Production (Weeks 6-8)
- Final data migration from Remedy to Helix (full dataset)
- Configure all integrations with external systems
- Cutover during planned maintenance window (typically weekend)
- Validate all data and functionality post-migration
Phase 6: Go-Live & Optimization (Weeks 8-12)
- User training and documentation
- Monitor system performance and fix issues
- Decommission old Remedy environment (after validation)
- Continuous optimization and adoption support
Data Migration – What You Need to Know
What data CAN be migrated:
- CI (Configuration Item) data from CMDB
- Incident, problem, change, and service request tickets (with full history)
- User accounts, roles, permissions, and group structures
- Service level agreements (SLAs) and targets
- Knowledge articles and documentation
- Custom fields and forms (with mapping considerations)
- Attachments and audit history
What typically needs to be rebuilt (not migrated):
- Complex custom workflows and active links
- Custom integrations with legacy systems (APIs changed in Helix)
- Custom reports and dashboards (Helix has different reporting engine)
- Homegrown automation scripts and escalations
- Custom UI modifications and branding
⚠️ Critical advice: Data migration is the most complex part of the project. Plan for data cleansing 2-3 weeks before migration. Old, duplicate, or inactive data should be archived, not migrated. "Garbage in, garbage out" applies heavily here.
Handling Customizations – Remedy to Helix Mapping
Most Remedy instances have customizations. Here is how they translate to BMC Helix:
| Remedy Customization | Helix Equivalent | Estimated Effort |
|---|---|---|
| AR System forms | Innovation Studio objects | Moderate |
| Active Links | Workflows (Flow Designer) | Moderate |
| Filters | Rules / Business logic | Moderate |
| Escalations | Scheduled workflows | Low to Moderate |
| Custom integrations (SOAP/REST) | REST APIs (similar, but different) | Low |
| Homegrown UI modifications | Designer / Portal customization | Moderate to High |
| Custom reports | Helix Analytics / Power BI | Moderate (rebuild) |
Common Pitfalls to Avoid
- Underestimating data cleansing time – Old, duplicate data will cause issues in Helix. Clean before migrating. Allocate 2-3 weeks for this.
- Assuming all customizations will work – Some need to be rebuilt. Audit before planning timeline. Have a rebuild budget.
- Not testing integrations early – Helix APIs work differently. Test integrations in sandbox during Week 3-4, not Week 7.
- Skipping user training – Helix UI is significantly different. Plan for 1-2 days of end-user training before go-live.
- Cutting over too quickly – Run Remedy and Helix in parallel for 1-2 weeks after cutover to validate. Then decommission Remedy.
- Forgetting about reporting – Remedy reports do not migrate. Rebuild critical reports in Helix Analytics or connect Power BI.
- No rollback plan – Always have a rollback plan. Know how to revert to Remedy if critical issues are found.
Migration Strategies – Which One Is Right for You?
Recommendation for most organizations: Start with a pilot migration of a non-critical module (e.g., Service Request Management) to validate the process. Then migrate the remaining modules in phases.
Real Example: Hyderabad Manufacturing Company
Client: Hyderabad-based Manufacturing (500+ users, 10+ years on Remedy)
Challenge: BMC Remedy on-prem version 9.1 – end of support approaching, high maintenance cost ($200k+/year for hardware + support), no AI capabilities, manual upgrades taking 2-3 months each.
Solution: Migration to BMC Helix ITSM + Helix Operations Management (BHOM).
Timeline: 10 weeks (assessment: 2 weeks, migration: 6 weeks, UAT and parallel run: 2 weeks)
Customizations migrated: 45 custom forms, 120 active links, 30 escalations, 8 integrations
Results (6 months after migration): 40% reduction in IT operations cost, automatic upgrades (zero downtime), proactive alerting reduced MTTR by 60%, user satisfaction increased by 35%.
How Anvigya Digital Services Can Help
What we provide:
- Assessment – Full inventory of your current Remedy environment (forms, workflows, integrations, customizations, data volume)
- Migration plan – Detailed timeline, effort estimates, and resource requirements
- Data migration – Extraction, cleansing, mapping, validation, and load to Helix
- Customization rebuild – Rebuilding active links, escalations, filters, and integrations in Helix
- Integration setup – Connecting Helix with Active Directory, SSO, SAP, monitoring tools, etc.
- User training – End-user and admin training (online or on-site)
- Post-migration support – Optional AMC for ongoing maintenance and support
What we do NOT do:
- We do not sell BMC licenses. You purchase BMC Helix licenses directly from BMC or their authorized partners.
- We are not a BMC partner or reseller. We are an independent implementation and consulting services provider.
Frequently Asked Questions
❓ How long does a typical migration take?
8-12 weeks for mid-size organizations (5,000-50,000 tickets/year). Larger or highly customized environments with 10+ years of history may take 16-20 weeks.
❓ What is the cost?
Depends on complexity, number of customizations, data volume, and integration requirements. Contact us for a customized assessment and fixed-price quote.
❓ Will there be downtime during migration?
Minimal. Users can access Remedy during migration preparation and testing. Only the final cutover weekend has planned downtime (typically 24-48 hours).
❓ Do we need to buy new BMC licenses?
Yes – BMC Helix is a subscription product. You purchase licenses directly from BMC. We can help you understand licensing requirements based on your user count and modules, but we do not sell licenses.
❓ Can we keep some Remedy modules and migrate others later?
Yes. Phased migration is common. For example, migrate ITSM and SRM first, then ITOM and Discovery, then CMDB. Most organizations take 6-12 months for full migration.
❓ What if we want to go back to Remedy?
Rolling back is complex and not recommended. We recommend running Remedy and Helix in parallel for 1-2 weeks after cutover to validate. After that, decommission Remedy. The cost of maintaining both is high.
❓ Do you provide post-migration support?
Yes. We offer AMC (Annual Maintenance Contract) for ongoing support, bug fixes, minor enhancements, and user support. Optional – can be started, paused, or cancelled with 30 days' notice.
❓ What about BHOM, TSSA, BCM modules?
We also provide migration support for BHOM (Operations Management), TSSA (Server Automation), and BCM (Business Critical Monitoring). Refer to our BMC Helix Training Guide for more details.
⚠️ IMPORTANT DISCLAIMER
BMC, Remedy, BMC Helix, and related trademarks are property of BMC Software, Inc. Anvigya Digital Services is an independent IT services provider and is not affiliated with, endorsed by, or partnered with BMC Software, Inc. This guide is for informational purposes based on industry experience. Migration details, timelines, and requirements may vary. Please refer to BMC's official documentation for the most current information.
We do not sell BMC licenses. Licenses must be purchased directly from BMC Software, Inc. or their authorized partners.
Planning Your BMC Remedy to Helix Migration?
We provide independent migration consulting, assessment, and execution support. No license upsell – just expertise. Fixed-price projects available.
Discuss Your Migration