Migrating BMC Service Request Management objects and data
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:
| Provides the following options when staging data:
| Provides the following options when staging data:
|
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. SeeLoading 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 |
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: | ||
---|---|---|---|
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 |