Skip to content

Issue 9  ·  01 Sep 2026  ·  4 min read

The migration that went too smoothly

A zero-downtime cut-over, the one check we nearly skipped, and why a boring launch day is the goal.

This month we switched off a twelve-year-old monolith. Nobody noticed, which is exactly what we were paid for — and also what made us nervous.

What we shipped

  • The final reporting service for a clinical analytics client, moving them fully off the old platform.
  • Offline photo sync for a field-service app, so inspection evidence survives a dead zone.
  • A cost dashboard that attributes every model call to the feature that made it.

What broke

Nothing in production. In staging, a timezone assumption in a nightly report shifted totals by one day for anyone east of London. The comparison harness caught it — the unit tests did not.

What we'd do differently

Run the side-by-side comparison on live traffic for longer than feels necessary. Four weeks felt excessive at the start and turned out to be just enough to see month-end figures.

Worth reading

Newsletter

One short email every month

What we shipped, what broke, what we'd do differently. Practical writing from the engineers and product people doing the work. No spam, unsubscribe in one click.