Migrate from BMC Helix ITSM to Jira Service Management 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
Jira Service Management
MIGRATION OVERVIEW

Why teams migrate from BMC Helix ITSM to Jira Service Management

Migrating from BMC Helix ITSM to Jira Service Management has no native migration path from either vendor, requiring custom API scripting or a managed migration service for all data transfer. The fundamental challenge is a deep data model mismatch: BMC Helix stores incidents, problems, and changes across dedicated AR System forms with relational links and uses a hierarchical class-based CMDB, while JSM collapses all work into Jira Issues differentiated by Issue Type and Request Type and uses flat object schemas with AQL-based references in JSM Assets. Significant custom transformation work is required to rebuild CMDB relationships, map enumerated field values, convert BMC's multi-level CI hierarchies into JSM's flat schema constraints (120 attributes per object type, 2 unique constraints), and reconstruct SLA policies, approval workflows, and support group assignment rules from scratch.
KEY CHALLENGES

What makes this migration complex

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

Most Critical

CMDB Relationship Model Conversion

BMC Helix CMDB uses hierarchical class-based CI relationships with typed associations like BMC_HostedSystemComponents, which must be entirely rebuilt as flat AQL-based reference attributes in JSM Assets object schemas.

Three-Layer Target Model Mapping

BMC Helix tickets must be mapped simultaneously into three distinct JSM layers—Issues, Request Types, and Assets schemas—making a naive table-to-table copy impossible.

Work Log Structure Loss

BMC Work Logs contain structured fields including Work Log Type, Submitter, and Time Spent, but JSM comments are plain text with only an internal/external flag, requiring time tracking data to be mapped to a separate JSM field.

JSM Assets Attribute Limits

JSM Assets enforces a hard limit of 120 attributes per object type and 2 unique constraints per object type, requiring BMC CI classes that exceed these limits to be restructured or split before import.

Enum and Status Value Transformation

BMC uses numeric status codes and numbered selection field values across all ITSM modules that must be individually mapped to JSM's configurable workflow statuses and select lists through a comprehensive value mapping table.

Knowledge Base Format Conversion

BMC Knowledge articles use their own article lifecycle and HTML format, which must be transformed to Confluence storage format since JSM does not host knowledge articles natively.

COMPLETE COVERAGE

Intelligent Human-Verified Data Mapping

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

BMC Helix ITSM
Jira Service Management
Incident
Service Requests (Issues)
Change Request
Service Requests (Issues)
Problem Investigation
Service Requests (Issues)
Known Error
Service Requests (Issues)
Service Request
Service Requests (Issues)
Configuration Item (CI)
Assets (Insight Objects)
Asset
Assets (Insight Objects)
People (Person)
Customers (Service Desk Users)
Company
Organizations
Knowledge Article
Knowledge Base Articles
Work Info (Activity Log)
Service Request Comments
Task
Service Requests (Issues)
Attachment
Attachments
Release Request
Versions (Releases)
Category (Operational/Product)
Request Types
Support Group
Not Available
SLA Definition
Not Available

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 Jira Service Management and built proven solutions for each one.

Migration Challenge ClonePartner Status
High Complexity —
Solved
Configuration Items (CMDB)
BMC's hierarchical class-based CMDB with typed relationships must be entirely rebuilt as flat JSM Assets object schemas with AQL-based references, and multi-level CI relationship hierarchies cannot be imported directly.
Solved
Work Logs
BMC's structured Work Log entries with typed fields, submitter data, and time spent cannot be migrated 1-to-1 into JSM's plain-text comments, resulting in loss of structured time tracking and log categorization data.
Solved
SLA Definitions and History
SLA logic must be completely rebuilt in JSM as new policies, and historical SLA compliance data cannot be migrated at all—it must be archived from BMC before decommission.
Solved
Custom Engineering —
Handled
Incidents
Incidents map to JSM Issue types conceptually, but status values require enum mapping from BMC's numeric codes to JSM's configurable workflow statuses, and associated work logs lose their structured metadata.
Handled
Change Requests
BMC Change fields like Risk Level, Change Type, and multi-phase approval workflows must be mapped to JSM custom fields and workflow transitions, requiring significant workflow redesign.
Handled
Service Requests
BMC Service Request Definitions do not map 1-to-1 to JSM Request Types, and the distinction between JSM work types and request types requires a separate manual mapping effort for portal taxonomy.
Handled
Knowledge Articles
Articles must be converted from BMC's knowledge format to Confluence storage format with HTML transformation, and BMC's article lifecycle states have no direct equivalent in Confluence.
Handled
Contacts / People
BMC People records include Support Group assignments and functional roles stored separately, requiring a complete identity map to be built before any ticket data can be loaded into JSM.
Handled
Support Groups
BMC Support Groups with their assignment rules do not map cleanly to JSM Groups or Organizations, requiring group-level routing logic to be rebuilt as JSM automation rules.
Handled
Clean Transfer
Attachments
Attachments can be migrated by downloading binary fields via the AR System API and re-uploading to JSM, though this is time-intensive for large volumes and subject to JSM's 250 MB per-file limit.
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 Jira Service Management 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 Jira Service Management 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 Jira Service Management, 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 Helix to Jira Service Management Migration: The Complete Guide

BMC Helix to JSM migration takes 4 to 12 weeks. The biggest risk is broken CMDB relationships. Plan for AQL-based CI mapping, JSM Assets rate limits of 1,000 req/min, and no native migration tool.

25 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 Jira Service Management 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 Jira Service Management 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 Jira Service Management
  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 Jira Service Management 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 Jira Service Management. Can't find what you're looking for? Talk to our team.

How long does a BMC Helix to Jira Service Management migration take?
A typical enterprise migration takes 4 to 12 weeks, including discovery, schema setup, script development, test migration, production migration, and post-migration QA. Small ticket-only moves with no CMDB can be done in 2 to 4 weeks. Add 2 to 4 weeks for environments with heavy CMDB customization or compliance requirements.
Can I migrate BMC Helix CMDB data to JSM Assets without losing relationships?
Yes, but each BMC CI class must be mapped to a JSM Assets Object Type, and every CMDB relationship must be rebuilt using AQL-based reference attributes. Multi-value references require separate import rows with merge-and-append settings. Load parent assets before child assets to avoid orphaned records.
Is there a native migration tool for BMC Helix to Jira Service Management?
No. Neither BMC nor Atlassian provides a native migration tool for this path. All migrations require API-based extraction from BMC and API or CSV-based loading into JSM. Third-party tools like Precision Bridge offer partial automation but still require mapping configuration and typically lack deep CMDB support.
What is the biggest risk in a BMC Helix to JSM migration?
Broken CMDB relationships. BMC Helix stores CI relationships in a deeply typed hierarchical model. If CIs load into JSM Assets without correctly mapped AQL references, CI-to-Incident links and CI-to-CI dependencies break silently. Fixing this after go-live is expensive and disruptive.
Is CSV export enough for a BMC Helix to JSM migration?
Usually not for production. BMC mid-tier report exports default to 2,000 records, no relational data is preserved, and Jira's CSV import path can make JSM comments public. CSV works for small closed-ticket archives. Use the API for anything larger or with mixed public and internal history.
How long does the BMC Helix ITSM to Jira Service Management 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 Jira Service Management?
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→Jira Service Management migration.

Contact our team

Ready to start your
Jira Service Management 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.