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 data by using the Import Export Console

Deployment managers can use the Import Export console to perform data migration for the following processes:


To export BMC Service Request Management objects and data

Exporting from the Import Export Console

To import Service Request Management objects and data

Importing data from the Import Export Console

For the following data import options:

  • To merge data
  • To cancel the import if duplicates are found
  • To skip the import of duplicate objects
  • To importing all SRDs as New
  • To apply the imported SRDs to a different company
  • To view the history records of your imports and exports
  • To import an exported file available in the history records
Viewing the history of imports and exports

The following video describes the import export process for SRDs.


The video is referring to an older version and you might observe some changes in the procedure.

To migrate data with the Import Export Console

Before you begin, ensure that you have the Request Catalog Manager and AR System Administrator permissions.


The Import Export Console handles only certain kinds of Service Request Management objects and data, as explained in the Objects and data that are migrated section in Migrating BMC Service Request Management objects and data.

If the data migration fails, ensure that the file does not contain any user credentials that do not have the required permission to perform the job. You can comment out the AR_USER and AR_PASS fields in the file before running the job and then uncomment the fields after the job is complete. The file is available on the AR System server installation location. The default location on Windows is: C:\Program Files\BMC Software\ARSystem\diserver\.kettle.

  1. Prepare your destination server.
  2. Export selected service request definitions (SRDs), process definition templates (PDTs), and supporting data from the source server.
    To perform this step, use the Import Export Console, as explained in Exporting SRDs, PDTS, and supporting data. The export process creates a .zip file and attachments folder (containing images).

  3. Import SRDs, PDTs, and supporting data to the destination server.
    Use the .zip file created in Step 2 to perform the steps in the Import Export Console. For more information, see Importing data from the Import Export Console.
Was this page helpful? Yes No Submitting... Thank you