Case Study: UK Challenger Bank

Migrating a major UK bank to a new Connect architecture

Managed the migration of a UK challenger bank from a legacy Amazon Connect instance to a modernised architecture with automated provisioning, enterprise SSO, and full data streaming. Parallel production instances running during transition with zero customer disruption.

2
Parallel production instances
0
Customer disruption
Full
Data streaming enabled
Subsidiary
Bank instance included

The challenge

Legacy instance, modern requirements

The bank's original Connect instance was manually provisioned without data streaming, automated configuration, or enterprise SSO. Growing operational demands required a modernised architecture without disrupting live customer service.

Zero-downtime migration

Customer-facing telephony could not go offline during migration. The legacy and new instances needed to run in parallel, with traffic gradually shifted as the new architecture was validated.

Subsidiary bank integration

The bank group included a subsidiary brand that needed its own Connect instance within the same AWS account, sharing infrastructure costs while maintaining operational independence.

Enterprise identity modernisation

The migration included moving from manual user management to automated Azure AD SSO with security group-based access. Agent provisioning needed to become self-service through the bank's identity platform.

What we built

A parallel migration architecture with dual production instances, automated provisioning, enterprise SSO, and a subsidiary bank instance, all with zero customer disruption.

01

Parallel production architecture

Two production Connect instances running simultaneously: the original (live traffic) and the new modernised instance (being configured and validated). Both fully operational with independent routing and queue configurations.

02

Modernised infrastructure

The new instance built with automated provisioning, Connect Data Streaming, WFM integration, PinPoint campaigns, and Azure AD SSO. Every capability the legacy instance lacked, deployed from the start.

03

Subsidiary brand instance

A separate Connect instance for the subsidiary bank deployed within the same AWS account. Shared infrastructure costs with isolated routing, queues, and contact flows for the subsidiary's operations.

04

Controlled migration path

Traffic migrated from legacy to new instance in controlled phases. Agents re-pointed to the new instance via Azure AD SSO. Legacy instance maintained as fallback until full cutover validated.

Architecture

AWS services powering the migration and modernised architecture.

Banking Connect migration architecture Dual production Amazon Connect instances run in parallel during the migration: the legacy instance carries live traffic while the modernised instance is built up alongside. Traffic is gradually shifted under controlled phases. A subsidiary brand instance runs in the same AWS account with isolated routing. The modernised stack includes Connect Data Streaming, WFM Integration, Amazon PinPoint, and Azure AD SSO. INSTANCE TOPOLOGY DURING MIGRATION LEGACY CONNECT INSTANCE Original deployment, live traffic . Manual provisioning . No data streaming . Manual user management Maintained as fallback until cutover CONTROLLED MIGRATION MODERN CONNECT INSTANCE Built up alongside, then promoted . Automated provisioning . Full data streaming . Azure AD SSO Live in parallel during transition SUBSIDIARY BRAND INSTANCE Same AWS account, isolated routing . Separate Connect instance . Shared infrastructure costs . Independent contact flows Group subsidiary brand operations MODERNISED STACK ON THE NEW INSTANCE Connect Data Streaming Contact events and agent activity WFM Integration Scheduling and performance management Amazon PinPoint Outbound customer engagement campaigns Azure AD SSO Automated agent provisioning via security groups Zero customer disruption Traffic migrated in controlled phases. Legacy maintained as fallback until full cutover validated. Both production instances live simultaneously. Subsidiary brand operating in the same AWS account.
Contact Centre

Amazon Connect

Dual production instances (legacy + modern) with parallel operation during migration. Subsidiary brand instance in the same account.

Analytics

Connect Data Streaming

Full data pipeline on the new instance capturing contact events, agent activity, and interaction records.

Workforce

WFM Integration

Workforce management data streaming deployed on the modernised instance for scheduling and performance management.

Identity

Azure AD SSO

Automated agent provisioning via security groups, replacing manual user management on the legacy instance.

Planning a Connect migration?

We migrate banks to modern Connect architectures without disrupting live operations.

Book a Discovery Call

View all case studies