Cloud migration for a regional healthcare network
A phased lift-and-modernize migration: containerized workloads, IaC with Terraform, and a zero-trust network layer — completed between patient-care windows.
Where things stood
Cedarline ran twelve clinical and administrative systems on aging on-premise servers — some out of vendor support, all expensive to maintain, and none of them allowed to go down during patient care hours. Previous migration attempts had stalled twice because nobody could guarantee continuity for scheduling and records systems that clinics depend on every minute of the day.
What we did
Mapped every system's dependencies and care-hour usage patterns before touching anything — the migration calendar was built around clinics, not engineers
Containerized workloads and rebuilt infrastructure as Terraform code, so every environment was reproducible and reviewable
Ran old and new environments in parallel with live data replication, cutting over one system at a time inside agreed quiet windows
Layered zero-trust networking and least-privilege access as part of the move — not as a later project
What the numbers say
All twelve systems migrated with zero unplanned downtime
35% lower monthly infrastructure spend after right-sizing and reserved capacity
Recovery time objectives cut from 'best effort' to tested, documented numbers
Security posture passed the network's external audit first time
Built with
- Microsoft Azure
- Kubernetes
- Docker
- Terraform
- GitHub Actions
The migration was the smoothest infrastructure project we've ever run. Twelve systems, zero unplanned downtime, and our monthly cloud bill is a third lower.
Daniel Okafor
CTO, Cedarline Health
Start the conversation
Want a result like Cedarline Health's?
Tell us what's slow, expensive, or broken today — and what the number should look like a year from now.