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.
Note: The Product Migration wizard and product migration command-line tool
are deprecated. Pega recommends using Deployment Manager to move an
application between systems. For more information, see Best practices for application configuration
. You can also use the prpcServiceUtils
tool. For more information, see Distributing an application from command line.
| Task | Tool | Interactive | Command line | Export | Import | Migrate |
|---|---|---|---|---|---|---|
| As a best practice, use Deployment Manager to promote an application from one system to another. | Getting started with Deployment Manager | |||||
| Create a product Rule that can be used for exporting or migrating an application. | Application Packaging wizard | X | ||||
| Export an application, a Ruleset, a product, or a patch to a file system or repository. | Export gadget | X | X | |||
| Create or modify a product Rule and optionally download an export file to your local file system. | Product Rule form | X | X | |||
| Import Rules and data from a file system or repository to your system. | Import wizard | X | X | |||
| 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 tool | X | X | X | ||
| 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 tool | X | X | X |