This documentation supports the 22.1 version of BMC Service Request Management.

To view an earlier version, select the version from the Product version menu.

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:

  1. 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)
  2.  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 Open link .

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 importChecks BMC Service Request Management foundation data IDs on importDoes 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:

SRDs

PDTs

Supporting data

SRDsYesNoNo
ActionsYesNoNo
Questions related to an SRDYesNoNo
Question to SR Field mappingsYesNoNo
Question to Variable mappingsYesNoNo
PDTsYesYesNo
VariablesYesYesNo
SRD and PDT Work InfoNoNoNo
Application template bridgeYesYesNo
Application target dataNoNoNo
Change templatesYesYesNo
Incident templatesYesYesNo
Work order templatesYesYesNo
Survey questionsYesNoYes
ImagesYesNoYes
Navigational categoriesYesNoYes
SRD entitlement definitionYesNoNo
People entitlementYesNoYes
People entitlement groupsYesNoYes
ENT People entitlement groupsYesNoYes
Questions from the Questions LibraryNoNoYes
SRD levels

Yes

NoYes
SRD packages

Yes

NoYes
Access permission groupsYesNoYes
Was this page helpful? Yes No Submitting... Thank you

Comments