Industry: Banking and Financial Services
Region: Global (60 markets)
Business Driver: Data center growth from legacy and active Pega systems, business transformation, and long-term regulatory retention obligations
Overview
The bank ran multiple versions of Pega Platform to power AI-driven decisioning and workflow automation across its operations. Over years of growth, retired and active Pega applications ran side by side, each adding case data, attachments and audit history to an expanding data center footprint.
As part of a wider modernization program, the bank decided to shut down its legacy Pega systems and move inactive data out of the ones still in use. Regulators across its markets still required that historical case records stay retained, retrievable and defensible, so deleting the data was never an option.
Challenges
- Multiple Pega versions held case data in different schemas and data models, so no single extraction approach worked across the estate.
- Legacy Pega applications had to stay licensed, patched and hosted only to keep historical records reachable for audits.
- Active Pega systems carried years of closed cases alongside live work, inflating database size, backup windows, and infrastructure costs.
- Case data was spread across work objects, case history, attachments, correspondence, and BLOB-stored properties, making it hard to preserve the full context of a case outside Pega.
- Retention requirements varied by market and case type, and they were enforced inside individual applications rather than through one policy layer.
- Legal holds had to be applied to specific records without blocking the decommissioning timeline.
Business Requirements
- Extract data and metadata from every Pega version in scope, including legacy and active systems.
- Archive inactive cases from active Pega systems without disrupting live workflows.
- Preserve case hierarchy, attachments, correspondence and audit trails with referential integrity intact.
- Apply retention schedules by case type and jurisdiction outside the Pega application layer.
- Support legal holds and controlled purge once retention periods expire.
- Give business, audit and compliance users secure, searchable access to archived records after decommissioning.
Solution
The bank partnered with Archon and used its in-house Pega archiving capability to move historical data into Archon Data Store, a single governed archive for both decommissioned and active Pega systems.
- Extracted data and metadata from multiple Pega versions, normalizing differing schemas into one consistent archive structure.
- Fully decommissioned legacy Pega applications after archived records were validated against source.
- Offloaded inactive cases from active Pega systems in controlled, incremental batches, so live operations continued without disruption.
- Preserved case hierarchy, lifecycle state, attachments, correspondence, and audit history so each case could be viewed in its original context.
- Configured retention policies by case type and jurisdiction, applied from one policy layer independent of Pega.
- Enabled legal holds at record level, with purge running only after retention expiry and the absence of active holds.
- Stored archived data in immutable storage with audit logs capturing every user access and policy action.
- Delivered role-based search and retrieval, so users can find and view archived case records after the source Pega system is switched off.
Business Outcomes
Legacy Pega Retired: Multiple legacy Pega applications fully decommissioned, with no remaining dependency on the source systems
Leaner Active Pega: Inactive case data offloaded from active Pega systems, reducing production database load without disrupting live workflows
Lower Infrastructure Costs: Reduced data centre storage, licensing and maintenance spend across retired and active Pega environments
Single Enterprise Archive: Data and metadata from multiple Pega versions consolidated into one governed archive in Archon Data Store
Policy-Driven Compliance: Retention, legal hold and purge applied consistently to archived records across all 60 markets
Retire Pega Without Losing a Single Case Record
With Archon Data Store, the bank replaced a sprawl of legacy and overloaded Pega systems with one archive that holds case data, metadata and audit history under consistent retention, hold and purge controls. Active Pega systems now run leaner, retired applications no longer need to be maintained, and compliance teams can still produce any historical record on demand.
If you are planning to retire your legacy Pega estate for AI-driven decisions, this is the right opportunity. Let’s plan your Pega decommission →