Migration tools
You can migrate rules and data between instances of Pega Platform by using Deployment Manager (best practice), interactive tools in Dev Studio, or by using command-line tools.
The following table lists the available tools and supported operations to choose the appropriate tool for your purpose.
| Task | Tool | Interactive | Command line | Export | Import | Migrate |
| Promote an application from one system to another. | Deployment Manager. | |||||
| Create a product rule that can be used for exporting or migrating an application. | Application Packaging wizard | X | ||||
| Migrate a product or an application from a source system to one or more target systems or export to a file system. | Product Migration wizard | X | X | 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 | |||
| Create a product rule that can be used for exporting or migrating work items. | Package Work wizard | X | ||||
| Remove resolved work items from your system and optionally save them in an archive file. | Purge/Archive wizards | X | X | |||
| Import rules and data from a file system or repository to your system. | Import wizard | X | X | |||
| Migrate a product or an application from a source system to a target system or export to a file system. | Product Migration command-line tool | X | 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 |
Previous topic Distributing applications between systems Next topic Preparing to package and move applications