Remedy to ServiceNow Migration 2026: Forms, Foundation Data, CMDB

Methodology: built from BMC Helix and ServiceNow product documentation, the BMC support version pages and the ServiceNow ITSM pricing page, all checked on 7 Oct 2026. No vendor reviewed or paid for this article. We did not run hands-on tests.

A Remedy to ServiceNow migration moves records from AR System forms such as HPD:Help Desk, CHG:Infrastructure Change and PBM:Problem Investigation into the ServiceNow incident, change_request and problem tables, along with Foundation data, work info and CMDB items. Workflows, SLAs and approvals are rebuilt on ServiceNow, not moved. This guide is for Remedy and BMC Helix ITSM teams whose version is near the end of BMC support and who have picked ServiceNow. It gives the dated triggers, a form-to-table mapping checked against both vendors' docs, and a phased plan.

Key takeaways

• BMC Helix ITSM OnPrem 23.3.04 and 25.2.01 reach end of version support on 3 Dec 2026, and 25.3.01 on 3 Mar 2027 (BMC support version page, as of 7 Oct 2026).
• Remedy work info has a View Access of Internal or Public; in ServiceNow, "All users who can view incidents see additional comments" (BMC Service Desk docs; ServiceNow incident docs, as of 7 Oct 2026).
• ServiceNow has no Assigned incident state. Its states are New, In Progress, On Hold, Resolved, Closed and Canceled (ServiceNow incident docs, as of 7 Oct 2026).
• BMC Helix SaaS permits read-only database access "via a JDBC connection only" (BMC Helix subscriber docs, as of 7 Oct 2026).
• Change and Problem Management sit in ITSM Advanced and Prime, not Foundation (ServiceNow ITSM pricing page, as of 7 Oct 2026).

Why teams move from Remedy or BMC Helix ITSM to ServiceNow

Most Remedy to ServiceNow projects start with a support date. Staying on BMC still means a migration: BMC documents the move from Remedy on premises to BMC Helix on premises as "a fresh installation of BMC Helix Service Management and migrating data", not an in-place upgrade (BMC Helix deployment docs, as of 7 Oct 2026). Once a data migration is coming either way, teams compare targets.

For containerized BMC Helix releases, BMC gives 1 year of full support from general availability plus 6 months of limited support, which covers "only critical security vulnerabilities and major defects" (BMC containerized products support policy, updated 1 Jan 2025).

Source: BMC support version pages for BMC Helix ITSM OnPrem and Remedy AR System Server, as of 7 Oct 2026.

On 23.3.04 or 25.2.01, a ServiceNow cutover before 3 Dec 2026 is tight. The alternative is one more BMC upgrade to stay supported while the migration runs. Price that in.

What moves, what gets rebuilt, what's at risk

The rule: records and their links move; Remedy behavior does not. Filters, active links, escalations and overlays stay in AR System.

Field mapping Remedy to ServiceNow

Map each form to a table first, then map the values inside each field.

Sources: BMC Helix Dashboards 23.3 and BMC Helix ITSM 26.2 REST API docs; ServiceNow Table, Attachment, Change Management, CMDB and Map pages docs, as of 7 Oct 2026.

States and status reasons

BMC lists incident statuses New, Assigned, In Progress, Pending, Resolved, Closed and Cancelled (BMC Service Desk 26.2 docs, as of 7 Oct 2026). ServiceNow's On Hold reasons are Awaiting Caller, Awaiting Change, Awaiting Problem and Awaiting vendor (ServiceNow incident docs, as of 7 Oct 2026).

Changes need the same work. ServiceNow normal changes use New, Assess, Authorize, Scheduled, Implement, Review, Closed and Canceled (ServiceNow change state model docs, as of 7 Oct 2026). A starting point for BMC's statuses (BMC Change Management docs, as of 7 Oct 2026): Draft to New; Request For Authorization and Request For Change to Assess; Scheduled For Approval to Authorize; Implementation In Progress to Implement; Completed to Review; Rejected and Cancelled to Canceled. Pending has no equivalent, so keep the prior state and flag it.

Priority, impact and urgency

Remedy uses impact values such as "1-Extensive/Widespread" and urgency values such as "1-Critical" (BMC Helix ITSM REST API docs, as of 7 Oct 2026). In ServiceNow, "By default, the Priority field is read-only and must be set by selecting the Impact and Urgency values", and the example lookup rules use High, Medium and Low (ServiceNow priority lookup docs, as of 7 Oct 2026). Map impact and urgency, let ServiceNow calculate priority, and keep the original Remedy priority in a read-only field.

Foundation data: companies, sites, support groups, people

BMC's data load process names five Foundation loads: Company, Organization, Location, Support Group and People (BMC Helix ITSM 25.4 docs, as of 7 Oct 2026). Load ServiceNow in the same order: core_company, cmn_location, sys_user_group, then sys_user. BMC says support users "must belong to at least one support group" and need a login ID; non-support users are everyone who requests services (BMC Helix ITSM 23.3 docs, as of 7 Oct 2026). In ServiceNow, that split becomes users with and without fulfiller roles.

Work info, attachments and relationships

Each Remedy work info entry has a Work Info Type, Notes, a Locked flag, a View Access of Internal or Public, and up to three attachments (BMC Service Desk 21.3 docs, as of 7 Oct 2026). Map Internal to work notes and Public to additional comments. Reversing them exposes internal notes to requesters.

ServiceNow's Attachment API handles "a single file with each request", with a default maximum of 1,024 MB (ServiceNow Attachment API docs, as of 7 Oct 2026). Record links use the incident's Problem, Change Request and Caused by Change fields (ServiceNow incident docs, as of 7 Oct 2026).

CIs from BMC CMDB to cmdb_ci

BMC models CIs as subclasses of BMC_BaseElement and relationships as subclasses of BMC_BaseRelationship (BMC Helix CMDB 25.2 docs, as of 7 Oct 2026). Its Reconciliation Engine merges import datasets into the BMC Asset dataset, the production dataset (BMC CMDB architecture docs, as of 7 Oct 2026). Extract from production only.

ServiceNow stores relationships in cmdb_rel_ci with a parent CI, child CI and a type such as Depends on / Used by (ServiceNow CMDB docs, as of 7 Oct 2026). Its Identification and Reconciliation Engine (IRE) "prevents duplicate CIs", applies to import sets, and can identify CIs by source_name and source_native_key (ServiceNow IRE docs, as of 7 Oct 2026). Use a stable BMC identifier as the native key so reruns update instead of duplicating.

Export from Remedy, import into ServiceNow

Export. The AR System REST API reads entries on forms under /api/arsys/v1/entry/{formName}, authenticates through /api/jwt/login, and "A single JWT token is valid for an hour" (Remedy AR System 20.02 REST API docs, as of 7 Oct 2026). Long extracts need token refresh. On BMC Helix SaaS, "No direct-write connection to the database is allowed" and read access is through JDBC only (BMC Helix subscriber docs, as of 7 Oct 2026).

Import. The Import Set API inserts rows into a staging table and applies transform maps; insertMultiple runs asynchronously by default (ServiceNow Import Set API docs, as of 7 Oct 2026). Coalesce on the Remedy ID: a match updates, no match inserts, and with several matches "only the first matching record in the target table is updated" (ServiceNow coalesce docs, as of 7 Oct 2026). Read back with the Table API, whose sysparm_limit defaults to 10,000 records per request with sysparm_offset for paging (ServiceNow Table API docs, as of 7 Oct 2026). Load attachments last.

We found no ServiceNow-documented importer built for Remedy, so plan to script this path or bring in a migration partner.

Remedy to ServiceNow migration plan in phases

1. Discover. Inventory forms, custom fields, overlays, record counts per year, attachment volume, CMDB classes and integrations.
2. Map. Build the form, value and Foundation maps above. Decide history scope: everything, open plus recent years, or open only with an archive.
3. Test migration. Load Foundation data, then a full copy into sub-production. Check counts, states, priorities, work info visibility, attachments and relationships.
4. Cutover with delta sync. Freeze Remedy, load records changed since the last full load, rerun coalesce and repoint integrations.
5. Reconcile. Compare counts per form and state, sample records field by field, check CI relationship counts, then hold the go/no-go.
6. Hypercare. Watch assignment, notifications and SLAs. Keep Remedy read-only for lookups.

BMC Helix to ServiceNow failure points

• Foundation out of order. Load people before their companies, locations and groups and references break. A missing referenced sys_id "could potentially appear in the target record as the DisplayValue" (ServiceNow transform map docs, as of 7 Oct 2026).
• The Assigned gap. Without one agreed rule, backlog reports shift on day one.
• SLA history. ServiceNow SLA repair "uses the history from the Task" (ServiceNow SLA repair docs, as of 7 Oct 2026). Imported records only have the history the import created, so store Remedy SLM results as fields.
• CMDB duplicates. Loading from an import dataset such as BMC.ADDM, or skipping IRE, duplicates CIs.
• Package gaps. Check that your ServiceNow subscription includes Change and Problem before loading their history.

Remedy to ServiceNow checklist

1. Confirm your BMC version's end of version support date.
2. Confirm your ServiceNow package covers Change and Problem.
3. Inventory forms, custom fields and overlays, with record counts per year.
4. Decide history scope and the archive approach.
5. Map HPD:Help Desk, PBM:Problem Investigation, CHG:Infrastructure Change and TMS:Task.
6. Agree value maps for incident status, Pending reasons and change status.
7. Map impact and urgency; keep the original priority in a field.
8. Load Foundation data in order: company, location, support group, people.
9. Split work info by View Access: Internal to work notes, Public to additional comments.
10. Extract CIs from the production dataset and load them through IRE.
11. Check Remedy IDs are unique before using them as coalesce keys.
12. Store original created and resolved dates and SLM results as fields.
13. Run a full test migration and reconcile it.
14. Plan the freeze window, delta load and integration repointing.

FAQ

Methodology

We read BMC Helix and Remedy documentation on docs.helixops.ai and docs.bmc.com, the BMC support version pages, and ServiceNow product documentation and pricing pages on 7 Oct 2026. Form and table names appear only where a vendor page we opened confirmed them. State mappings and load order are our suggested starting points, not vendor rules. We did not run hands-on tests.

Disclosure: MigrateX, the publisher of this article, runs ITSM data migrations, including between platforms named here. No vendor reviewed or paid for this article.