This documentation applies to the 8.1 version of Remedy Action Request System, which is in "End of Version Support."

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

Migrating data

You can migrate data entries associated with a form from one server to another, between a server and a file, or between files. For example, you can migrate data entries from a production server to a development server for testing newly designed applications with actual data. Or, you can migrate data from one file to another. Data is migrated individually or in a batch.

Note

If you stop and then restart a migration in progress, BMC Remedy Migrator restarts the migration from the entry that was last migrated successfully.

By default, BMC Remedy Migrator uses the field IDs to map field values between the two forms you select. You can migrate four types of data:

  • Individual entries
  • All entries
  • Searched entries
  • "X" number of entries

Note

Data Migration options are not available for Display Only forms.

Migrating ITSM, SLA, and CMDB data

BMC Remedy Migrator does not take the place of the current ITSM/SLA/CMDB installation processes, because it cannot execute the meta workflow used to generate workflow required by the client. BMC Remedy Migrator allows you to safely move generated workflow from the system on which it was created to a production system without taking the meta workflow with it.

Note

All users must have administrator privileges to use BMC Remedy Migrator. When migrating ITSM/SLA/CMDB application-related data, you must first verify that they are a member of the required group or groups, in order for the data to be migrated correctly.

This section contains information about:

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Comments