The promise is familiar: replace monolithic legacy systems with agile, cloud-native platforms that reduce operational risk, cut costs and unlock digital service delivery. Pega Systems promotes its low-code workflow and case-management suite as a path to precisely that outcome. Yet for public administrations across Europe, legacy transformation is less a technical checklist and more a political, budgetary and organisational gauntlet. Can Pega's platform meet the real-world demands of government IT modernisation, or does it paper over deeper structural challenges?
Why legacy systems persist in the public sector
Most agencies know their core systems are outdated. COBOL codebases, proprietary client-server stacks and tightly coupled databases underpin citizen services, case management and benefits administration in nearly every jurisdiction. These systems work—technically. They process millions of transactions annually, they're stable, and staff know how to operate them. The problem is maintainability, extensibility and the growing inability to integrate with modern digital front-ends or cross-border interoperability frameworks.
Replacement projects frequently stall. Budget cycles prioritise visible citizen-facing services over back-end infrastructure. Procurement rules favour cautious incremental upgrades. Risk-averse IT departments fear service interruptions. And the skills gap is widening: fewer developers understand legacy languages, while cloud-native talent commands a premium public budgets cannot always meet.
This is where vendors like Pega enter. Rather than wholesale replacement, Pega proposes a layered approach: keep legacy systems running underneath while building a new process orchestration and case management layer on top. The sales pitch is appealing—no "big bang" migration, faster time-to-value, and the ability to surface legacy data through modern APIs and citizen portals.
Pega's approach: orchestration over replacement
Pega's legacy transformation offering centres on three components. First, its low-code platform allows agencies to model workflows visually and deploy them without extensive custom coding. Second, Pega's robotic process automation (RPA) can interact with legacy user interfaces, extracting and feeding data without touching the underlying code. Third, integration connectors bridge legacy databases with modern microservices architectures and cloud environments.
In practice, this means a caseworker in a benefits agency might use a Pega-built interface to initiate a claim, which triggers a series of automated steps: data retrieval from a mainframe, validation against external registers, document generation, and approval routing—all without the user ever seeing the underlying legacy screens. For agencies struggling to modernise citizen-facing citizen portals or implement proactive service delivery, this orchestration layer can unlock progress quickly.
But orchestration is not the same as transformation. Legacy systems remain in place. Technical debt accumulates. And agencies risk creating a new layer of complexity—a "Pega middle tier"—that becomes its own quasi-legacy environment if not actively governed.
Where Pega's model shows promise
Pega's strength lies in rapid prototyping and process optimisation. Agencies that have deployed Pega successfully often cite shorter development cycles, improved transparency in case handling, and the ability to iterate workflows in response to policy changes. The platform's rules engine allows business analysts, not just developers, to configure logic, which can reduce bottlenecks in IT departments stretched thin.
For use cases like case management in social services, permitting workflows in planning departments, or complaint handling in ombudsman offices, Pega's visual modelling and out-of-the-box templates can accelerate deployment. The platform's audit trail and compliance features align well with public sector transparency and accountability requirements.
Moreover, Pega's cloud deployment options—available on AWS, Azure and Google Cloud—offer a path for agencies pursuing cloud migration strategies in line with national digital programmes. In jurisdictions where OZG 2.0 in Germany or the GDS roadmap in the UK mandate digital-first service delivery, Pega's ability to expose legacy data through APIs can be a tactical advantage.
Integration with existing public-sector ecosystems
Public administrations do not operate in isolation. Any transformation platform must integrate with national identity schemes, shared registers, once-only architectures and cross-border services under frameworks like eIDAS. Pega supports standard protocols (REST, SOAP, SAML, OAuth), but integration complexity often depends more on the maturity of the agency's existing middleware and data governance than on the vendor's capabilities.
Agencies working with established public-sector IT providers—Dataport AöR in Germany, BRZ Bundesrechenzentrum in Austria, or Capita Public Sector in the UK—may find that Pega integrations require additional custom connectors, governance oversight and alignment with sovereignty requirements. The platform itself is vendor-agnostic, but the real work lies in orchestrating the surrounding ecosystem.
Where the pitch falls short
Pega's orchestration model does not eliminate technical debt; it defers it. Agencies still face the underlying challenge: legacy systems that are expensive to maintain, difficult to audit and vulnerable to skills attrition. Wrapping them in a modern interface may improve user experience, but it does not resolve the structural fragility of the core infrastructure.
Additionally, Pega's licensing model can be opaque and costly. Public sector buyers accustomed to transparent per-user or per-transaction pricing may find Pega's consumption-based or case-based licensing difficult to forecast, especially as usage scales. Budget overruns during implementation are common, particularly when agencies underestimate the effort required to map legacy workflows into Pega's process modelling paradigm.
Another frequent concern is vendor lock-in. Once an agency has built significant process logic in Pega's proprietary environment, migrating to another platform becomes expensive and risky. While Pega supports standards, its differentiation lies in features—such as its decisioning engine and AI-driven next-best-action recommendations—that are tightly coupled to the platform. Agencies must weigh agility today against flexibility tomorrow.
Cultural and organisational barriers
Technology is rarely the only—or even the primary—obstacle to legacy transformation. Pega's platform can automate workflows, but it cannot resolve organisational silos, unclear accountability, or resistance to process re-engineering. Successful deployments require executive sponsorship, cross-departmental collaboration and a willingness to challenge entrenched ways of working.
Vendors often underplay these realities. Marketing materials emphasise speed and simplicity, but public sector IT leaders report that implementation timelines stretch, requirements evolve, and change management consumes more effort than anticipated. In jurisdictions where civil service unions have input on automation initiatives, or where data protection authorities scrutinise automated decision-making, deployment can face non-technical hurdles that no platform can solve alone.
Alternatives and strategic considerations
Pega is not the only option. Competing low-code platforms—Microsoft Power Platform, ServiceNow, and Appian—offer similar orchestration capabilities, often with tighter integration into existing enterprise stacks. Open-source workflow engines like Camunda provide flexibility without licensing constraints, though they require more in-house development capacity.
For agencies committed to digital sovereignty, the choice of platform is also a strategic question. Pega is a US-based vendor, subject to US legal jurisdiction. While it offers EU-hosted cloud options, agencies in France, Germany and Austria are increasingly favouring European or nationally anchored solutions that align with sovereignty principles. Governikus, Materna, and msg systems have built public-sector platforms that prioritise compliance with national data residency and procurement requirements.
Moreover, the choice between orchestration and true modernisation depends on long-term strategy. If the goal is to maintain legacy systems for another decade, orchestration makes sense. If the goal is genuine IT consolidation and architectural renewal, agencies may need to invest in re-platforming core functions onto modern, modular architectures—a costlier and riskier path, but one that addresses the root causes of technical debt.
What public sector IT leaders should ask
Before committing to Pega—or any legacy transformation vendor—agencies should demand clarity on several fronts. What is the total cost of ownership over five years, including licensing, integration, training and ongoing support? What happens if the vendor is acquired, changes pricing, or discontinues a product line? Can process models be exported and reused on other platforms, or are they locked to Pega's environment?
Equally important: what is the organisation's capacity to absorb change? Does the agency have skilled process analysts, data architects and change managers to support a transformation initiative, or will it rely on external consultancies? Is there political and budgetary commitment to see the project through, or is this another pilot that will languish after initial enthusiasm fades?
Transparency matters. Agencies should insist on reference implementations in comparable jurisdictions, access to user communities, and independent audits of vendor claims. Peer networks—whether through national CIO forums, pan-European digital government initiatives, or industry associations—can provide valuable reality checks on vendor promises.
Conclusion: orchestration as a tactic, not a cure
Pega Systems offers a credible set of tools for public sector agencies navigating the transition from legacy infrastructure to digital service delivery. Its low-code platform can accelerate workflow automation, improve interoperability, and provide a modern user experience on top of outdated systems. For agencies under pressure to deliver visible results quickly—whether to meet Swiss e-government mandates or respond to citizen expectations—Pega's orchestration approach can be a pragmatic short-term tactic.
But orchestration is not transformation. Legacy systems remain. Technical debt persists. And without a broader strategy that addresses governance, skills, budgets and organisational culture, even the best platform will struggle to deliver lasting change. Public sector IT leaders should approach vendor pitches with scepticism, demand evidence over rhetoric, and ensure that any legacy transformation initiative aligns with long-term architectural and sovereignty goals, not just vendor roadmaps.
