Drezen Technology

Cascade Regional Bank

Migrating a regional bank to AWS without a maintenance window

43 workloads moved from two ageing data centres to AWS in eleven months, with a governed landing zone and a 34% run-rate reduction.
Fintech & Financial Services11 months11 people2024

Results

Unplanned outages during migration
0Unplanned outages during migration
Infrastructure run-rate reduction
34%Infrastructure run-rate reduction
Environment provisioning time
11 days → 40 minEnvironment provisioning time

The challenge

A regional bank was running 43 workloads across two data centres, one of which had a lease expiring in fourteen months and hardware already past end of support. Regulatory expectations around operational resilience meant a rushed migration was not an option, and the internal team had no prior cloud delivery experience at this scale.

The existing environment had accumulated a decade of undocumented configuration. Provisioning a new test environment took eleven days and a series of tickets, which meant that testing anything substantial was rare enough to be an event.

What we did

  1. 01

    Assessment with a costed disposition per workload

    Every workload was inventoried with its dependencies and assigned a disposition across rehost, replatform, refactor, repurchase and retire — with nine systems identified for retirement outright, which removed roughly 20% of the migration scope before it started.

  2. 02

    Regulator-aware landing zone first

    Account structure, network segmentation, identity boundaries, encryption policy, logging and evidence generation were built as code and reviewed with internal audit and the bank's regulator before any workload moved.

  3. 03

    Migration in dependency-ordered waves

    Seven waves, each with a rehearsed cutover, a tested rollback path and agreed validation criteria. Data replication ran continuously so cutover windows were minutes rather than hours.

  4. 04

    Capability transfer as a deliverable

    Two bank engineers were embedded in the delivery team throughout, with pairing and formal handover sessions. By wave five they were leading cutovers with us reviewing rather than executing.

  5. 05

    FinOps from wave one

    Right-sizing against observed utilisation, savings plan commitments purchased on evidence, storage lifecycle policies and scheduled shutdown of non-production environments outside working hours.

The outcome

All 43 workloads migrated across eleven months with no unplanned outages and no cutover requiring rollback. The expiring data centre was exited two months ahead of the lease deadline.

Infrastructure run rate fell 34% against the pre-migration baseline once optimisation completed. Environment provisioning dropped from eleven days to forty minutes, which changed the bank's testing practice more than any single technical improvement — full-scale testing moved from quarterly to per-release.

Services

How we did it

All services

Cloud Consulting & Migration

AWS, Azure and GCP migrations that land on budget and stay there.

Learn more

Legacy System Modernization

Replace the engine without stopping the car.

Learn more

Site Reliability Engineering (SRE)

SLOs, observability and incident practice that make uptime predictable.

Learn more

More

Other case studies

View all
Fintech & Financial Services9 months

Rebuilding a lending origination platform around an event-sourced ledger

An event-sourced origination platform replacing a spreadsheet-and-email process, with decisioning, audit trail and reconciliation built in.

Median time to credit decision
4.2 days → 6 hrsMedian time to credit decision
Applications processed per underwriter
3.1xApplications processed per underwriter
Decisions reconstructable for audit
100%Decisions reconstructable for audit
Read the case study
Logistics & Supply Chain7 months

A supply chain control tower that surfaces exceptions before they land

A real-time visibility platform unifying 19 carrier feeds, with predictive ETAs and exception routing that reaches an operator while options still exist.

Reduction in late-delivery penalties
61%Reduction in late-delivery penalties
Systems an operator monitors
19 → 1Systems an operator monitors
Average earlier exception detection
4.5 hrsAverage earlier exception detection
Read the case study
SaaS & Technology6 months

Scaling a B2B SaaS platform through 8x growth without a rewrite

Targeted performance and isolation work absorbed 8x tenant growth, cut p95 latency 78%, and took deployment from fortnightly to daily.

Reduction in p95 API latency
78%Reduction in p95 API latency
Deployment frequency
14 days → 1 dayDeployment frequency
Tenant growth absorbed
8xTenant growth absorbed
Read the case study

Tell us what you are trying to build

A 30-minute call is usually enough for both of us to know whether this is a fit. If it is not, we will point you somewhere better.

sales@drezentechnology.comUsually replies within one business day