Modernization roadmap with the Application Signature Tool

The ideal Heritage Modernization Application Profile looks like the following process: 

• Pega Platform/upgrade history: Originally built on Pega Platform version 7.1.5 or later and tolerance upgraded to more recent releases (no feature adoption). 
• Business agility needs: Slow time to market, difficulty with regulatory updates, siloed applications, and inconsistent user experience. 
• Operational stability requirements: Performance bottlenecks and outages that harm user productivity and customer experience.
• Low guardrail quality: Sub-par guardrail compliance score with technical debt, customizations, and deviation from Pega best practices.
• Lack of modern Pega Platform capabilities: Minimal App Studio/Case Designer usage, no Live Data, limited AI/Decisioning, UI Kit only (no Constellation). 

The following steps are ideal for a phased modernization rollout using the Application Signature Tool: 

1. Use the Application Signature Tool to accelerate modernization by generating an Application Signature File of the old Pega application. This file is a complete inventory of the Case Types, Data Models, workflows, Personas, Rules, and integrations in the older application. 
2. Load the file into Pega Blueprint, where AI reimagines the application using modern design principles, optimized Case structures, Data Objects, business rules, and other Constellation components that you want to import into Pega Infinity™.
3. Note that modernization can occur a Case at a time, and follow an incremental approach using Blended UI to run heritage traditional architecture and modern constellation architecture side by side. This approach enables phased rollouts, focusing on your high-priority Cases first. This reduces risk, supports continuous feedback, and delivers value throughout the journey, rather than waiting for a full rebuild. 

The following video illustrates iterative case creation combined with a dynamic, blended user interface for maximum efficiency:

Choosing the right approach is critical to the success of the modernization journey. Learn which of the following approaches fits best:  

Application Signature Tool 

• Automates the discovery of heritage Pega applications.  
• Avoids weeks and months of manual analysis.
• Produces consistent Pega Blueprint baselines to accelerate modernization. 
• Ideal for heritage app discovery, complex, or poorly documented applications.  
• Best suited for old or unclearly documented apps.
• Extracts metadata into a .pegasign file for Blueprint ingestion.
• Supports demo creation by establishing realistic baselines for client discussions
• Available on Pega Marketplace for download from January 2026.    

Constellation Modernization Assistant (CMA) 

• Helps migrate existing apps to the Constellation architecture for modern UI/UX. 
• Modernization of the front-end experience without a full application redesign. 
• Ideal when the app is already relatively modern and follows guardrails. 
• Includes analysis (used to assess scope) and migration capabilities. 

Pega Blueprint export option

• The Application Signature Tool captures older apps without Case Types; the Blueprints that it exports target modern Pega applications.
• Introduced in Pega Platform release 23.1.5; updated with each release.
• Best for starting new apps based on existing ones, to enable reuse and collaboration.
• Ideal for quickly deploying a reusable Case Type across multiple departments.
• Exports start from the Application Rule and require Case Types, Data Objects, and relevant records.
• Builds a lifecycle from design-time data that includes Cases, Stages, processes, Steps, and Views.