Retiring a mainframe in slices
A billing mainframe nobody could safely change, replaced one slice at a time while it kept running.
- Client
- Brindley Water
- Sector
- Utilities
- Engagement
- Modernization
- Duration
- 16 months
Why they called us
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.
The problem we were handed
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.
What was actually going wrong
- Lorem ipsum dolor sit amet, consectetur adipiscing elit.
- Sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
- Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris.

How we worked
The sequence we followed, and why each stage had to come before the next.
Map what the system actually does
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
Agree what must not break
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
Move one slice, in production
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
Repeat until the old system is idle
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
Turn it off, with the client's hand on the switch
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
What we built
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
One record of truth per domain
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
A translation layer, not a rewrite
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
Observability from day one
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
Rollback at every step
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.

Reading the diagram
- The source system, left running throughout.
- The translation layer that reads from it.
- The new service, taking one slice of traffic at a time.
- The shared datastore both sides write to during migration.
The system in full
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.

Reading the diagram
- The source system, left running throughout.
- The translation layer that reads from it.
- The new service, taking one slice of traffic at a time.
- The shared datastore both sides write to during migration.
What changed
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.
0
Hours of downtime
Across sixteen months and eleven cutovers.
11
Slices migrated
Each one live in production before the next began.
64%
Lower running cost
Measured twelve months after the mainframe was switched off.
3
Weeks to first slice
Billing enquiries moved first, as the lowest-risk path.
Before and after
Measured on the same terms, twelve months apart.
Billing run
46xfaster
Change lead time
35xfaster
Engineers who can deploy
9xmore
They never asked us to stop billing customers while they worked. That constraint shaped everything, and they took it seriously from the first meeting.
Priya RamanathanDirector of Technology, Brindley WaterOther case studies
Engagements that shared a constraint, a sector, or a way of working.
Have a problem shaped like this one?
Tell us the constraint you are working under. We will tell you how we would approach it.



