Skip to main content

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

Migrating a new application to a different environment

Updated on August 3, 2022

During a normal development and implementation process, you build and test new application features in a dedicated development environment. After testing, you migrate the application to a different environment, for example, the business-as-usual staging server.

Pega Customer Decision Hub Implementation Guide

Packaging and importing a new implementation application

When first migrating a new application to a different environment, you must manually package and import it. For more information, see Packaging an application.

Making further updates to your implementation application

To deploy further changes to your production environment, for example, after developing new features for your implementation application, we recommend using Deployment Manager pipelines to automate the migration process for Pega Customer Decision Hub. Your Deployment Manager version must be 4.8 or later. For more information about Deployment Manager, see Understanding model-driven DevOps with Deployment Manager.

If you do not use Deployment Manager, you can also continue to manually package your application and import it into different environments.

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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us