Migrating BMC Service Request Management objects and data

Migration is the process of exporting objects and data from one server and importing them to another server.

To migrate, you can follow this process:

Prepare your destination server by importing the following objects and data (which are not migrated through the methods listed in step 2):
- Foundation data, such as companies and people information
- Customizations, such as custom advanced interface forms (AIFs), custom workflow, and registered AIF configuration records
- Configuration data for BMC Service Request Management, such as application target data, service targets, On Behalf Of management, and task templates. Change, incident, and work order templates are migrated by the Import Export Console.
- Work information for objects such as SRDs and PDTs
- Atrium Service Catalog data (requestable offerings and service offerings)
Use one of the following consoles to migrate the Service Request Management and data:
- The Deployment Application in Action Request System

- The Import Export Console in Service Request Management
- Data Management Job Console.

Comparison of the migration methods

The following table provides a quick comparison of each migration method for Service Request Management:

Deployment Application	Import Export Console	Data Management Job Console
Performs a merge operation when staging data as follows: Objects that exist on the server are updated. Objects that do not exist on the server are created. Child objects not included in the .arx file are deleted on the server.	Provides the following options when staging data: Merge Data Import new definitions only and skip duplicates Import new definitions only and cancel import if existing definitions , if found Import all definitions as new and rename all by adding a prefix to name Apply the imported definitions to a different company	Provides the following options when staging data: Import new definitions only and skip duplicates Import new definitions only. You can use "wait" templates that enable you to cancel import if you find duplicates.
Import and export from the Deployment Application console	Import and export from the Import Export Console in Service Request Management	Export from the Import Export Console in Service Request Management, and import from the Job Console. See Loading Foundation data by using Data Management.
Import Service Request Management, data from BMC Helix ITSM, and other AR System objects and data	Import only Service Request Management data	Import Foundation data and data from BMC Helix ITSM
Users require Remedy Administrator or Deployment Manager permissions to import data	Users require AR Administrator permissions to import data	Users require Data Management Tool (DMT) User or DMT Administrator permission to import data.
Imports application templates along with AOTs	Imports application templates along with AOTs	Cannot import application templates along with AOTs
Files are exported to your local computer	Files must reside on the server	Files must reside on the client
Automated staging, validation, and promotion of data	Manual staging, validation, and promotion of data	Automated staging, validation, and promotion of data
Does not provide a job scheduler to schedule job	Does not provide a job scheduler to schedule jobs	Provides a job scheduler to schedule jobs
Checks BMC Service Request Management foundation data IDs on import	Checks BMC Service Request Management foundation data IDs on import	Does not check foundation data IDs on import

Objects and data that are migrated

The Import Export Console and the Deployment Management Console allow you to choose whether to migrate SRDs, PDTs, or supporting data. The following table shows the objects and data that are migrated with each.

Type of object or data	Migrated with:
Type of object or data	SRDs	PDTs	Supporting data
SRDs	Yes	No	No
Actions	Yes	No	No
Questions related to an SRD	Yes	No	No
Question to SR Field mappings	Yes	No	No
Question to Variable mappings	Yes	No	No
PDTs	Yes	Yes	No
Variables	Yes	Yes	No
SRD and PDT Work Info	No	No	No
Application template bridge	Yes	Yes	No
Application target data	No	No	No
Change templates	Yes	Yes	No
Incident templates	Yes	Yes	No
Work order templates	Yes	Yes	No
Survey questions	Yes	No	Yes
Images	Yes	No	Yes
Navigational categories	Yes	No	Yes
SRD entitlement definition	Yes	No	No
People entitlement	Yes	No	Yes
People entitlement groups	Yes	No	Yes
ENT People entitlement groups	Yes	No	Yes
Questions from the Questions Library	No	No	Yes
SRD levels	Yes	No	Yes
SRD packages	Yes	No	Yes
Access permission groups	Yes	No	Yes

To migrate services to BMC Helix Digital Workplace Catalog by leveraging the utility

BMC provides a utility to migrate service request definitions (SRDs) from BMC Service Request Management to BMC Helix Digital Workplace Catalog . With this utility, BMC Service Request Management customers can seamlessly migrate the SRDs along with the Process Definition Templates (PDTs) and Application Object Templates (AOTs). The migration utility provides additional parity for the migrated services than the conventional import functionality in BMC Helix Digital Workplace Catalog. For more information, see Migration of services from BMC Service Request Management by leveraging the utility.

The utility supports BMC Service Request Management and BMC Helix Digital Workplace Catalog versions 23.3.02 and later.

Migrating BMC Service Request Management objects and data

Comparison of the migration methods

Objects and data that are migrated

To migrate services to BMC Helix Digital Workplace Catalog by leveraging the utility

On this page