Skip to main content


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

Synchronize Parallel Development

Updated on December 12, 2023

+

This content applies to On-premises, Client-managed cloud and Pega Cloud environments

Attention: This documentation has been moved to the new documentation site:
https://docs.pega.com/bundle/migration-modernization/page/pega-cloud-migration-modernization/migrating-pega-cloud-overview.html
This documentation is no longer being maintained. It is out of date and pending deletion. Please update your bookmarks.

Freeze all development on the source production environment before beginning the data migration dry run.

If any rule changes are made on the source environment after the initial application migration, import them into the Pega Cloud Development environment and use Deployment Manager to promote them to the higher environments using the standard DevOps pipeline. For more information about Deployment Manager, see DevOps Process.

Use the standard process of exporting and importing a RAP file to migrate the changes to the development environment on Pega Cloud.

 

  • Previous topic Stage 1: Production Environment: Preparation and Dry Run
  • Next topic Promote Application to Production Environment

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Visit the Support Center

Did you find this content helpful?

Yes
No

Want to help us improve this content?
Suggest an edit

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