Case study · Regional retail bank
Keeping digital banking resilient through a core migration
How Eximus stabilized channels, strengthened recovery readiness, and reduced incidents during a high-stakes core migration.
Result in operation
Zero downtime during migration, 32% fewer incidents, and stronger recovery readiness.
- Client
- Regional retail bank
- Context
- Banking & Finance
- Service
- Backup, DR and Resilience
The case at a glance
01 · Challenge
Maintain channel uptime and cut incidents during a risky core migration.
02 · Intervention
We combined hardening, observability and rehearsed recovery.
03 · Outcome
Zero downtime during migration, 32% fewer incidents, and stronger recovery readiness.
A regional bank was migrating core systems while serving millions of daily users. Incidents were frequent and costly. Eximus hardened critical services, rehearsed recovery, and improved observability to keep channels stable through the migration.
Client and context
The bank operated multiple digital channels while upgrading its core. Reliability and auditability were mandatory.
- Sector: Banking.
- Size: Regional bank with high daily transaction volume.
- Key systems: core banking services, SQL Server, Azure-based monitoring.
Challenge
Maintain channel uptime and cut incidents during a risky core migration.
- Frequent incidents with unclear ownership.
- Limited observability and slow recovery steps.
- Regulatory scrutiny on availability and evidence.
- No room for downtime during cutover windows.
Our approach
We combined hardening, observability and rehearsed recovery.
- Hardened critical services and adjusted configurations.
- Introduced observability for critical flows with actionable alerts.
- Defined failover runbooks and ran DR tests before milestones.
- Set up on-call processes with SLAs and communication templates.
Results
- Zero unplanned downtime during the migration window.
- 32% fewer incidents quarter over quarter.
- Faster incident response with clear owners and playbooks.
- Audit-ready evidence of DR rehearsals and incident handling.
Tech & services used
- Core banking services, SQL Server, Azure monitoring/alerts.
- Services: GeneXus Support, Backup, DR & Resilience.
Lessons learned
- Observability plus clear ownership reduces noise and speeds recovery.
- DR rehearsals before major milestones prevent surprises during cutover.
- Standardized on-call processes improve communication under stress.
Next step
If you are modernizing core systems and must keep channels stable, we can review your current resilience gaps and plan rehearsals. Contact us to discuss the safest path forward.
Continue exploring
More decisions in similar contexts
IT Consulting
Automating SARCADAPTER with SSIS to feed ITSARC WEB
A manual desktop process still prepared the flat files needed by ITSARC WEB and was outside the initial scope.
Outcome
The upstream process was automated and integrated with ITSARC WEB in under three weeks; the historical source reports runs of about five minutes.
Banco de la Provincia de Córdoba
Bantotal development for loan refinancing and consolidation at Bancor
Add development capacity to an ongoing Bantotal implementation to deliver complex requirements for the lending module.
Outcome
The bank's users approved the requirements delivered for the loan refinancing and consolidation module.
ITSARC
Modernizing ITSARC's credit risk platform without disrupting operations
Upgrade under regulatory deadlines without breaking reporting or integrations.
Outcome
Kept reporting and integrations stable while moving the platform to a maintainable, lower-risk architecture.