Core Banking · Systems Design·12 months·Lead UX Designer

Designing the Transition: Legacy to Modern Core Banking

Led the UX strategy for migrating 3.2 million accounts from a legacy mainframe system to a modern cloud-native core banking platform — without disrupting daily operations.

3.2M

Accounts Migrated

100%

Zero-Downtime Achieved

70%

Training Time Reduced

Strategic Context

Core banking migrations are among the most complex undertakings in financial technology. Every screen, workflow, and data interaction must be redesigned while ensuring that 4,000+ banking staff can operate without disruption. The stakes are absolute — a failed migration can cost hundreds of millions and erode customer trust irreversibly.

The legacy system had been in operation for 22 years. Staff had developed deep muscle memory around its workflows. Any new system that disrupted these patterns would face immediate resistance and operational risk.

We developed a 'progressive familiarity' framework — new interfaces that maintained spatial and workflow patterns from the legacy system while introducing modern capabilities through progressive disclosure.

Migration Phases

01Complete UX audit of 380+ legacy screens

02Workflow taxonomy and dependency mapping

03Parallel interface design — legacy patterns, modern architecture

04Cognitive load testing across 6 role-based user segments

05Shadow deployment with real-time feedback loops

06Full production cutover with zero downtime

Complexity Management

The legacy system contained over 380 unique screen patterns. We consolidated these into 47 adaptive templates using a modular component system. Each template was designed to handle multiple banking operations through configurable parameters, reducing cognitive overhead while preserving operational depth.

380 → 47

Legacy Screens Consolidated

6 weeks → 1.5 weeks

Staff Onboarding Time

< 0.3%

Error Rate Post-Migration

42%

Operational Efficiency Gain

In core banking, the best redesign is one where experienced staff feel like the system evolved rather than replaced.

Reflection

The biggest lesson from this project: migration UX isn't about designing the best possible new system — it's about designing the most navigable bridge between old and new. Every decision had to balance modernization ambitions against operational continuity. The system we delivered wasn't just technically superior — it was adoptable, and in enterprise banking, adoptability is the real measure of success.

Next Case Study

Intelligent Compliance Dashboard