Case study / Client engagement, anonymized
Moved a 200-user editorial platform to AWS with zero disruption
A media division ran its editorial system on aging on-premise infrastructure with rising cost and risk, and a newsroom that could not stop publishing while it moved.
In production- 200+ users, zero disruption
- 2x capacity
- Parent org followed
The engagement
Challenge
Move the newsroom's core system without it noticing
The editorial platform ran on aging on-premise infrastructure with rising cost and risk. The catch: the newsroom could not stop publishing for 200-plus editorial and production users while the platform moved underneath them.
Action
Migrate live, as technical lead and PM
I led the migration of the editorial platform to AWS-hosted infrastructure as both technical lead and project manager, sequencing the cutover around live operations so that editing and production never stopped, and keeping the preflight pipelines and Mac fleet management continuous through the transition.
Result
Zero disruption, double the capacity, and a follow-on
The cutover happened without the newsroom noticing, and capacity doubled. It was credible enough that the parent organization migrated its own editorial system onto the same platform immediately after. In the deep detail: operating cost roughly halved.
How it is built
A cutover the newsroom never felt
The number that matters is the zero: zero disruption to a newsroom that could not stop.
- 01Live migration. Sequenced the platform cutover around active editorial and production work for 200-plus users.
- 02Capacity. The AWS-hosted platform doubled user capacity relative to the on-premise system it replaced.
- 03Continuity. Preflight pipelines and Mac fleet management stayed continuous through the transition.
- 04Cost. Operating cost was roughly halved, a deep-detail outcome, not the headline.
- 05Follow-on. The parent organization migrated its own editorial system onto the same platform right after cutover.
What it proves
Migrating a newsroom's core system without it noticing is the job. Zero disruption is the number that matters, not the dollar figure.
See the rest of the work →Client and infrastructure details are anonymized. No client names or resource identifiers are shown; dollar figures live in the resume, not the headline.