Skip to main content


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

Migrating robotic automation packages between environments 8.4.1

Updated on February 3, 2020

Easily migrate robotic automation packages between environment by using the Import Wizard and the activities provided with Pega Robotic Automation Importer and with Pega Robot Manager.

For more information about the flow of robotic automation packages during deployment and migration, see Robotic automation package deployment and migration - overview.

Before you begin

  • Ensure that you have access to the source and target repositories
  • Ensure that you have the privileges required to import packages into the production Pega Robotic Automation Importer and Pega Robot Manager environment.
  • If you are using separate Pega Package Servers in the target and source environments: Copy the automation package binaries from one Package Server to another and retain the original directory structure. For more information, see Back up configuration files and packages in the Pega Package Server and Server Status Page User Guide on Pega Community.
    1. Export the automation package component from the source environment repository.
    2. Save the automation package component from the repository to your local drive.

    Result: The robotic automation package is now migrated from the source environment to the target environment. Depending on your choices, you migrated either all versions of the automation package (default behavior) or only some specific version(s).

    • Previous topic Robotic automation package deployment and migration between environments 8.4.1
    • Next topic Importing robotic automation package components to Pega Robotic Automation Importer 8.4.1

    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