This part tells you how to set up, run, and monitor migration events and assign and maintain versions of migrated objects.

• Migration

• Migration Paths

• Migration Events

• Migration Path Defaults

• Archive Event Maintenance

• Authorizing and Submitting a Migration Event

• Migrations Into, Within, and Out of PAC

• Migrating Predict Objects

• Assigning and Maintaining Object Versions

• Object Version Maintenance

The overall migration steps are:

1. Define the migration event to migrate the application from one status to another along a defined migration path. Identify the activities that must take place during the migration of the objects of an application.

   Note:
   The event that migrates Predict objects must be run before the event that moves/copies the Natural and non-Natural application objects that use them.

2. Build the object list. The object list identifies the objects of an application to be migrated.

   The expand status option may be used to specify the status from which subordinate objects are to be compiled.

3. Validate the object list. PAC checks the list of objects to be migrated.

4. Authorize the event. Permission is given to execute the migration.

5. Submit the event; this activates the job that runs the migration event.

6. Monitor the processing of the migration event. The Audit Report and the Job Information screens show the progress of the migration.

After the migration steps are completed, a version can be assigned to an object to identify and control it in the PAC environment.