Question
IN
Posted: Jul 30, 2025
Last activity: Jul 31, 2025
Last activity: 31 Jul 2025 19:05 EDT
Pega upgrade from 7.2 to infinity 24.2
We are planning for Pega upgrade from Version 7.2 to infinity 24 and migration from On-Premise to Pega Cloud 3
Is it possible to upgrade directly from Version 7.2 to infinity 24 with (UI Kit 15.1) or need we need to go for multi-hop upgrade
Posted: 6 months ago
Updated: 6 months ago
Updated: 31 Jul 2025 19:08 EDT
ai4process ltd
ai4process ltd
GB
Posted: 6 months ago
ai4process ltd
ai4process ltd
GB
Upgrading your platform version is separate from moving to Cloud 3.
-
Containerize your application
-
Validate infrastructure-specific integrations Authentication, Authorization, databases etc
-
Use Deployment Manager or CI/CD pipelines to automate deployments.
-
Test network configurations in a staging Cloud 3 environment.
@BoggarapuR17533647
Yes, it is technically possible to upgrade directly from Pega 7.2 to Infinity 24.2, but only if certain preconditions are met. Otherwise, a multi-hop upgrade provides a safer, more manageable path.
Direct Upgrade Path
Use this when your application is already modern and guardrail-compliant:
Perform an Impact Analysis to identify deprecated rules, custom UI Kit versions (<10), or legacy section formats.
Clean up or refactor any noncompliant rules (old-style sections, outdated harnesses).
Upgrade your application’s UI to UI Kit 15.1 before or during the upgrade.
Execute the in-place upgrade using Infinity 24.2 upgrade utilities.
Run Regression Suites and Performance Tests in a sandbox before production.
Have a lightweight application with minimal technical debt.
Can dedicate time upfront for code cleanup and refactoring.
Recommended Multi-Hop Upgrade Path
This approach helps you catch and resolve issues incrementally:
7.2 → 8.6 or 8.8
Leverage the upgrade tools in 8.x (Upgrade Advisor, Rule Inspector).
Migrate to UI Kit 10+ if you haven’t already.
Code Cleanup & Refactoring
@BoggarapuR17533647
Yes, it is technically possible to upgrade directly from Pega 7.2 to Infinity 24.2, but only if certain preconditions are met. Otherwise, a multi-hop upgrade provides a safer, more manageable path.
Direct Upgrade Path
Use this when your application is already modern and guardrail-compliant:
Perform an Impact Analysis to identify deprecated rules, custom UI Kit versions (<10), or legacy section formats.
Clean up or refactor any noncompliant rules (old-style sections, outdated harnesses).
Upgrade your application’s UI to UI Kit 15.1 before or during the upgrade.
Execute the in-place upgrade using Infinity 24.2 upgrade utilities.
Run Regression Suites and Performance Tests in a sandbox before production.
Have a lightweight application with minimal technical debt.
Can dedicate time upfront for code cleanup and refactoring.
Recommended Multi-Hop Upgrade Path
This approach helps you catch and resolve issues incrementally:
7.2 → 8.6 or 8.8
Leverage the upgrade tools in 8.x (Upgrade Advisor, Rule Inspector).
Migrate to UI Kit 10+ if you haven’t already.
Code Cleanup & Refactoring
Deprecate old UI components and harnesses.
Align custom rules to best practices and guardrails.
8.6/8.8 → Infinity 24.2
Upgrade to UI Kit 15.1 (or move to Constellation).
Reapply any final customizations and run end-to-end tests.
Download and run the Upgrade Advisor for both 7.2→8.x and 8.x→24.2.and prepare a sandbox POC for your path. Also make sure that you draft a rollback plan and test suite for each phase.