
BMC Helix ITSMServiceNow
BMC Helix ITSM to ServiceNow migration
ITSM specialists move your people (ctm:people), incidents (hpd:help desk) and work info (hpd:worklog) into ServiceNow, check a sample with you first, and count every record on both sides.
Free sample migration of 100 of your records, plus a fixed quote within 24 hours.
Last updated October 2026 · 14 object types mapped
- 1000+migrations
- 15 yearsof collective experience
SOC 2 Type IIGDPR compliantHIPAA compliant
BMC Helix ITSM to ServiceNow at a glance
We move incidents, problems, changes, work orders, people, support groups, knowledge and CMDB data from BMC Helix ITSM (formerly Remedy) into ServiceNow, with Internal and Public work info kept apart. Our ITSM team runs this route as an engineer-led migration: Foundation data first, test loads in sub-production, and a reconciled cutover.
- Objects mapped
- 14
- in this route's mapping
- Typical timeline
- About 8-10 weeks for a typical Remedy estate; very large CMDBs or heavy customisation add test cycles
- 3 phases
- Free sample
- 100 records
- checked by your team first
- Quote
- Fixed
- within 24 hours
What moves
What moves from BMC Helix ITSM to ServiceNow
Every record type is mapped from BMC Helix ITSM to its ServiceNow equivalent.
- 14 included
| BMC Helix ITSM | maps to | ServiceNow | Status |
|---|---|---|---|
| Companies (Foundation) | Companies (core_company) | Included | |
| People (CTM:People) | Users (sys_user) | Included | |
| Support Groups (CTM:Support Group) | Assignment groups (sys_user_group) | Included | |
| Incidents (HPD:Help Desk) | Incidents (incident) | Included | |
| Work Info (HPD:WorkLog) | Work notes and Additional comments | Included | |
| Problems (PBM:Problem Investigation) | Problems (problem) | Included | |
| Known Errors (PBM:Known Error) | Problems flagged as known error | Included | |
| Changes (CHG:Infrastructure Change) | Change requests (change_request) | Included | |
| Service Requests (SRM) | Requested items (sc_req_item) | Included | |
| Work Orders (WOI:WorkOrder) | Catalog tasks (sc_task) | Included | |
| Attachments | Attachments (sys_attachment) | Included | |
| Knowledge Articles (RKM) | Knowledge articles (kb_knowledge) | Included | |
| Configuration Items (BMC_BaseElement) | CI classes (cmdb_ci) | Included | |
| CI Relationships (BMC_BaseRelationship) | CI relationships (cmdb_rel_ci) | Included |
- Companies (Foundation)Companies (core_company)
- People (CTM:People)Users (sys_user)
- Support Groups (CTM:Support Group)Assignment groups (sys_user_group)
- Incidents (HPD:Help Desk)Incidents (incident)
- Work Info (HPD:WorkLog)Work notes and Additional comments
- Problems (PBM:Problem Investigation)Problems (problem)
- Known Errors (PBM:Known Error)Problems flagged as known error
- Changes (CHG:Infrastructure Change)Change requests (change_request)
- Service Requests (SRM)Requested items (sc_req_item)
- Work Orders (WOI:WorkOrder)Catalog tasks (sc_task)
- AttachmentsAttachments (sys_attachment)
- Knowledge Articles (RKM)Knowledge articles (kb_knowledge)
- Configuration Items (BMC_BaseElement)CI classes (cmdb_ci)
- CI Relationships (BMC_BaseRelationship)CI relationships (cmdb_rel_ci)
Looking for another object?Field-level mapping is reviewed with you during scoping.
What does not move
What does not move from BMC Helix ITSM to ServiceNow as-is
These BMC Helix ITSM items are not migrated as records; each line says what takes their place in ServiceNow.
- SLM service targetsNot migrated
- In ServiceNow: Rebuilt as SLA definitions
- Not migrated
- Approval historyNot migrated
- In ServiceNow: Summarised as work notes
- Not migrated
Free sample migration of 100 of your records. Fixed quote within 24 hours.
Scope my migrationTimeline
BMC Helix ITSM to ServiceNow migration timeline
Estimated total
About 8-10 weeks
for a typical Remedy estate; very large CMDBs or heavy customisation add test cycles
- MigrateXwe run it
- Youyour team acts
- Bothon a call together
Discovery and mapping
Weeks 1-3
Access and inventory
Both1 weekYou provide a read-only Remedy API account (or a Data Connector replica on SaaS) and a ServiceNow integration user. We count records per form and year, size attachments, list custom fields and overlays, and pull the CMDB class and relationship counts.
Scope and history decision
You2-3 daysYou decide what history moves: everything, open plus recent years, or open only with an archive. We confirm your ServiceNow subscription covers change and problem before their history is in scope.
Mapping sign-off
Both1 weekWe send the form-to-table map, value maps for status, status reason, impact and urgency, the Foundation load plan and the CDM class map. You approve or amend it.
Test migrations
Weeks 4-7
Foundation load
MigrateX3-5 daysCompanies, locations, support groups and people load into a ServiceNow sub-production instance, with roles and group membership.
Full test migration
MigrateX1-2 weeksIncidents, problems, known errors, changes, requests, work orders, work info, attachments, knowledge and CIs load in dependency order, checkpointed by Remedy ID.
Your review and a second pass
Both1-2 weeksYour process owners check counts, states, work note visibility, CI relationships and sample records. We fix the maps and run the test load again until it reconciles.
Cutover and validation
Weeks 8-10
Production bulk load
MigrateX3-5 daysThe signed-off load runs into production while Remedy stays live, so the service desk keeps working.
Freeze, delta and go-live
Both1-2 daysRemedy is frozen, records changed since the bulk load are synced by last-modified date, integrations are repointed and intake moves to ServiceNow.
Reconciliation and sign-off
Both1 weekCounts per form, state and group on both sides, CI relationship counts, a list of every default mapping used, and the Remedy ID to sys_id map. Remedy stays read-only for lookups.
An estimate. Record volume, API rate limits and how fast your team reviews the sample all move it.
Technical profile
What makes this route technical
The API limits and data model differences between BMC Helix ITSM and ServiceNow that shape the plan.
- ServiceNow bulk load path
- The Import Set API writes rows into a staging table at /api/now/import/{stagingTableName} and runs the transform maps defined on it. Transform maps coalesce on a key, so a rerun updates the record instead of creating a duplicate.
Source: ServiceNow documentation, checked 15 Nov 2026
- ServiceNow Table API page size
- sysparm_limit defaults to 10,000 records per request. We use it to read back loaded records for reconciliation and for the sys_id map.
Source: ServiceNow documentation, checked 15 Nov 2026
- ServiceNow attachment ceiling
- The Attachment API takes one file per request. com.glide.attachment.max_size defaults to 1024 MB per file, and allowed types come from glide.attachment.extensions.
Source: ServiceNow documentation, checked 15 Nov 2026
Facts checked 15 Nov 2026 against ServiceNow documentation. Each fact links its source.
BMC Helix ITSM to ServiceNow questions
Still unsure? Ask the engineer who would run this migration, not a sales rep.
Is BMC Helix ITSM the same as Remedy?
Yes, in practice. BMC Helix calls BMC Helix ITSM the next generation of Remedy. The core AR System forms carry over, which is why HPD:Help Desk, CHG:Infrastructure Change and PBM:Problem Investigation still appear in current BMC Helix docs. The same mapping applies whether you run older Remedy, BMC Helix on-premises or BMC Helix SaaS.
Is there a built-in importer to move Remedy data into ServiceNow?
We found no ServiceNow-documented importer built for Remedy. Data leaves through the AR System REST API, or on SaaS through a database replica, and enters ServiceNow through import sets and transform maps plus the Attachment API. Our ITSM team runs this route as an engineer-led migration with scripts built for your forms.
Do we need to migrate the CMDB?
Not always. If ServiceNow discovery will rebuild your infrastructure CIs, many teams migrate only the CIs that tickets reference, plus business services and applications that discovery cannot find. If you need full CI history and relationships, we migrate from the production dataset through ServiceNow's reconciliation engine. We help you decide during discovery.
What happens to Internal and Public work info?
Each Work Info entry is posted to the matching ServiceNow journal in date order: Internal to work notes, Public to additional comments. The original author and date are written into each entry. Your team checks a sample of both before the bulk pass, because a reversed flag would expose internal notes to requesters.
How do Remedy statuses map when ServiceNow has no Assigned state?
We agree one rule with you, usually Assigned to In Progress with the assignment group set. Pending maps to On Hold with a reason taken from the Remedy Status Reason. The original status and status reason are kept in read-only fields so old reports still work.
Do our SLAs move?
No. Service targets and running timers are rebuilt as ServiceNow SLA definitions. Historic SLM results, such as met or missed and the target times, are stored as fields on each migrated record so past SLA reporting holds.
Where do work orders go?
Work orders are fulfilment work for service requests, so they become catalog tasks (sc_task) under the requested item that carries the original request. Work orders raised on their own, without a request, are scoped with you during discovery.
Are original created and resolved dates preserved?
Yes. Tickets load through import sets, where the opened, resolved and closed dates are set from Remedy and the system created date is set in the transform. The original Remedy ID is kept on every record so agents can still search by it.
Is there downtime during the migration?
No. We only read from Remedy during the bulk load. At cutover Remedy is frozen for a short window, records changed since the bulk load are synced, integrations are repointed and intake moves to ServiceNow. Remedy stays read-only afterwards for lookups.
How long does it take?
Around eight to ten weeks for a typical Remedy estate: three for discovery and mapping, four for test migrations, and up to three for cutover and validation. Very large CMDBs, heavy customisation or extra test cycles add time.
How it compares
Four ways to run BMC Helix ITSM to ServiceNow
The same data, moved four different ways. This is what changes between them.
Object coverage (incidents, problems, changes, requests, KB)
MigrateX
Every object in the BMC Helix ITSM connector, plus the ones you ask for during scoping.
Automated migration software
Tickets and contacts are covered. Problems, changes and request items often are not.
Vendor CSV import
One object per file, and only the fields the export template exposes.
In-house scripts
Whatever you have time to build before the cutover date.
Work notes vs comments fidelity
MigrateX
Each entry is posted separately, private stays private, public stays public.
Automated migration software
Threads usually arrive, but per-entry author and visibility can be flattened.
Vendor CSV import
Notes collapse into one field on the ticket, if they come across at all.
In-house scripts
Possible, but it is the part teams most often run out of time for.
Attachments
MigrateX
Uploaded against the right note, and re-hosted with a link when they exceed the ServiceNow cap.
Automated migration software
Supported up to the destination cap. Oversize files are skipped.
Vendor CSV import
Not carried by a CSV import.
In-house scripts
Needs its own download, retry and upload pipeline.
Original IDs cross-referenced
MigrateX
Every source id is stored on the destination record and handed back as a map.
Automated migration software
Often kept as a tag or a single text field.
Vendor CSV import
Lost once the file is imported.
In-house scripts
Only if you design the mapping table up front.
Delta sync before cutover
MigrateX
Included. Anything created or changed during the bulk pass is synced at cutover.
Automated migration software
Usually a paid upgrade on the top tier.
Vendor CSV import
You would re-export and re-import by hand.
In-house scripts
Requires change tracking and idempotent writes on both sides.
Rate-limit handling
MigrateX
Paced to your plan limits, honours Retry-After, and resumes from a checkpoint.
Automated migration software
Backs off, but a long run can still stall and leave partial records.
Vendor CSV import
Not applicable, and the file size limits bite instead.
In-house scripts
The most common reason a home-grown run dies overnight.
Validation report
MigrateX
Counts per object and per status on both sides, with every default and placeholder listed.
Automated migration software
A run log and an error list, rather than a reconciliation.
Vendor CSV import
Row counts in a spreadsheet.
In-house scripts
You write the reconciliation queries yourself.
Rollback plan
MigrateX
Every write is tagged, so a batch can be reversed without touching your own records.
Automated migration software
Some approaches can clear a migration, some cannot.
Vendor CSV import
Manual cleanup of everything the import created.
In-house scripts
Only if you built the tagging in from the start.
Who does the work
MigrateX
A MigrateX engineer runs it and stays on the cutover call.
Automated migration software
You run the software. Support answers tickets.
Vendor CSV import
Your admins, one file at a time.
In-house scripts
Your engineers, instead of your roadmap.
Guides
Guides for a BMC Helix ITSM to ServiceNow migration
Related routes
Other routes we run
Built for your security review, from the first call.
Read how we handle your data
SOC 2 Type II
Independently audited controls over how we handle your data.
GDPR compliant
Data processing agreement available.
HIPAA compliant
Business associate agreement available.

Start your ServiceNow move with 100 of your records.
Scope my migrationFree sample migration of 100 of your records, plus a fixed quote within 24 hours.








