HealthOmics migration

AWS closed HealthOmics to new customers at the end of 2025, and many existing users are skeptical about the long-term support prognosis.

Take ownership of your data layer with Phoebe

Phoebe replaces the variant store, cohort query layer, and annotation management that HealthOmics analytics provides. Cohort search, variant lookup, sample-level filtering, and annotation-driven reanalysis all map directly onto Phoebe's core functionality. Because Phoebe is built on open standards and deployed on your own infrastructure, you aren't just swapping one managed service for another. You are future-proofing your data layer and eliminating vendor lock-in so your team never has to execute a forced migration again.

What Phoebe does not replace

Phoebe does not replace clinical interpretation tools, pipeline orchestration (such as HealthOmics Workflows), or raw sequencing-data storage. Those layers remain wherever they are today; Phoebe sits at the variant warehouse layer.

Typical migration / deployment

The ease and speed of moving VCF and annotation data into and out of Phoebe means the simplest migration is likely bulk ingest from VCFs rather than exporting from the HealthOmics variant store to an intermediate set of files. However, this is an option if VCFs are no longer available or if the variant warehouse has accumulated new information separate from VCFs and annotations. After import, existing cohort queries are then recoded against Phoebe's SQL or Python interfaces, validated against historical results, and brought into production. This work is done collaboratively between the Phoebe migration team and customer data engineers.