BMC Helix ITSM migration

Moving off BMC Helix ITSM?

BMC Helix ITSM (formerly Remedy) keeps incidents, work orders, changes and problems, with Work Info history and a CMDB built on the Common Data Model. We move that history to ServiceNow or Freshservice.

Scope my migration

Free sample migration of 100 of your records, plus a fixed quote within 24 hours.

  • 1000+migrations
  • 15 yearsof collective experience
  • AICPA SOC 2 Type IISOC 2 Type IIGDPR compliantHIPAA compliant

Read how we handle your data

What moves

What moves from BMC Helix ITSM?

The objects we carry across by default. Your exact scope is agreed on the scoping call.

  • Incidents
  • Work Orders
  • Changes
  • Problems
  • People
  • Support Groups
  • Configuration Items
  • Knowledge Articles

What does not move

What does not move from BMC Helix ITSM as-is

Configuration, not data. We list each item in scope so your team can rebuild it in the target.

  • Remedy workflow (filters, active links and escalations): rebuilt in the target
  • Service level targets and running SLA timers
  • Form customisations and overlays

Free sample migration of 100 of your records. Fixed quote within 24 hours.

Scope my migration

Migration paths

Where can I move to or from BMC Helix ITSM?

Routes we run from and into BMC Helix ITSM. Open a route to see what migrates, or ask us about one that is not listed yet.

From BMC Helix ITSM

191 connectors, all live

Every connector is live, so BMC Helix ITSM can be paired with any of them. Some of the ITSM platforms:

  • Jira Service Management
  • Cherwell
  • Ivanti Neurons for ITSM
  • ManageEngine ServiceDesk Plus
  • HaloITSM
  • TOPdesk
  • SysAid
  • SolarWinds Service Desk
  • IBM Control Desk
See all 191 connectors

Platform not listed?

We build new connectors in 2 to 3 days. Tell us what you run and we scope the route with you.

Timeline

Your BMC Helix ITSM migration, step by step

Estimated total

About 10 business days

end to end

  • MigrateXwe run it
  • Youyour team acts
  • Bothon a call together
  1. Preparation

    Day 1-2

    • Scoping call

      Both0.5 day

      A 30 minute call with the engineer who will run the migration, to agree the objects, date ranges and volumes in scope.

    • Connect both platforms

      You0.5 day

      You create scoped API credentials on the source and the destination. Nothing is written until you sign off the mapping.

    • Field mapping review

      Both1 day

      We walk through every field, status and group mapping with your team and note the ones that need a decision.

  2. Migration

    Day 3-7

    • Free sample migration of 100 records

      MigrateX1 day

      A sample of your real records is migrated end to end so you can see the result before the full run.

    • You review the sample

      You1 day

      Your team opens the migrated records and tells us what to adjust. We rerun the sample until it is right.

    • Full migration

      MigrateX2-3 days

      The bulk pass runs in dependency order, paced to the destination rate limit. Your team keeps working normally.

    • Delta sync

      MigrateX0.5 day

      Everything created or changed during the bulk pass is synced at cutover so nothing falls between the two systems.

  3. Validation

    Day 8-10

    • Validation report

      MigrateX1 day

      Record counts per object and per status on both sides, plus every record that needed a default or a placeholder.

    • Spot checks and sign-off

      You1-2 days

      Your leads check a random sample and sign off. We stay available for two weeks after go-live.

An estimate. Record volume, API rate limits and how fast your team reviews the sample all move it.

See how it works in detail

Data model

How BMC Helix ITSM stores your data

What shapes the export, checked against the vendor's own documentation.

  • Work orders, not only incidents

    Work orders fulfil service requests, and can also support an incident, a CI change or a known error. We map them to the target's request or task model, not to incidents.

    Source: BMC Helix documentation

  • Work Info is its own record

    Work Info entries are separate work log records, and entries can be locked, public or hidden. We read every entry and keep its visibility in the target.

    Source: BMC Helix documentation

  • CMDB on the Common Data Model

    CIs extend the BMC_BaseElement class and relationships extend BMC_BaseRelationship. We map those classes to the target's CMDB classes and relationship types.

    Source: BMC Helix documentation

BMC Helix ITSM migration questions

Still unsure? Ask us on the scoping call.

What does a BMC Helix or Remedy migration cost?

The cost of moving off BMC Helix ITSM, or an older Remedy system, depends on the volume of incidents, work orders, changes and problems, the number of Work Info entries and attachments on them, how much of the CMDB is in scope, and how many customised forms hold data. MigrateX moves 100 of your records as a free sample and then gives you a fixed quote within 24 hours.

How long does a BMC Helix migration take?

Our default plan is about 10 business days end to end. With BMC Helix, the full run takes longest when records carry long Work Info histories, because every entry is its own record and is read separately, and when CMDB relationships are in scope. The scoping call gives you a timeline with dates before any data moves.

Do you migrate older Remedy systems as well as BMC Helix ITSM?

Yes. BMC Helix ITSM was formerly Remedy, and both keep their records in AR System forms, which MigrateX reads form by form. Tell us your version, and whether you run on-premises or BMC Helix SaaS, on the scoping call, because that decides how the data is extracted. Workflow built in Remedy is rebuilt in the target platform, not copied.

Does BMC Helix stay live while the data moves?

Yes. BMC Helix stays live for your service desk during the full run, because MigrateX only reads from it. A delta sync at cutover picks up the records created or changed since the bulk run, using their last-modified date, and you switch over in one planned window with a rollback plan ready.

Do work orders become incidents?

Usually not. In BMC Helix, work orders fulfil service requests, so they map to requested items or tasks in ServiceNow and to service requests or tasks in Freshservice, not to incidents. Loading them as incidents would distort your incident counts and reports. We agree the mapping with you before anything moves.

Is Work Info visibility kept?

Yes. Every Work Info entry is its own record with a visibility setting, and MigrateX reads all of them. Public entries become customer-visible comments, and hidden or internal entries become work notes, in date order, with the original author and date. Attachments on a Work Info entry move with the entry they belong to.

Does the CMDB move with its relationships?

Yes, into targets with a relationship model. BMC Helix CMDB is built on the Common Data Model, where CIs extend the BMC_BaseElement class and relationships extend BMC_BaseRelationship. MigrateX maps those classes to the target's CI classes and relationship types, and you decide on the scoping call which classes are worth moving.

What does not move from BMC Helix?

Remedy workflow does not move. Filters, active links and escalations are logic, not data, so they are rebuilt in the target, and the same goes for service level targets, running SLA timers, form customisations and overlays. MigrateX lists each item in scope so your team or implementation partner knows what to rebuild, and the records arrive with their history.

Guides

Guides for a BMC Helix ITSM migration

Start with 100 of your records.

Scope my migration

Free sample migration of 100 of your records, plus a fixed quote within 24 hours.