Migrating rules and data

You follow similar steps for migration regardless of the tool you use. These common steps are listed below.

  1. Compare the source and target systems.

    1. Confirm that you have a working Operator ID with a PegaRULES:SysAdm4 access role on both the source system and target system.
    2. Confirm that the Pega Platform version number of the target system is not earlier than the version number of the source system. For example, do not attempt to move a ruleset that was created in version 05-01-06 into a system that is based on version 04-02-01.
    3. Review the ruleset version rules to be included. Note the prerequisite rulesets and versions they reference. If you move more than one ruleset, note whether and how they are interdependent.
  2. Prepare the target system for migration.

    1. On the target system, access the Records Explorer and confirm that the target system includes all the prerequisite rulesets and versions.
    2. On the source system, create a product rule or product patch rule.
    3. On the source system, examine the checked-out rules display. Confirm that none of the rules to be migrated are checked out by clicking Designer Studio >Application > Development > Checked Out Rules .
    4. On the source system, click Designer Studio > Process and Rules > Tools > Find Rules and use the Find by Ruleset, Version, Rule Type report to estimate a count of rules to be included in the .zip archive.
      Note: Although the reports display up to 10,000 rules, the .zip archive might contain more than 10,000 instances.
    5. Create a restore point on the target system so that you can roll back the import if there is an error.
  3. Export from the source system and import to the target system.

    The links below describe how to export and import interactively, but you can use any tool.
    1. Export the .zip archive.
    2. On the target system, import the .zip archive.
    3. Adjust your access group to provide access to the uploaded rulesets and versions.
  4. Review the updated target system.

    1. Log off and then log in again with the updated access group, and then review the uploaded results. If they are satisfactory, lock the imported rulesets and versions. If the results are not satisfactory, and you have created a restore point, you can roll back to the restore point.
    2. Consider whether a new class group and work type structure is appropriate for deployment of the application. See Data Model category — Classes and Properties page.
    3. In a multinode system, recompile the libraries and delete the lookup list cache on each of the other nodes. The lookup list cache (and in some cases the compiled libraries) might be stale on nodes other than the node on which you run the Import wizard.