How to explain Data Hub to whoever decides

If you have five minutes

Whoever approves the seat or the beta is not asking what Data Studio does.
They are asking whether the data already sitting in HubSpot can be trusted, and what it costs to make it so.

1 of 5

The room you are walking into

Whoever approves the seat or the beta is not asking what Data Studio does. They are asking whether the data already sitting in HubSpot can be trusted, and what it costs to make it so. If the page you forward answers the first question and skips the second, it gets read and not acted on.

2 of 5

Say this, not that

Say: the criteria finally exist. Merge Rules | Winning Record Rules (public beta) gives HubSpot its first real criterion for which record survives a merge, instead of "created first" or "most recent engagement" — the two options nobody actually merges on.
Do not say: "it deduplicates for you." Create Custom Rules to Manage Duplicate Records (public beta) still asks someone to write the rule that flags a duplicate. Nobody automated the judgment out of it; they gave the judgment a place to live.
Say: transformation is what costs credits, not movement. Credit Consumption Updates for Data Warehouse CRM Syncs via Data Studio (live) draws the line at whether Data Studio is transforming the data, not at whether data moved at all.
Say: you can finally watch the export run. Amazon S3 Data Out (public beta) added object-level selection, scheduling, and sync health, so a nightly export stops being something you hope happened.

3 of 5

Watch the word "winning"

A caution worth repeating in the room

"A record is only winning until you need a value from the other one to override it." — Casey Hawkins, on Merge Rules | Winning Record Rules (public beta), first covered August 6, 2026

Casey's own follow-on, from the same take: define the word everywhere it is used, or the label stops describing what is actually happening the first time someone needs a field back from the record that lost.

Full take — Merge Rules | Winning Record Rules.

4 of 5

The words, and what each mistake costs

The words, and what each mistake costs
Term	What it means	What loses the room
Duplicate rule vs. Merge Rules	A duplicate rule decides two records describe the same person; Merge Rules decides which one survives once they are flagged	Treating them as one feature — they shipped as two separate 2026 releases
Transformation vs. movement	A straight warehouse-to-CRM sync consumes no Data Studio transformation credit; transforming inside Data Studio does	Assuming every sync is billed the same, no matter what it does to the data
Object-level selection	Choosing which objects leave HubSpot in an S3 export, rather than exporting everything	Assuming "data out" means a full, undifferentiated dump
Winning record	The record chosen to survive a merge	Treating "winning" as permanent instead of "chosen, until a value is needed back from the one that lost"

5 of 5

Objections and answers

"We already dedupe with another tool.": Create Custom Rules to Manage Duplicate Records is a public beta on HubSpot's own admin surface, not a replacement for judgment — it gives HubSpot a rule engine for the job a third-party tool used to own alone. Whether it covers everything your current tool does has not been checked here; verify against your own duplicate rules before switching anything off.
"Won't this cost us more in sync credits?": Not automatically. The credit change draws the line at transformation, not at movement — Casey Hawkins and Chris Carolan, on the record: "Charging credits for what amounts to a straight write to a record, the same shape as an API update or a CSV import, was hard to defend." If a straight sync was held back on cost grounds, that is the thing to revisit first.
"How do we know last night's export actually ran?": That is the headline of Amazon S3 Data Out, not the fact that export exists: "A data pipeline you cannot observe is one you cannot trust, and the old beta's real failure was leaving teams unsure whether last night's export ran at all." Object-level selection, scheduling, and sync health together are the answer.

Full take — Credit Consumption Updates for Data Warehouse CRM Syncs via Data Studio.

Full take — Amazon S3 Data Out.

Where to next

Where this comes from

Merge Rules | Winning Record Rules, the show's own take. Casey Hawkins on the record; public beta, first covered August 6, 2026
Credit Consumption Updates for Data Warehouse CRM Syncs via Data Studio, the show's own take. Casey Hawkins and Chris Carolan on the record; live, first covered August 3, 2026
Amazon S3 Data Out, the show's own take. public beta; the written take is the only record referenced here, and it carries no air date and no byline
Create Custom Rules to Manage Duplicate Records. public beta; first covered on the show 2026-05-27, status read from the record

What we do not know yet

No independently run cost comparison exists in the material behind this door. The credit-change take states the principle — transformation, not movement, is what is charged — but not a dollar figure to bring into a budget conversation.
Whether Create Custom Rules to Manage Duplicate Records has moved out of public beta since it was last covered on 2026-05-27 has not been re-checked against the live portal for this draft. Verify current status before promising it as generally available.
Amazon S3 Data Out's take carries no air date and no byline on the published page, unlike this Hub's other three own takes. It was never covered as a discussion on the show; the written take is the only record of it referenced here.