BMC Helix ITSM to Jira Service Management Migration

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.

Blocks all downstream imports if mapped wrong

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.

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.

High complexity

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

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

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

Data Types

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

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.

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.

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.

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.

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.

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 support
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:

Speed of automation for bulk record migration
Precision of engineers verifying integrity and business logic
Pilot migrations and sandbox testing to catch issues early
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:

Field mapping and transformation
Pagination, rate-limit handling, and throttling
Preserving incident history, worknotes, and CI relationships
Syncing custom fields, SLAs, and workflows 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:

100% record-count parity between your BMC Helix ITSM data and Jira Service Management
Zero downtime during staged cutovers
99.9% attachment integrity (verified via checksum)
Full automation and preservation of all business rules

Our standard: Includes full SLA and CMDB-relationship preservation and 30 days 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 workflows and data. We customize every migration script to fit your exact workflow, SLAs, and CMDB relationships.

Our engineers adapt for:

Custom fields, SLAs, and workflows
Multi-brand or multi-language setups
Historical imports and partial (date-based) migrations
Integration re-mapping for CMDB, monitoring, or chat tools

The promise: If your data doesn't fit a standard template, we build one just for you.

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.

Before you start 4 Data & mapping 6 Timeline & downtime 2 Security & access 1 Pricing 1 After go-live 4

Still have questions?

Book a free 30-minute consultation with our team.

Contact our team

Before you start

4 questions

Do I need professional help for this migration?

Yes. Professional help ensures 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.

Do you use an off-the-shelf tool to migrate from BMC Helix ITSM to Jira Service Management, or is this built for our data?

It is built for your data. Each migration is a set of custom scripts written for your data model, not a generic import tool. That is also why we start with a sample migration: you see your own records in Jira Service Management before the full migration is committed.

Can we see a sample of our BMC Helix ITSM data migrated to Jira Service Management before the full migration runs?

Yes. We run a sample migration on your own data first, so you can review how your records look in Jira Service Management before the full migration goes ahead. We run validation scripts to confirm the record counts match your source, and you check the sample against your source records; if a field is missing or mapped wrong, or anything else needs adjusting, we fix it in the migration scripts and re-run the sample as many times as you need. The full migration only runs after you've approved the sample. On projects delivered in phases, each phase gets its own sample migration for you to approve.

Data & mapping

6 questions

Will the original assignees, message authors and created dates be preserved?

Yes. Created-time metadata is carried across, and so are assignees and message authors who have a user account in Jira Service Management. Where Jira Service Management cannot store one of them natively, it is kept as embedded metadata on the migrated record.

If the new system can't natively support an old record type, what are my options?

We handle it case by case. While mapping your data, we identify every record type without a direct counterpart in Jira Service Management, review sample records from it and propose how it can be represented, based on what Jira Service Management supports: map it to the closest native object, create a custom field or object, fold it into the parent record as text or a note, attach it as a file, or keep it in a read-only archive. You choose the approach, we write the migration scripts to place the data there, so it comes across in the form you choose instead of being left behind, and you see how it looks in a sample migration before we run the full set.

Will the migration set off automations or send emails or notifications to customers, our team or anyone else?

No. Before the sample or full migration starts, we confirm with you that nothing in Jira Service Management will send messages about the migrated data: we import with notifications switched off wherever Jira Service Management allows it, and either pause any automation that could send them for the migration window or give it a condition, such as a suppression tag, that skips migrated records, which lets your live automations keep running for new records. We only proceed once you have confirmed it. If you want anyone told about the move, that message is sent separately, once the migrated data has been checked.

Can you migrate data that Jira Service Management can't take in through an API?

In many cases, yes. Where something can't be written through an API, we recreate it through Jira Service Management's user interface where the interface allows it, and where that work is repetitive we script and automate it. We tell you up front which items are handled this way, because recreating them through the interface can add time to the schedule.

What happens if Jira Service Management requires fields our BMC Helix ITSM data doesn't have?

We check the destination for required fields your source data cannot fill and bring each one to you before those records are migrated. Together we agree how each one is handled, such as a mapping from an existing field, a default value, or, where Jira Service Management lets that field be made optional, setting it to not required for the migration so you can make it required again once the migration is complete. The migration then runs with that rule applied, so no records are rejected or left behind.

How will we tell migrated records apart from the ones already in Jira Service Management?

We can mark every migrated record in Jira Service Management, for example with a custom checkbox field such as "Migrated from BMC Helix ITSM", so your team can tell migrated data apart from records created there. We agree the marker with you during scoping so it fits how your team uses Jira Service Management.

Timeline & downtime

2 questions

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; very large migrations, such as several hundred thousand records, take longer. We provide a detailed timeline after the initial assessment and can often complete small migrations in under 24 hours.

Will there be downtime when migrating from BMC Helix ITSM to Jira Service Management?

No. Our migration process is designed for zero downtime. BMC Helix ITSM stays fully operational throughout: the bulk migration runs in the background and the cutover is fast, so there is no disruption to your live business operations.

Security & access

1 question

Can we whitelist a single IP instead of opening our network to your migration tool?

Yes. All migration traffic runs through a centralized system using one fixed IP, which your IT team can whitelist instead of opening broader network access.

Pricing

1 question

Is migration pricing a flat fee, or does it scale with data volume?

It's a flat fee with no hidden costs. The price we agree with you for your scope is the price you pay, and small variances in the final volume, a bit more or less, are included.

After go-live

4 questions

How do I validate that everything migrated correctly?

Every client receives a Migration Validation Report with comprehensive metrics including record-count comparison, attachment integrity verification via checksum, and full audit logs of the migration run, showing every record created, skipped or failed. If any item didn't come across, the report names each one, the specific reason, and how to bring it across if you want it there. We also offer unlimited sample migrations, so you can check your data before the full migration runs.

What support do you provide after the migration goes live?

At ClonePartner, we consider ourselves your partners in this journey. We take full accountability for your migration's success. Once your migration goes live, we provide 30 days of comprehensive post-migration support as standard, and longer support, such as 60 or 90 days, can be agreed for your project. During this period, we help with anything related to your migrated data, so your migration is a complete success.

Will we get a migration report and a mapping sheet linking old record IDs to new ones?

Yes. We provide a comprehensive migration report along with an ID-mapping sheet that links each old BMC Helix ITSM record ID to its new ID in Jira Service Management. This ensures full traceability, simplifies post-migration verification, and helps your team validate that records have been migrated accurately.

After migration, do I contact ClonePartner or the platform's own support if something looks wrong?

ClonePartner is the contact for anything about the migrated data itself. Questions about the platform itself, such as how its features and settings work, go to the platform's own support or to whoever administers it for you.

Migrate from BMC Helix ITSM to Jira Service Management with precision & ease

Why teams migrate from BMC Helix ITSM to Jira Service Management