Skip to main content

Table of Contents

Distributing product rules to multiple systems by using the Product Migration wizard


Only available versions of this content are shown in the dropdown

Use the Product Migration wizard to push your product rule to multiple systems in a single step from the user interface. The wizard simplifies the management of rule assets across Pega Platform systems.

For more complex migrations, see Distributing an application from command line.

The source system and target system must be in the same major Pega Platform version. For example, you cannot migrate if the source is in PRPC 6.x and the target is Pega 8.x.

This wizard creates a work item with the prefix pxMigReq-. To find open and resolved wizard work items, in Dev Studio, select Configure Application Tools All Wizards .


Before using the Product Migration wizard, do the following:

  • In your source system, verify that the PegaDiagnosticUser security role is defined for your Pega Platform server node. Also confirm that an instance of the Data-Admin-System-Security class exists with this security role as the key. The user and password information must match the ones specified by the web server console for this security role. Normally, this security role is configured when you install Pega Platform. For more information, see the Installation Guide for your platform.
  • Verify that the Pega Platform is installed on the target systems.
  • Validate the connections between the source system and target systems.
  • Create a pre-import activity. For more information, see Create a pre-import activity.

Using the Product Migration wizard

For IBM Db2 for z/OS, configure the import properties.

If you are importing an application with schema changes and a separate DB-Admin-DB-Name and you are using IBM Db2 for z/OS, configure the import parameters before you import the application, or the import will fail.

For more information about configuring the import parameters, see IBM Db2 for z/OS: Preparing to import an application with schema changes and a separate DB-Admin-DB-Name. For more information about your application, see your database administrator.
Did you find this content helpful?

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us