Migrate from BMC Helix ITSM to ServiceNow with precision & ease

A seamless, customizable migration solution for moving your BMC Helix ITSM data with perfect fidelity and minimal disruption.

Book free consultation
BMC Helix ITSM
ServiceNow
MIGRATION OVERVIEW

Why teams migrate from BMC Helix ITSM to ServiceNow

Migrating from BMC Helix ITSM to ServiceNow is a legacy-to-cloud architectural shift with no native migration path or out-of-the-box plugin to connect the two platforms. BMC Remedy's AR System uses a form-driven architecture with tightly coupled data, logic, and UI—stored in proprietary T-tables, H-tables, and B-tables—while ServiceNow operates on a normalized, table-driven relational model aligned to the Common Service Data Model (CSDM). Every data structure requires explicit field-level mapping (including translating numeric Remedy Field IDs to human-readable ServiceNow columns), a custom ETL pipeline for on-prem extraction, and a full rebuild of workflow objects such as Active Links, Filters, and Escalations into ServiceNow's Business Rules, Flow Designer, and UI Policies.
KEY CHALLENGES

What makes this migration complex

These are the architectural mismatches and technical hurdles specific to a BMC Helix ITSM to ServiceNow migration.

Most Critical

No Native Migration Path

ServiceNow provides no out-of-the-box plugin or connector to extract data from BMC Remedy, requiring a fully custom ETL pipeline built with tools like Talend, Informatica, or custom Python scripts.

Incompatible Data Models

Remedy's form-based AR System architecture with numeric Field IDs, proprietary T/H/B-table schemas, and enumerated integer fields must be translated to ServiceNow's normalized relational tables with human-readable column names, choice fields, and glide_date_time types.

CMDB Class Explosion

BMC's Common Data Model uses approximately 7 base CI classes like BMC_ComputerSystem, which must be redistributed across 50–60+ granular ServiceNow CSDM classes such as cmdb_ci_win_server and cmdb_ci_linux_server based on CI attributes.

Workflow Logic Rebuild

Remedy's Active Links, Filters, and Escalations are tightly coupled to forms and cannot transfer automatically, requiring each workflow chain to be analyzed and rebuilt using ServiceNow's Business Rules, Flow Designer, and UI Policies.

Work Log History Preservation

Remedy stores work logs in separate forms (HPD:WorkLog, CHG:WorkLog) and migrating them to ServiceNow's sys_journal_field without using autoSysFields(false) overwrites original authors and timestamps, destroying the audit trail.

On-Prem Extraction Complexity

Extraction capabilities vary significantly across Remedy versions—7.x offers no REST API and requires direct SQL, while 9.x and Helix provide REST APIs with pagination limits—making data extraction a standalone engineering workstream.

COMPLETE COVERAGE

Intelligent Human-Verified Data Mapping

Our migration engineer precisely maps every data point from BMC Helix ITSM to ServiceNow, ensuring perfect continuity for your customer support operations.

BMC Helix ITSM
ServiceNow
Incident
Incidents
Change Request
Change Requests
Problem Investigation
Problems
Known Error
Problems
Service Request
Requested Items
Configuration Item (CI)
Configuration Items (CIs)
CI Relationship
CI Relationships
Asset
Asset Records
People (Person)
Users
Support Group
Groups
Support Group Association
Group Members
Company
Companies
Site
Locations
Knowledge Article
Knowledge Articles
Work Info (Activity Log)
Comments/Work Notes
SLA Definition
SLA Definitions
Attachment
Attachments
Service (Business Service CI)
Service Offerings (Business Services)
Category (Operational/Product)
Catalog Categories

Looking for more entity mappings?

Contact our team
MIGRATION RISK ASSESSMENT

Every migration risk, already solved

Migration between platforms is full of edge cases. Our engineers have identified every risk from BMC Helix ITSM to ServiceNow and built proven solutions for each one.

Migration Challenge ClonePartner Status
High Complexity —
Solved
Work Logs / Journal History
Without autoSysFields(false) in transform scripts, all work log entries are stamped with the migration user and current timestamp, permanently destroying the original chronological audit trail.
Solved
CMDB Configuration Items
BMC's ~7 base CDM classes must be decomposed into 50-60+ ServiceNow CSDM classes with identification rules pre-defined; without this, bulk imports create massive duplicate CI records.
Solved
Custom Fields
Remedy fields identified by numeric IDs with data types like diary fields, selection enums, and >4000-character strings require individual type conversion rules, and missing interface form fields will cause silent data loss.
Solved
Custom Engineering —
Handled
Incidents
HPD:HelpDesk maps to the incident table, but status/status_reason combinations require explicit enum mapping to ServiceNow's state, close_code, and on_hold_reason fields to avoid misclassification.
Handled
Problems
PBM:Problem Investigation maps to the problem table, but integration interface forms (PBM:ProblemInterface_Create) must also be inventoried to capture all fields used during record creation.
Handled
Change Requests
CHG:Infrastructure Change maps to change_request, but Remedy's change types and approval workflow chains must be carefully re-mapped to ServiceNow's standard, normal, and emergency change models.
Handled
Service Requests / Catalog Items
SRM:Request and TMS:Task map to sc_request, sc_req_item, and sc_task, but the service catalog structure and fulfillment workflows must be rebuilt in ServiceNow's Service Catalog framework.
Handled
Assets
AST:Asset maps to alm_asset, but Remedy's asset-CI relationship model may not align with ServiceNow's asset-to-CI linking conventions, requiring relationship reconciliation.
Handled
Notifications / Email Rules
Remedy's NTE:Notification has no direct ServiceNow equivalent and all notification logic must be manually rebuilt as ServiceNow Notification records with appropriate triggers and conditions.
Handled
Clean Transfer
Knowledge Articles
KM:Knowledge Article maps to kb_knowledge with relatively straightforward content migration, though embedded attachments and article categorization may require additional handling.
Clean
3 high-complexity solved
6 custom-engineered
1 clean transfers
CUSTOM MIGRATION

Fully customizable engineer-led migration

Tailor your migration from BMC Helix ITSM to ServiceNow exactly to your needs with our flexible customization options. Our experts will configure the perfect migration plan for your business.

Migration Filters

Ticket Status

Filter by open, resolved, closed, or pending states

Assignment Group

Migrate tickets assigned to specific support teams or queues

Priority Level

Select records based on urgency, impact, or priority levels

Time Range

Migrate tickets created or updated within a specific period

Data Types

Incidents & Requests

Active and closed tickets including history, comments, and attachments

Problems & Changes

Root cause analysis records and change management workflows

Assets & CMDB

Hardware, software, and configuration items with relationships

Knowledge Base

Help articles, FAQs, and internal documentation with categorization

ZERO DOWNTIME

Your timeline. Our engineers.

A dedicated engineer runs your migration, planned around your schedule and your data.

No babysitting a wizard. Avoid debugging errors yourself.

Looking for a more detailed migration timeline?

Contact our team

Speed

The migration timeline depends on both our turnaround time and yours.

We can complete a migration in under a day when the accounts are connected and the sample migration is approved promptly.

Background Sync

We also support migrating the newest records first, so you can go live faster while the rest of the data is synced in the background.

Data Volume Impact

Larger data volumes may require longer migration windows.

Continuous Operation

Weekend migrations minimize disruption to your customer service operations.

MIGRATION TIMELINE

Your BMC Helix ITSM to ServiceNow migration, step by step

See how long your migration will take from start to finish. Drag the slider to estimate based on your data volume.

How many records are you migrating?

<10K 50K 100K 250K 500K 1M 2M 5M 10M+
Checklist ~3 days
Sample 1 day
Review ~2 days
Full 2 days
Delta 1 day
Your team ClonePartner

Estimated total

~9 business days

1

Migration Checklist

1 day · ClonePartner ~2 days · Your team

We prepare the optimal data mapping as a shareable spreadsheet. Your team reviews, approves, and adds any customizations.

2

Sample Migration

1 day · ClonePartner

We run a test migration with a representative sample of your data to verify mapping accuracy and identify any potential issues before the full run.

3

Review & Approve

~2 days · Your team

Your team reviews the sample migration results, confirms data accuracy and mapping, and gives the go-ahead for the full migration.

4

Full Migration

2 days · ClonePartner

We execute the complete migration of all your data to your new ServiceNow, with real-time progress tracking and comprehensive logging.

5

Delta Migration

1 day · ClonePartner

We capture and transfer any new data that was added or updated during the main migration to ensure no data is lost. This final sync keeps everything current.

Timeline is an estimate. Actual duration depends on API rate limits, data complexity, and your team's availability.

Get an exact timeline

Complete Technical Guide

BMC Remedy to ServiceNow Migration: The CTO's Technical Guide

BMC Remedy to ServiceNow migration requires mapping AR System forms to ServiceNow tables, rebuilding Active Links/Filters in Flow Designer, and translating BMC's CDM-based CMDB to ServiceNow's CSDM — none of it automatic.

29 min read

Read the guide

Pros and cons of different migration options

Choosing the right approach is key because migrating from BMC Helix ITSM to ServiceNow isn't just about moving data – it's about protecting customer relationships.

Feature / Criteria ClonePartner Automated Tools CSV Import In-house migration
Custom Scripting for complex data ✓ Engineers build & maintain ✗ No ⚠ Manual ✓ Yes – but costly
Sandbox & Pilot Migrations ✓ Full sandbox + pilot plans ⚠ Limited ✗ No ⚠ Often Informal
Manual validation & reconciliation ✓ Automated + manual QA ✗ No ✓ Yes (Manual) ✓ Heavy manual effort
Backup & rollback plan ✓ Robust procedures ✗ No ✗ No ⚠ Often incomplete
Handles automation and integrations ✓ Full support ⚠ Partial ✗ No ⚠ Possible but fragmented
Post-migration engineer support ✓ Dedicated engineers ✗ No ✗ No ⚠ Limited SLA
Adaptable to API changes ✓ Proactive adaptation ✗ No ⚠ Manual fixes ⚠ Slower response
Turnaround / SLA predictability ✓ Predictable SLAs ⚠ Fast but brittle ⚠ Slow and manual ⚠ Often slower
Data Security & Compliance ✓ High – enterprise grade ⚠ Medium (depends) ⚠ Low (manual) ⚠ Hidden gaps common
Pricing predictability ✓ Transparent & fixed ⚠ Low (per-job) ⚠ Low (manual hours) ⚠ High/variable OPEX
End-to-end project management ✓ Full E2E delivery & PM ✗ No ✗ No ⚠ Often partial
Business impact & opportunity cost ✓ No diversion of staff ✗ No ✗ No ⚠ Diverts engineering

What does an Engineer-led migration mean anyway?

Speed & Accuracy: Our Blended Method

We blend automation (smart scripts, bulk APIs) with human expertise for speed without risk. Our engineers manually check every mapping, validation, and exception.

You get:

  1. Speed of automation for bulk record migration
  2. Precision of engineers verifying integrity and business logic
  3. Pilot migrations and sandbox testing to catch issues early
  4. Real-time validation reports and rollback readiness
Result: 50x faster migrations than manual imports — with near-zero error rates.

Handling the Tricky Tech and API Details

The BMC Helix ITSM and ServiceNow APIs each behave differently, which is where our engineers shine. We build custom logic to handle the data quirks where generic tools typically break.

We handcraft API logic for:

  1. Field mapping and transformation
  2. Pagination, rate-limit handling, and throttling
  3. Preserving conversation threads, attachments, and internal notes
  4. Syncing custom fields, SLAs, and macros without breaking structure
Our scripts: Natively retry failed calls, re-queue large attachments, and ensure data parity.

No Guesswork

We don't just promise smooth migrations—we measure and prove them. Every client receives a Migration Validation Report with all metrics.

Typical results across projects:

  1. 100% record-count parity between your BMC Helix ITSM data and ServiceNow
  2. Zero downtime during staged cutovers
  3. 99.9% attachment integrity (verified via checksum)
  4. Full automation and preservation of all business rules
Our standard: Includes full SLA preservation and 48 hours of engineer-assigned support post go-live.

We Adapt to Your Setup (Not the Other Way Around)

No two teams configure BMC Helix ITSM or ServiceNow exactly the same way—with unique automations and data. We customize every migration script to fit your exact workflow, tags, and triggers.

Our engineers adapt for:

  1. Custom fields, ticket forms, and workflows
  2. Multi-brand or multi-language setups
  3. Historical imports and partial (date-based) migrations
  4. Integration re-mapping for CRMs, chat, or feedback tools
The promise: If your data doesn't fit a standard template, we build one just for you.

Enterprise-Grade Security & Compliance

Your customer data is precious. Our migration process maintains the highest standards of security and regulatory compliance.

SOC 2 Type II

Independently audited compliance with rigorous security standards

ISO 27001

Certified information security management system

GDPR

Full compliance with EU data protection regulations

HIPAA

Certified for handling protected health information

AES-256 Encryption

Bank-grade encryption for all stored credentials

Latest TLS

Secure transfer protocol for all data in transit

Role-Based Access

We follow role-based access control for every migration project

Scheduled Deletion

Automatic data purging after migration completion

FAQ

Frequently Asked Questions

Everything you need to know about migrating from BMC Helix ITSM to ServiceNow. Can't find what you're looking for? Talk to our team.

Can you automatically migrate BMC Remedy Active Links and Filters to ServiceNow?
No. Remedy's Active Links, Filters, and Escalations have no automated migration path to ServiceNow. Each must be inventoried, classified as keep/redesign/retire, and rebuilt using ServiceNow's Client Scripts, Business Rules, Flow Designer, or UI Policies. Some tools like Precision Bridge can migrate service request definitions, but core workflow logic requires manual rebuild.
How long does a BMC Remedy to ServiceNow migration take?
For a midsized enterprise with moderate customizations and under 2M records, plan for 8–16 weeks end-to-end. Highly customized environments with 5M+ records and complex CMDB structures can take 20–30 weeks. The biggest timeline drivers are custom workflow rebuild, CMDB class mapping, and Foundation data cleanup.
How do you map BMC Remedy CMDB to ServiceNow CMDB?
BMC's CMDB uses the Common Data Model with as few as 7 base CI classes. ServiceNow uses the CSDM-aligned model with 50–60+ granular classes. You must build conditional routing logic that reads Remedy's Category, Type, and Item attributes and routes each CI to the correct ServiceNow class, mapping BMC_Relationship records to ServiceNow's cmdb_rel_ci table.
Do we need to migrate all historical Remedy data to ServiceNow?
No. Best practice is to migrate open/active tickets in full, closed tickets from the last 12–24 months for operational reference, and archive older records to a data warehouse or cold storage. This reduces migration time, keeps ServiceNow performant, and avoids storing data no one actively accesses.
What happens to custom Remedy forms and fields during migration?
Custom forms do not transfer to ServiceNow. Each custom field must be mapped to a ServiceNow field — either an existing OOB field or a new custom field. Remedy's numeric Field IDs need translation to ServiceNow's named column format, and data types often require conversion. Some custom forms map to existing ServiceNow tables; others need new custom tables extending from task.
How long does the BMC Helix ITSM to ServiceNow migration take?
Most migrations complete within 1–5 business days, depending on data volume and complexity. We provide a detailed timeline after the initial assessment and can often complete small migrations in under 24 hours.
Will my team lose access to BMC Helix ITSM during the migration?
No. Your source system remains fully operational throughout the entire migration. We run the migration in the background with zero downtime to your current operations.
Will there be downtime when migrating from BMC Helix ITSM to ServiceNow?
No. Our migration process is designed for zero downtime. We use a staged approach with background sync and a fast cutover, ensuring no disruption to your live business operations.
How do I validate that everything migrated correctly?
Every client receives a Migration Validation Report with comprehensive metrics including record-count parity, attachment integrity verification via checksum, and full audit logs. We also offer unlimited sample migrations so you can verify before committing.
Do I need professional help for this migration?
While simple migrations can sometimes be handled in-house, professional help ensures zero data loss, proper field mapping, and preservation of relationships between records. Our engineer-led approach catches edge cases that automated tools miss.
Does ClonePartner provide guidance before committing?
Yes. We provide a free consultation and assessment. We'll review your data structure, discuss your requirements, and provide a detailed migration plan and fixed-price quote before you commit to anything.

Still have questions?

Book a free 30-minute consultation with our migration engineers. We'll walk you through the exact approach for your BMC Helix ITSM→ServiceNow migration.

Contact our team

Ready to start your
ServiceNow Migration?

Join hundreds of businesses who have successfully migrated with ClonePartner. Let's discuss your migration needs and build a plan that works for you.

Book free consultation

Attention to Detail

We meticulously handle every aspect of your migration, ensuring no data is lost during transfer and mapping every field correctly between platforms.

Custom Solutions

Every business is unique. We tailor your migration strategy to match your specific requirements, workflows, and data structures.

Security & Compliance

Your customer data is handled with enterprise-grade security protocols, ensuring compliance with GDPR, HIPAA, and industry standards.