Back office ops · Production

WHOOP improves data quality and team efficiency by migrating from dbt Core to dbt Cloud

The problem

WHOOP's analytics team had no centralized governance, lacked built-in scheduling and orchestration in dbt Core, and faced persistent data quality issues that consumed as much as a day per week of senior engineer time. As the team grew, stakeholders stopped receiving consistent answers, and an impending migration from AWS Redshift to Snowflake made data trust the team's top priority.

First attempt

dbt Core did not scale as the team grew: bottlenecks emerged from dependence on engineers outside the analytics team, stakeholders received inconsistent answers, and model failures were difficult to troubleshoot or vouch for.

Workflow diagram · grounded in source
1
Weekly production code fork
trigger
“every Friday, they fork their dbt code off of production”
2
Analytics engineer QA implementation
human_review
“An analytics engineer then implements the week's QA changes into a single release”
3
dbt Copilot documentation assist
ai_action
“dbt Copilot has streamlined our process by cutting PR review times from thirty minutes to five—making it easy to maintain our 99% documentation coverage inertia”
4
Code-owner review and unit tests
validation
“gets code-owner review, and runs unit tests to ensure data integrity”
5
Production deployment with release notes
output
“After pushing the update to production, they share release notes with the business detailing the changes”
6
Shared data access via dbt Mesh
integration
“With dbt Mesh, every team can access these common assets via dbt Explorer and reference them in their own projects”
Reported outcome

After migrating to dbt Cloud, WHOOP saves 32+ hours per month on data error resolution, completed the Redshift-to-Snowflake migration in 3 months, and achieved 99% documentation coverage.
PR review times dropped from thirty minutes to five, and the team now experiences no production job failures or accidental errors.

Reported metrics
Hours saved per month on data errors32+
days to migrate from dbt Core to dbt Cloud1 day
Documentation coverage99%
PR review time reductionfrom thirty minutes to five
Show all 5 reported metrics
hours saved per month on data errors32+
days to migrate from dbt Core to dbt Cloud1 day
documentation coverage99%
PR review time reductionfrom thirty minutes to five
weekly data quality time (before state)as much as a day every week
Reported stack
dbt Coredbt Clouddbt Copilotdbt Meshdbt Explorerdbt Semantic LayerSnowflakeRedshiftSlack
Source
https://www.getdbt.com/case-studies/whoop
Read source ↗

Frequently asked questions

What did this team achieve with this AI workflow?

After migrating to dbt Cloud, WHOOP saves 32+ hours per month on data error resolution, completed the Redshift-to-Snowflake migration in 3 months, and achieved 99% documentation coverage.

What tools did this team use?

dbt Core, dbt Cloud, dbt Copilot, dbt Mesh, dbt Explorer, dbt Semantic Layer, Snowflake, Redshift, Slack.

What results were reported?

Hours saved per month on data errors: 32+; days to migrate from dbt Core to dbt Cloud: 1 day; Documentation coverage: 99%; PR review time reduction: from thirty minutes to five (source-reported, not independently verified).

What failed first in this deployment?

dbt Core did not scale as the team grew: bottlenecks emerged from dependence on engineers outside the analytics team, stakeholders received inconsistent answers, and model failures were difficult to troubleshoot or vo…

How is this back office ops AI workflow structured?

Weekly production code fork → Analytics engineer QA implementation → dbt Copilot documentation assist → Code-owner review and unit tests → Production deployment with release notes → Shared data access via dbt Mesh.

Related back office ops cases