Make the decision explicit first
In a legacy core system, functional coverage, data handling, licence terms and change rights are connected. A sound decision frame separates evidence from assumption and shows the implications of continuing, stabilising or replacing the system.
- Which functions are actually usable?
- Where do data and resilience risks sit?
- Who controls enhancements and future changes?
- What dependencies follow from each option?
A case: an e-money institution's core system
The 2021 review found about 60% of the core-system functions usable, a single unprotected instance holding customer and transaction data, and enhancements owned by the licensor. The recommendation was to stabilize, stop extending and replace.
In 2023, €500m in customer assets was migrated under supervision to a certified platform with ISO 27001 certification. Jürgen Röck later led that implementation. This documented path is an example, not a universal recipe or outcome commitment.
From analysis to a decision that holds
The work can be agreed as a one-off technical second opinion or focused external support. It assesses available information within an agreed scope. Implementation remains with the company and its appointed teams.
A considered next step
Clarify the question before choosing the scope.
An initial conversation is for clarifying the issue, the available information and the boundaries. If another format is a better fit, that will be said plainly.