Skip to main content

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

Modernization Journey

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:
This documentation is no longer being maintained. It is out of date and pending deletion. Please update your bookmarks.

The Modernization Journey consists of four phases: Assess, Update, Implement, and Evolve. These classify the activities required when modernizing a Pega application.  Migrating to Pega Cloud is a subset of the modernization journey, which will extend beyond migrating to Pega Cloud.  When assessing the changes required for modernization, categorize the work into one of the phases to ensure alignment when planning your migration to Pega Cloud.  When migrating to Pega Cloud, focus on completing the first three phases (Assess, Update, and Implement) to ensure the initial release on Pega Cloud is stable, secure, and performant.

As you progress through the Assess phase, identify gaps, remediations, functionality changes and areas for improvement.  Classify the findings and required actions into the following phases to align with the modernization journey.

Update: Fix what is needed to ensure the applications operate on Pega Cloud and the target Pega Infinity version. Some of the tasks may be done on the current system for early benefit.

Implement: Improve application stability, integrity, security, and performance. Adopt best practices and leverage new features to promote and enable modernization of the application. Perform any required actions to ensure the initial release on Pega Cloud is stable, secure, and performant.

Evolve: Fully modernize the applications – innovate and drive competitive advantage. Address all pending gaps preventing the application from reaching a modern state and effectively leveraging the latest features. There is no need to urgently address this prior to go-live of the application, but it is important to continuously work on this backlog as part of your normal business.  Make it 10% - 20% of the development effort.

Modernization Journey

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