Zero unplanned
downtime.
One regulatory deadline.

The Problem

The bank — serving roughly [VERIFY: 180,000 retail customers] across Kosova, Albania, and North Macedonia — had grown on a core banking platform installed in the mid-2000s. The platform still functioned but had reached end-of-support on the vendor roadmap, leaving the bank without security updates or compliance patches for newer regulations.

The central bank's operational-resilience framework set a hard deadline: operators on end-of-support critical systems would face sanctions after a specific date. The bank's board approved the replacement programme with two non-negotiable constraints: zero unplanned downtime during business hours, and regulatory-audit passing on the first attempt.

Previous attempts by a global systems integrator had stalled at the assessment phase — the risk of disruption across three countries, with different regulatory regimes and different operational practices in each subsidiary, was judged too high against the deadline available.

Why Virtual Era

The bank approached Virtual Era for three reasons: deep regional knowledge of banking in all four target countries, a fixed-outcome commercial model that priced the delivery risk into the contract rather than the backlog, and a delivery team that had successfully replaced core systems at two other regional banks within comparable constraints.

After a four-week assessment, we proposed a phased migration architecture — replacing the platform in one subsidiary at a time, running old and new in parallel for a four-week hypercare period after each phase, and using the learnings from phase one to compress phase-two and phase-three execution. The steering committee, including the central bank observer, approved the approach.

The Approach

Phase one covered the Kosova subsidiary — the bank's largest and most operationally complex. Twelve months of assessment, design, build, data migration, and cutover. The cutover itself took place over a single weekend, with an L1/L2/L3 war-room structure on standby and rollback procedures pre-rehearsed three times.

Phase two covered Albania. Six months — the compressed timeline possible because the platform configuration, data-migration tools, and cutover runbooks developed for phase one were largely reusable. The regulatory overlay was different, but the technology execution was faster.

Phase three covered North Macedonia. Four months. At that point the programme had momentum: both the bank's operational staff and Virtual Era's engineering team had rehearsed the cutover pattern twice. The third cutover executed without significant incident.

Throughout all three phases, the programme maintained a single steering committee chaired by the bank's COO and attended by the central-bank observer. Monthly reporting was structured around the operational-resilience framework the regulator would eventually audit against.

The Outcome

The core banking replacement went live across all three countries within 18 months. Zero unplanned downtime during any business hours. Regulatory audit passed on first submission, with the regulator citing the programme's structured risk management as exemplary.

Post-launch, the bank measured a 38% reduction in transaction cost per account — driven by the new platform's lower licence cost, its cloud-native architecture allowing elastic capacity, and the removal of several middleware components the old platform had required.

The programme has since been used as a reference architecture by the central bank when advising other tier-2 operators on resilience modernisation. The bank's CIO was promoted to a group-level role on the strength of the programme delivery.