- Organisation
- WellSpan Health
- Predecessor
- Traditional data centres hosting more than 300 applications and 7.5 PB of clinical and non-clinical data
- Destination
- Amazon Web Services
- Workload
- More than 300 applications, 7.5 PB of data and the full Epic electronic medical record environment
- Stage
- Completed cloud migration and data-centre exit
- Retirement status
- WellSpan states it fully moved away from a data-centre-based model; later native-service modernisation remains separate.
- Confidence
- High
- Next trigger
- A second-phase native-service milestone or material change to the Epic/AWS architecture.
Programme context
WellSpan completed a 17-week migration of more than 300 applications and 7.5 PB of data to AWS and fully moved away from a data-centre-based model.
Why this matters: The record identifies a named organisation, an explicit predecessor and destination platform, and a bounded workload and lifecycle stage.
Migration timeline
| Date or stage | Milestone | What changed | Evidence status |
|---|---|---|---|
| January 2026 | Migration milestone | WellSpan announced the comprehensive AWS migration programme. | Dated first-party announcement |
| 17 weeks | Migration milestone | The migration was completed in 17 weeks. | Source-stated duration |
| 22 Jul 2026 | Migration milestone | WellSpan announced successful completion and exit from the data-centre-based model. | Dated completion evidence |
Workload migration matrix
| Workload | Predecessor | Destination | Status by 23 Jul 2026 |
|---|---|---|---|
| More than 300 applications, 7.5 PB of data and the full Epic electronic medical record environment | Traditional data centres hosting more than 300 applications and 7.5 PB of clinical and non-clinical data | Amazon Web Services | Completed cloud migration and data-centre exit |
Implementation and architecture
- The scope includes the full Epic electronic medical record environment.
- Clinical and non-clinical data were included in the 7.5 PB estate.
- A second phase focuses on native AWS services and AI capabilities.
Known unknowns and contradictions
- The exact final cutover timestamp.
- The application-by-application migration inventory.
- The detailed retirement sequence for each physical facility.
No missing fact is inferred to broaden the source-supported migration claim.
PlatformTrace analysis
The completion announcement supports the named migration and data-centre-model exit. A second phase moving further toward native AWS services remains future work.
Performance, cost, uptime and operational outcomes remain attributed source claims unless independently stated otherwise.
Evidence ledger
- WellSpan announcement, 22 July 2026
First-party completion announcement identifying the 17-week duration, 300-plus applications, 7.5 PB, full Epic environment and move away from data centres.
- WellSpan partnership announcement, January 2026
Earlier first-party announcement establishing the original programme scope and target.
Corrections and updates
23 July 2026 — Initial Verified dossier published from the complete five-lane overnight intake and corrected central adjudication. Later milestones will be appended rather than silently replacing this state.