Migrating off a hyperscaler without the bill shock

Most healthcare organisations do not leave a hyperscaler because of a single failure. They leave because the costs became unforecastable, the residency rules tightened, and the day to day burden never eased. This playbook lays out how to move deliberately, protect clinical continuity, and land on economics you can actually defend.

Start with the bill, not the architecture

Before touching infrastructure, map where the money actually goes. In imaging heavy estates, egress and retrieval charges often dwarf compute. Document the metered lines that move unpredictably, because these are the ones a capitalised, no egress model will neutralise. This map becomes the business case.

Establish the sovereign target

Define the destination in terms of the six layers of sovereignty, not just residency. Decide which regions you need, what your jurisdictional requirements are, and what your recovery posture must look like. With 3verest this is a concierge exercise: we design the target region by region with your team rather than handing you a console.

Migrate region by region, with zero downtime

Clinical systems cannot pause. The proven approach is a staged, region by region cutover with replication running in parallel until each workload is validated in its new sovereign home. PACS and VNA estates move first behind the scenes; users only notice faster retrievals, not a migration.

Prove it, then decommission

Validate performance, residency and recovery in the new environment before anything is switched off. Run a disaster recovery test. Capture the evidence pack your auditors will want. Only then decommission the old footprint, so there is never a moment without a safety net.

The outcome

Done well, a migration like this turns an unpredictable operating line into a balance sheet asset, returns IT capacity to your own team, and leaves every study resident in its jurisdiction. The goal is not just a cheaper cloud. It is a cloud you can forecast, trust and answer for.