This documentation supports the 9.1 version of Service Request Management.

To view the latest version, select the version from the Product version menu.

Migrating BMC Service Request Management objects and data

This topic contains important information about migrating BMC Service Request Management objects and data. The following information is provided:

Overview of the migration process

Migration is the process of exporting objects and data from one server (the source server) and importing them to another server (the destination 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) and custom workflow
    • Configuration data for BMC Service Request Management, such as application target data, service targets, On Behalf Of management, and task templates (Note that 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 methods to migrate the BMC Service Request Management objects and data:

Comparison of migration methods

The following table provides a quick comparison of each migration method.

BMC Remedy 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 (skip duplicates)
  • Import new definitions only (cancel import if existing definitions found)
  • Import all definitions as new (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 (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 BMC Remedy Deployment Application console

Import and export from the Import Export Console in BMC Service Request Management

Export from the Import Export Console in BMC Service Request Management, and import from the Job Console in Data Management

Import BMC Service Request Management data , data from BMC Remedy ITSM applications, and other BMC Remedy AR Systems objects and data

Import only BMC Service Request Management data

Import Foundation data and data from BMC Remedy ITSM applications

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.

 Migrated with:

Type of object or data

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

Related topic

Preparing the server for import

Was this page helpful? Yes No Submitting... Thank you

Comments