Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Moving applications between systems

Updated on July 8, 2022

You can migrate rules and data between instances of Pega Platform by using interactive tools in Dev Studio or by using command-line tools. You can develop rules on one system and deploy them on other systems. As a best practice, use Deployment Manager to promote applications.

Check this list of available tools and supported operations to choose the appropriate tool for your purpose.

TaskToolInteractiveCommand lineExportImportMigrate
As a best practice, use Deployment Manager to promote an application from one system to another.See Getting started with Deployment Manager
Create a product rule that can be used for exporting or migrating an application. Application Packaging wizardX
Migrate a product or an application from a source system to one or more target systems or export to a file system.Product Migration wizardXXX
Export an application, a ruleset, a product, or a patch to a file system or repository.Export gadgetXX
Create or modify a product rule and optionally download an export file to your local file system.Product rule formXX
Create a product rule that can be used for exporting or migrating work items. Package Work wizardX
Import rules and data from a file system or repository to your system.Import wizardXX
Migrate a product or an application from a source system to a target system or export to a file system.Product Migration command-line toolXXX
Use scripting to export rules and data to a file system or repository, or import from a file system or repository by using a web service to connect to an active instance. prpcServiceUtils command-line toolXXX
Use scripting to export rules and data to a file system, or import from a file system by using a direct connection to the database. prpcUtils command-line toolXXX
  • Previous topic On-premises only: Running the static assembler from the command line
  • Next topic IBM Db2 for z/OS: Preparing to import an application with schema changes and a separate DB-Admin-DB-Name

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

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

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us