Skip to main content

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

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Understanding application migration scenarios

Updated on April 5, 2022

The Standard Release migration process supports the following scenarios:

  • All developers in the organization use a single shared development environment (recommended by Pegasystems).
  • The organization follows a distributed development model, where individual developers or development teams have their own isolated development environments.

The release process works for either development scenario, because it begins after changes have been merged into the appropriate ruleset versions. Regardless of development scenario or team size, development teams must use branching and merging for releasing applications. Otherwise, you cannot take full advantage of the tools and capabilities of the Pega Platform. For more information, see Understanding application migration scenarios.

  • Previous topic Understanding application migration requirements
  • Next topic Deploying application changes to your staging or production environment

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