This approach describes a parallel development strategy for migrating a Pega application from on‑prem to Pega Cloud while allowing BAU development to continue uninterrupted. A controlled code freeze is used only to establish a stable baseline, followed by a major ruleset version skim to create a clean cloud baseline. The application is then cleaned up and migrated to Pega Cloud DEV, where cloud‑specific remediation is performed in incremental ruleset versions. Meanwhile, BAU fixes and enhancements continue independently on‑prem in higher patch versions.
Once cloud remediation stabilizes, BAU changes are manually retrofitted into the cloud ruleset and conflicts are resolved before promotion to higher environments. A key advantage of this model is that it does not impact delivery timelines of BAU functionality. This keeps migration risk low while avoiding prolonged BAU freezes or duplicate testing cycles.
Please share your thoughts !