Independent enterprise technology-change research

PT-2026-065 · dossier edition · 20 July 2026

PlatformTrace

Enterprise platform migrations, examined in public.

Public-sector data-platform migration · Production complete · High confidence

Virginia DBHDS completes Snowflake-on-AWS data warehouse programme

Virginia's Department of Behavioral Health and Developmental Services implemented a modern enterprise data warehouse using Snowflake in VITA's AWS environment, moved Community Service Board workloads into production and completed the programme while the predecessor's final decommissioning remains unconfirmed.

Organisation
Virginia DBHDS
Predecessor
VITA-hosted SQL Server EDW
Successor
Snowflake on AWS
Implementation partner
Deloitte
Programme cost
$11.08 million
Production scope
40 Community Service Boards
Retirement status
Not explicitly confirmed
Confidence
High
Evidence boundary: Production cutovers, final release and administrative project completion are established. No reviewed source explicitly confirms final shutdown of the predecessor SQL Server warehouse, so PlatformTrace does not claim decommissioning.

Programme context

DBHDS launched the Enterprise Data Warehouse programme to replace an existing VITA-hosted warehouse maintained by the agency. Official planning material describes the old environment as the existing SQL Server enterprise data warehouse and identifies the new destination as a data platform hosted by VITA in AWS. Technical and governance sources name Snowflake as the analytical core.

Programme objective: consolidate behavioural-health data from Community Service Boards and other systems, improve timeliness, refactor reporting and implement a master patient index capable of recognising one individual across multiple services.

Programme timeline

DateMilestoneMeaningStatus
3 Apr 2023Project startStart recorded in the FY24–26 IT strategic plan.Confirmed
28 Feb 2025Original planned endOriginal planning horizon before later implementation and closeout movement.Superseded plan
Jul 2024Deloitte contract beginsImplementation contract for the replacement data platform.Confirmed
Aug 2024Development environmentsAWS and Snowflake development access was being enabled.Confirmed
Mar–May 2025Production migrationsCSB production readiness and go-lives were active across multiple EHR vendors.Confirmed
Dec 2025Final release implementedThe project team reported delivery of the final release.Confirmed
Feb 2026Planned closeoutAdministrative closeout target after the final release.Planned
May 2026Portfolio marked completeVITA moved the project into its completed-project portfolio.Confirmed

Workload and source-system matrix

ComponentRole in programmeStatusEvidence boundary
Community Service BoardsPrimary production data providers; 40 CSBs in scope.Production migration active in 2025Some boards were at risk of missing individual timelines; final per-board completion is not published.
Multiple EHR vendorsSource-system integrations for CSB data.Go-live handling confirmedPublic material does not list every vendor or final interface state.
Master Patient IndexIdentify a unique individual across services.Programme scope confirmedDetailed matching model and production metrics are not public.
Existing reportsRefactored to use the new EDW.Required scopeComplete inventory and retirement of old reports are not disclosed.
Near-real-time ingestionImprove source-to-warehouse timeliness.Design objectivePer-source latency and production coverage are not published.
CCS3, EDCC/SmartChart, Millennium EHRRelated systems and potential data-exchange scope.Related programme contextExact cutover status of each named system is not uniformly documented.
Predecessor SQL Server warehouseLegacy analytical platform to be replaced.Retirement unconfirmedNo explicit decommissioning date was found.

Implementation challenge

The May 2025 status report recorded issues as different CSBs went live with different EHR vendors. The programme remained green, and the team reported resolving issues quickly, but the evidence shows that source-system variation—not only warehouse technology—was a material delivery constraint.

Destination architecture and governance

  • Core platform: Snowflake Data Cloud.
  • Cloud environment: AWS environment supplied by VITA.
  • Pattern: serverless, event-driven architecture integrating AWS services with Snowflake.
  • Implementation partner: Deloitte, with the contract beginning in July 2024.
  • Data model scope: master patient index, new and existing source connections and refactored reporting.
  • Reported economics: $11,081,064 total project cost, comprising general-fund and non-general-fund sources.

Completion semantics

The December 2025 status report establishes that the final release was implemented. The May 2026 portfolio status establishes project completion. Those facts do not by themselves establish that every legacy SQL Server component, report or interface was switched off in May 2026.

Known unknowns and monitoring questions

  • The exact date of SQL Server warehouse decommissioning.
  • Whether every one of the 40 CSBs completed migration on its original timetable.
  • The current operating status and service performance of the Snowflake platform after project closeout.
  • The Snowflake edition, region and full resilience configuration.
  • The final production status of every related source system and interface.
  • Whether all predecessor reporting assets were retired or retained for historical use.

PlatformTrace analysis

The strongest evidence supports a completed modern-data-platform programme with production workloads moving during 2025 and the final release delivered by December. The May 2026 “complete” designation is best interpreted as portfolio and administrative closure, not the technical cutover date.

For enterprise clients, the useful lesson is that the warehouse replacement depended on a federated source estate: 40 boards, multiple EHR vendors, identity resolution and report refactoring. The difficult part was not simply provisioning Snowflake. It was aligning heterogeneous operational systems and moving each producer into a governed data model.

Next monitoring triggers

  • An explicit predecessor-retirement notice.
  • Post-implementation performance or adoption reporting.
  • Expansion to additional data sources.
  • Public confirmation that all 40 CSBs completed migration.
  • Any follow-on procurement for the same platform.

Evidence ledger

  1. DBHDS FY24–26 IT strategic planOfficial agency plan · 30 November 2023 · proves project start, predecessor-replacement objective, original schedule, report refactoring and ingestion goals.
  2. Virginia Executive Data Board materialOfficial governance material · August 2024 · proves AWS and Snowflake development-environment preparation.
  3. VITA May 2025 project status reportOfficial status report · May 2025 · proves CSB production go-lives, EHR-vendor issues and continuing migration work.
  4. VITA December 2025 project status reportOfficial status report · December 2025 · proves the final release and planned closeout.
  5. DBHDS FY26–28 IT strategic planOfficial agency plan · 7 October 2025 · proves Deloitte, AWS hosting, replacement framing and MPI scope.
  6. VITA May 2026 major-project portfolioOfficial portfolio · May 2026 · proves completed-project status and programme economics.
  7. AWS re:Invent 2025 DBHDS and Deloitte sessionTechnical conference presentation · December 2025 · supports Snowflake-on-AWS and serverless event-driven architecture.

Corrections and update history

  • Initial verified record published with production and completion boundaries.
  • Expanded into a dossier covering project chronology, economics, architecture, CSB/EHR scope, MPI work and the unconfirmed predecessor-retirement boundary.

No correction is currently open. Explicit retirement or later operating milestones will be appended.