HubSpot to Data Studio: how to connect CRM data, what it costs and how to build pipeline reports that hold up

Can you connect HubSpot to Data Studio without a paid connector?

Yes. The free routes are a Sheets add-on with a free tier, Google's BigQuery transfer while it is in Preview, a vendor's free plan for a single account, or manual CSV exports. What you trade away is refresh frequency, object coverage and the time someone spends keeping it running.

Data Studio's native connectors cover Google products and a set of databases: GA4, Google Ads, Search Console, Sheets, BigQuery, YouTube, Campaign Manager 360, Display and Video 360, Ad Manager, Cloud SQL, MySQL, PostgreSQL, SQL Server and Redshift. HubSpot is not on that list, and the April 2026 rename from Looker Studio back to Data Studio did not add it. Every HubSpot route therefore goes through a partner connector or lands the data somewhere Data Studio already reads.

The free options I checked on the vendors' own pages in October 2026: Coefficient has a free plan that pulls HubSpot records into Google Sheets, with paid plans from $49 a month. Windsor.ai keeps a forever free plan with 1 user, 1 data source and 1 account. Google's documentation for its HubSpot transfer states there is no cost to transfer HubSpot data into BigQuery while the feature is in Preview, though BigQuery storage and queries are billed as usual once you pass the free tier.

What are the five ways to get HubSpot data into Data Studio?

Each route trades setup speed against freshness, cost and control over the data model. The right one depends on how many records you have, how far back you report, and whether HubSpot must be joined to ad spend or finance data.

A partner connector sits in the Data Studio connector gallery and queries HubSpot (or the vendor's copy of it) when a chart loads. A Sheets route writes HubSpot records into a Google Sheet on a schedule, and Data Studio reads the sheet. A BigQuery route loads HubSpot objects into tables, either with Google's own transfer service or an ETL vendor. A hosted database route, such as Datawarehouse.io, syncs HubSpot into a SQL database you then connect with Data Studio's SQL Server connector. A CSV route means exporting a view from HubSpot by hand.

How much does a HubSpot connector for Data Studio cost?

Entry prices run from free to about $99 a month, and the jump comes with refresh frequency and the number of portals. The figures below come from each vendor's own pages, read in October 2026. Vendors change prices often, so confirm on the pricing page before you buy.

Price the plan you will need in six months, not the entry tier. Count your HubSpot portals, the objects you need (deals, contacts, companies, tickets, custom objects), how fresh the pipeline view must be, and which ad platforms belong in the same report. A sales team that reviews pipeline every Monday does not need a 15-minute refresh.

What is Google's HubSpot transfer to BigQuery, and should you use it?

It is a HubSpot connector inside BigQuery Data Transfer Service that loads HubSpot objects into BigQuery on a schedule, and it is free while it remains in Preview. For a team that already has a Google Cloud project, it is now the cheapest way to get HubSpot history into a warehouse that Data Studio reads natively.

According to Google Cloud's documentation (last updated October 13, 2026), the transfer authenticates with a HubSpot private app access token, so someone with admin rights must create a private app in HubSpot and grant read scopes such as crm.objects.contacts.read and crm.objects.deals.read. You select the objects to transfer, including contacts, companies, deals, owners and custom objects, then set a repeat schedule or run it on demand. Preview features fall under Google's Pre-GA Offerings Terms, with support through a preview mailbox rather than standard Cloud support.

My view: use it for new builds where you want history and joins, but treat it as Preview. Keep the private app token owned by a company admin account, check each run in the transfer history for the first few weeks, and do not point a board report at raw transfer tables. Build a modelled view on top (one row per deal with stage dates, owner name and amount), partition anything large by date, and connect Data Studio to the view. If Google changes the schema when the connector leaves Preview, you fix one view, not every chart.

Why do HubSpot pipeline reports in Data Studio show the wrong numbers?

Mostly because the CRM data model does not fit a flat table, not because the connector failed. HubSpot stores deals, contacts and companies as separate objects linked by associations, and Data Studio wants one row per thing you count. Check the causes below in order before blaming the vendor.

The fix for most of these is the same: decide what one row means (one deal, one contact, one stage change), build that table once in a Sheet or BigQuery view, and point every chart at it. A blend that joins contacts to deals inside Data Studio will repeat a deal's amount for each associated contact and inflate pipeline value.

• Associations: a deal linked to three contacts appears three times in a joined table, tripling its amount in any SUM.
• Multiple pipelines: a sales pipeline and a renewals pipeline share stage names like Closed Won unless you filter on pipeline ID.
• Stage history: the current deal stage tells you where a deal is now, not when it moved. Velocity and conversion reports need HubSpot's date entered stage properties or a history table.
• Owners: connectors often return an owner ID, not a name; without an owners lookup, charts show numbers instead of reps.
• Deleted and archived records: some connectors drop them, others keep them, so totals differ from HubSpot's own reports.
• Currency and close date: multi-currency portals need the company-currency amount field, and deals without a close date vanish from date-filtered charts.
• Time zones: HubSpot timestamps and the report's date range can fall on different days around midnight.

What should a HubSpot dashboard in Data Studio include?

Build it around the decisions your team makes each week: where pipeline will land this quarter, which sources bring deals that close, and which reps or stages are stuck. A good first version fits on three pages.

Page one is pipeline: open pipeline value by stage and close month, weighted forecast against target, deals created and won this period, win rate and average days to close. Page two is source quality: contacts and deals by original source, conversion from lead to opportunity to customer, and won revenue by first campaign, ideally beside Google Ads and Meta spend so cost per opportunity is visible. Page three is team activity: deals by owner and stage, stalled deals with no stage change in 30 days, and a filterable deal list so a manager can click through to the record.

Use a calculated field with a CASE statement to group raw lifecycle stages into the three or four labels your board uses, and a date range control set to the close date, not the create date, on pipeline pages. Projects I've led at Greenwolf Tech Labs include marketing dashboards built this way, bringing multi-channel spend, leads and return across Google Ads, Meta, LinkedIn, GA4 and Search Console into one view.

Do HubSpot API limits affect a Data Studio report?

They can, on busy reports with a live connector. Every live chart load can turn into HubSpot API calls, and HubSpot caps how many calls each app and each account can make. Warehouse and Sheets routes avoid the problem because Data Studio reads the copy, not HubSpot.

HubSpot's developer documentation lists these limits for privately distributed apps: Free and Starter portals get 100 requests per 10 seconds per app and 250,000 requests per day per account. Professional gets 190 per 10 seconds and 625,000 per day. Enterprise gets 190 per 10 seconds and 1,000,000 per day. An API Limit Increase add-on raises this to 250 per 10 seconds and adds 1,000,000 a day. The daily figure is shared by every integration on the portal, so a connector competes with your forms, enrichment tools and sync apps for the same budget.

If charts time out or return partial data, reduce live load first: lengthen the data freshness setting on the data source where the connector allows it, cut duplicate charts that request the same fields, and move high-traffic reports to an extract, a Sheet or BigQuery. If you also report GA4 on the same dashboard, remember its separate quota of 14,000 tokens per project per property per hour.

How do you connect HubSpot to Data Studio step by step?

The clicks take minutes. The steps that save you later are about ownership, scope and testing, so they are included here.

Data Studio data sources run on the owner's credentials by default, so viewers see HubSpot data without a HubSpot seat. That is useful, but if the connecting login belongs to a contractor or an employee who leaves, every chart breaks the day their access is removed, and Data Studio gives no warning when a connector stops working.

• Agree the questions: list the five or six numbers leadership reviews, and the definition of each (for example, won revenue by close date, in company currency).
• Choose the route: partner connector for a quick single-portal report, BigQuery for history and joins, Sheets for a small CRM on a budget.
• Use a company-owned login or private app: never a personal or freelancer account.
• Pull only what you need: deals, deal stages, pipelines, owners and the contact and company fields used in charts, not every property.
• Model one row per deal: flatten associations, add stage dates and owner names before Data Studio sees the data.
• Reconcile: compare last quarter's won revenue and deal count against a HubSpot report with the same filters before anyone else sees the dashboard.
• Share the report, not the data source, and schedule an email delivery for the weekly pipeline meeting.

When is HubSpot to Data Studio not worth it?

If HubSpot is your only source and your team already lives in HubSpot, its own dashboards and report builder may be enough. Moving data out adds a connector, a data model and something else to maintain, and you should only take that on for a reason.

Good reasons: leadership needs CRM pipeline beside ad spend, GA4, finance or product data in one place; people who should see the numbers do not have HubSpot seats; you need history or definitions that HubSpot reports cannot hold; or you want one reporting tool across several systems. Weak reasons: a nicer chart style, or copying a HubSpot dashboard that already works.

Do it yourself if you have one portal, a simple pipeline and someone comfortable in Data Studio; a free connector tier and an afternoon is the right spend. Bring in help when deal values do not match HubSpot, when several pipelines or currencies are involved, or when the report must keep working after the person who built it moves on.

How I handle HubSpot to Data Studio projects

I start with a free review of your HubSpot portal, the questions the report must answer and any existing dashboards. I recommend the cheapest route that will hold up, which is often a connector you already pay for or Google's BigQuery transfer, and quote a fixed price for the build.

The work covers the data model (one row per deal, stage history, owner lookups, currency), the dashboard itself, reconciliation against HubSpot, and a handover so your team can add fields and pages without me. Everything lives in your Google and HubSpot accounts from day one, so nothing depends on my logins.