Organisations that use BMC Remedy or BMC Helix ITSM are increasingly looking at ServiceNow, in the hope of achieving a more modern, scalable, and unified setup. However, this shift is not a straightforward lift-and-shift. BMC and ServiceNow are, at a fundamental level, built on different architectures. As a result, a successful migration requires deliberate planning, structured data mapping, and disciplined execution.
At Virtuxient Technologies, we support enterprises throughout this transition with a methodology grounded in IT Service Management best practices, ensuring the change enhances day-to-day operations rather than disrupting existing processes or causing avoidable issues.
Why Organisations Are Moving Away from BMC
BMC’s form-based architecture has served IT teams well for decades. Still, there are real limitations to it:
- rigid customisations
- numeric field identifiers
- workflows tightly coupled to individual forms
ServiceNow, in contrast, provides a cloud-native platform with a normalised data model, visual workflow tools, and a large ecosystem of integrations. Teams that complete the migration can generally see improvements in automation, more detailed reporting and the end-user experience, but only when the underlying data and processes are correctly mapped and migrated.
IT Service Management Modules: You Should Know Before Migration
It is important to inventory the IT Service Management modules that are in use before touching any data. Most BMC environments will contain some combination of:
- Incident Management – handling tickets on a day-to-day basis
- Change Management – managed changes to production systems
- Problem Management – root cause investigation and known errors
- CMDB (Configuration Management Database) – assets and relationships
- Knowledge Management – how-to articles, known errors, and reference material
Each of these modules represents a different ServiceNow table, and each mapping has its own complications. The primary one consists of:
- Redistributing BMC’s approximately seven base CI classes into dozens of granular ServiceNow CSDM classes. Care must be taken when migrating work logs from disparate BMC forms to maintain the original timestamps and authorship.
This step can easily be mishandled if scripts are not configured to protect historical audit data.
The migration process – Step by Step
A migration usually goes through five phases:
1. Planning and Assessment — Inventory all active modules, custom fields, and workflows. Check how records will be uniquely identified and evaluate the approach to avoid duplicate CMDB entries once the data is migrated to ServiceNow.
2. Data Extraction and Mapping – Extract data from BMC via API or flat-file export and map relationship tables, user groups, and permission structures to their ServiceNow equivalents.
3. Implementation and Loading — Import Set tables and load data into ServiceNow. Transform Maps and coalesce rules are used to merge and clean records as they load.
4. Validation and Cutover — Test workflows, SLAs and notifications on a sub-production instance, then run a delta migration to capture any transactions created during the cutover window.
5. Decommission – Wait until all historical data has been verified in the new system before decommissioning BMC and removing user access.
Knowledge Management deserves special mention here, as BMC stores article content in several back-end formats depending on the article type (How-To, Known Error, Problem Solution, Reference). To properly migrate these articles, you will need to export both the article metadata and attachments, then reconcile them using a consistent document ID before loading them into ServiceNow’s knowledge base tables.
Selecting the Appropriate IT Service Management Software Approach
Not every migration route is the same. A hands-on CSV import might work for a small, straightforward set of records, but it tends to become difficult to manage at scale, and it usually provides limited validation and no reliable rollback capability. Fully automated tooling moves things quickly; still, it often runs into trouble with custom fields, specialised workflows and CMDB relationships that are specific to how your environment actually behaves.
Most dependable outcomes usually result with a hybrid approach, which includes automation for the large volumes of data, plus engineers who review and validate the field mapping, run tests on the workflows and spot those unusual edge cases that generic utilities tend to miss.
So, in the end, the strongest IT service management software strategy is one that aligns the migration approach you choose:
- with the complexity of your data,
- the compliance requirements you must follow,
- and the amount of downtime your business can tolerate.
To Wrap Up
Migrating from BMC to ServiceNow is a significant technical task, but it does not have to be unpredictable. If you keep a clear inventory of your modules, along with a solid data mapping strategy and a robust validation process that catches issues before cutover, organisations can move to ServiceNow with confidence and less disruption to service continuity.
FAQs
1. Do you have a native tool to migrate directly from BMC to ServiceNow?
No. There is no out-of-the-box connector, so migrations rely on a custom ETL process using APIs, flat-file exports, and ServiceNow’s Import Set and Transform Map tools.
2. How long does a BMC to ServiceNow migration usually take?
It depends on how much data is in scope and how complex the data is. We suggest you use a structured approach, such as building a checklist , doing a small sample run, then moving into the full migration, followed by a delta sync. In general terms, for mid-sized data sets it often takes about 1-2 weeks.
3. What happens to historical work logs and audit trails in a migration?
If the scripting approach is done correctly, the original timestamps and authors are preserved, rather than being overwritten by the migration user’s data. But if it’s mishandled, that audit trail can be lost forever, and it’s not really something you can simply reconstruct later.
4. How does BMC’s CMDB align with ServiceNow’s CSDM?
BMC’s small set of base CI classes needs to be mapped and reclassified to ServiceNow’s much larger set of granular CSDM classes, based on the specific attributes of each configuration item.
5. Is it possible to migrate knowledge articles and attachments without any data loss?
Yes, but careful handling is required for BMC’s template-based back-end forms and use a reliable document ID to match articles with their attachments during the ServiceNow load process.
