BMC Remedy to ServiceNow Data Migration
Replacing Remedy with ServiceNow? Settle automates the mapping between Remedy's form-based architecture and ServiceNow's ITIL tables — preserving incident history, change records, CMDB relationships, and SLA data.
Working with enterprise teams on active migration programs
Days
to production-ready mappings
Roughly half
the cost of consulting-led delivery
Every row
validated before go-live
Enterprise migrations routinely run months behind schedule. Yours doesn't have to.
This guide is for VPs of IT, data architects, and migration leads at companies moving data from BMC Remedy to ServiceNow — whether you're scoping, planning, or mid-program.
BMC Remedy stores ITSM data in a form-based architecture with HPD:Help Desk (incidents), CHG:Infrastructure Change (changes), and AST:Attributes (CMDB) using AR System forms with custom fields and workflow rules. ServiceNow uses ITIL-aligned tables — incident, change_request, cmdb_ci — with a fundamentally different data model. Settle translates Remedy's form-based schema to ServiceNow's table architecture automatically.
Based on the founding team's enterprise migration experience
Last updated July 2026
How Settle automates your BMC Remedy to ServiceNow migration
Settle profiles Remedy's AR System forms and maps each to the corresponding ServiceNow table — HPD:Help Desk to incident, CHG:Infrastructure Change to change_request — with field-level type translation including Remedy's Character, Diary, Selection, and Date fields.
Atrium CMDB classes are mapped to ServiceNow's CMDB class hierarchy with attribute translation and relationship type alignment — preserving CI data and dependency maps.
Remedy support groups and permission structures are translated to ServiceNow assignment groups and ACLs — generating the group membership and access control configuration.
Settle catalogs all active links, filters, and escalations with field-level dependencies, generating a Flow Designer rebuild checklist for the ServiceNow implementation team.
Get your BMC Remedy to ServiceNow mapping analysis — see results in under an hour
Migration timeline: manual vs. Settle
Traditional approach
Timeline
12–18 months
Estimated cost
$1.5M+
Team size
8–15 consultants
Typically requires
×Manual field mapping in spreadsheets
×Custom ABAP/SQL extraction scripts
×3–5 mock migration cycles
×Dedicated source system consultants
×Manual reconciliation testing
With Settle
Enterprise benchmarksTimeline
Days
Estimated cost
A fraction of consulting cost
Team size
2–4 internal resources
Included
✓Schema profiling & analysis
✓AI-generated field mappings
✓Transformation SQL
✓Validation & readiness reports
✓Production-ready load files
Common challenges migrating from BMC Remedy to ServiceNow
AR System forms to ServiceNow tables
Remedy uses AR System forms as its core data structure — each form has custom fields, permissions, and workflow. ServiceNow uses database tables with dictionary entries. The form-to-table mapping is not one-to-one: Remedy's HPD:Help Desk has different field structures than ServiceNow's incident table. Custom fields on Remedy forms (Character, Diary, Selection, Attachment) must map to ServiceNow field types (String, Journal, Choice, Attachment).
Explore related migrations →Atrium CMDB to ServiceNow CMDB class hierarchy
Remedy's Atrium CMDB uses a class hierarchy (BMC_BaseElement, BMC_ComputerSystem, BMC_Application) with class-specific attributes and relationship types. ServiceNow's CMDB uses a different class structure (cmdb_ci, cmdb_ci_computer, cmdb_ci_service). The class mapping, CI attribute translation, and relationship type alignment require deep analysis of both CMDB models.
Explore related migrations →Active links and workflow to ServiceNow Flow Designer
Remedy's automation uses active links (client-side), filters (server-side), and escalations (time-based). ServiceNow uses business rules, Flow Designer, and SLA definitions. The automation logic doesn't migrate — it must be rebuilt. Settle documents field references and trigger conditions for each Remedy workflow.
Explore related migrations →Multi-tenancy and permission model translation
Remedy uses support groups, permission fields, and row-level security through AR System permissions. ServiceNow uses assignment groups, ACLs, and domain separation. The security model translation affects which records users can see and edit post-migration.
Explore related migrations →Historical ticket volume and performance
Mature Remedy instances contain millions of incident, change, and problem records spanning 10–20 years. Migrating this volume into ServiceNow requires careful scoping — most organizations migrate 2–5 years of detail plus summary data for older records.
Explore related migrations →BMC Remedy to ServiceNow field mapping — what data moves
12 data objects typically migrated
| Source Object | → | Target Object |
|---|---|---|
| HPD:Help Desk (Incident) | → | Incident (incident) |
| HPD:WorkLog (Work Info) | → | Work Note / Comment |
| CHG:Infrastructure Change | → | Change Request (change_request) |
| CHG:Task | → | Change Task (change_task) |
| PBM:Problem Investigation | → | Problem (problem) |
| SRM:Request (Service Request) | → | Request (sc_request) |
| AST:Attributes (CMDB) | → | CMDB CI (cmdb_ci_*) |
| BMC.CORE:BMC_BaseRelationship | → | CI Relationship (cmdb_rel_ci) |
| CTM:People (Contacts) | → | sys_user / customer_contact |
| CTM:Support Group | → | Assignment Group (sys_user_group) |
| KM:Knowledge (Knowledge Base) | → | Knowledge Article (kb_knowledge) |
| SLA:SLA Definitions | → | SLA Definition (contract_sla) |
Typical enterprise migrations include 500K–10M+ records across these objects. Settle handles profiling and mapping at enterprise scale.
The cost of manual BMC Remedy to ServiceNow migration
BMC Remedy to ServiceNow is the single largest ITSM platform migration in enterprise IT. Remedy (including Remedy ITSM, Remedy OnDemand, and Helix ITSM) has been the dominant enterprise ITSM platform for decades, but companies are migrating to ServiceNow for its modern cloud architecture, superior user experience, and faster innovation cycles. This migration is driven by Remedy's aging on-premise infrastructure costs, limited SaaS options, and the difficulty of finding Remedy AR System administrators and developers.
The technical complexity is significant because Remedy and ServiceNow use fundamentally different architectures. Remedy stores data in AR System forms — HPD:Help Desk for incidents, CHG:Infrastructure Change for changes, AST:Attributes for CMDB — with custom fields, active links, and escalation rules defined in the AR System. ServiceNow uses relational tables with a different field naming convention, workflow engine, and CMDB structure. Remedy's Atrium CMDB uses a class hierarchy that maps differently to ServiceNow's CMDB class structure.
These migrations are typically managed by large consulting firms over 12–18 months. The data conversion workstream — mapping Remedy forms to ServiceNow tables, translating CMDB class hierarchies, and preserving workflow logic context — consumes 25–35% of the total program effort.
Consulting-led delivery for migrations in this class typically runs $1.5M+. Settle prices it fixed and scoped — read the full cost breakdown.
Frequently asked questions
Related migration paths
Exceptions surface before the first load, not after the third.
Built by the team that ran Fortune 500 migrations by hand. Currently onboarding enterprise design partners on active migration programs.
Ready to migrate from BMC Remedy to ServiceNow?
Tell us about your migration and we'll show you how Settle can help.
No commitment required. We'll review your migration scope and share a preliminary assessment within 48 hours.