HubSpot to BigQuery integration and connector tools compared, including Google's Preview transfer that is free for now
Eleven ways to get HubSpot into BigQuery, starting with the two native ones. Google's Data Transfer Service connector costs nothing during Preview, reloads all of your HubSpot data on every run, and authenticates with a private app token of the kind HubSpot stops letting existing accounts create on October 26, 2026. HubSpot's own integration needs Data Hub Enterprise and refreshes every 6 hours at best. All of it read from Google and HubSpot documentation on 22 September 2026.
The live demo needs no card, and Starter is $49 a month.
Field mapping auto-plugged · tap a port to rewire
Plug a source port into
Transform on this cable
JSON in
JSON out
5 sample records ready
Vendor documentation read 22 September 2026
Which HubSpot to BigQuery connector should you use?
Try Google's BigQuery Data Transfer Service connector first if your portal is small or mid-size, a daily refresh is enough, and you can create a HubSpot private app before October 26, 2026. It is free while in Preview and lands native tables in your own project. If you already pay for Data Hub Enterprise and 6 hour freshness is fine, HubSpot's own integration is included. Choose a paid pipeline or a mapping tool when you need incremental syncs on a large portal, exact NUMERIC money columns, a support contract, or a route that does not depend on a Preview connector's pricing at GA.
For the vendor landscape on the HubSpot side, see HubSpot integration tools. For every other source into the same warehouse, see BigQuery ETL tools, and if your team is weighing Snowflake instead, the same CRM is compared on HubSpot to Snowflake integration tools.
What Google's HubSpot connector actually does, and what a buyer assumes it does
Google's setup page for HubSpot is short and every sentence on it matters. We read it on 22 September 2026 beside the BigQuery pricing page and HubSpot's own developer changelog, then wrote down what each line costs a revenue team. The last column is what we would do about it.
| What is at stake | What the docs say | Why it matters to a buyer | What we would do |
|---|---|---|---|
| Launch stage | Marked Preview and "subject to the Pre-GA Offerings Terms". Pre-GA features "are available as is and might have limited support". Support runs through a preview mailbox. | No SLA and no standard support path for a pipeline your board metrics may depend on. Behavior can change before GA, and so can the price, which is zero today. | Use it, with a fallback you have tested |
| What each run moves | "With every transfer run, the HubSpot connector transfers all available data from HubSpot into BigQuery." | There is no incremental watermark documented. A portal with a million contacts reads a million contacts every run, so run time and API use grow with the size of the portal, not with the amount of change. | Schedule by portal size, daily for most |
| Authentication | Accepts a HubSpot private app access token only, and links to HubSpot's legacy private apps documentation. | HubSpot stops creation of legacy private apps on September 28, 2026 for new accounts and October 26, 2026 for existing accounts. Its recommended replacement, Service Keys, is not mentioned on Google's page. | Create the private app before October 26 |
| Scopes it asks for | More than 30 required scopes, including automation, content, files, social, transactional-email, crm.import and crm.export, plus optional scopes such as crm.dealsplits.read_write. | An analytics copy that only reads data still needs a token with a very wide grant, including scope names that describe importing and writing. Your security review will ask why, and the token lives in a transfer config. | Put the token owner and rotation in writing |
| Money and number columns | The documented mapping covers String, Text, Integer, Boolean, Date, Datetime and Long. Long becomes BIGNUMERIC. | HubSpot's number and enumeration property types are not in the table. Deal amount is a number property, so the type it lands as is something you confirm on a sample, not something the docs promise. | Cast amounts to NUMERIC in a staging view |
| Date properties | HubSpot Date maps to TIMESTAMP, the same as Datetime. | A close date becomes a point in time. HubSpot stores date properties at midnight UTC, and converting that to Eastern or Pacific time for a US report moves it to the previous evening, so month-end deals slip into the prior month. | Cast date properties back to DATE in UTC |
| BigQuery permissions | The person creating the transfer needs BigQuery Admin on the project, or a custom role with the transfer and dataset IAM permissions listed. | Many analytics teams do not hold project admin. Expect a ticket to your cloud platform team before the first run, and plan for it in the timeline. | Request a custom role, not full admin |
| Price after Preview | Preview connectors "will not be charged. Billing will start once connector are GA." HubSpot is listed among the paid connectors, billed in slot-hours. | A full reload on every run is exactly the pattern that makes slot-hour billing grow. Free today, and on GA the bill will follow run time, which follows portal size. | Log run durations now to forecast GA cost |
The authentication row is the one with a deadline. Google's page was updated on 18 September 2026 and still asks for a private app token, linking to HubSpot's documentation for legacy private apps. On 27 August HubSpot announced that legacy private app creation ends on September 28, 2026 for accounts created from that day and on October 26, 2026 for everyone else. Existing apps and tokens keep working, so a team that creates its private app this month is fine for now. A team that starts in November may find the only path is HubSpot's Service Keys, which Google does not mention. We are not going to guess whether the transfer accepts them. Ask Google in writing, and see the limits that decide how fast any HubSpot pipeline can run on HubSpot API rate limits.
Google's HubSpot connector against HubSpot's BigQuery integration
Both vendors ship a HubSpot to BigQuery route, both are pre-release, and they are built on opposite sides. One question settles most cases before any feature comparison: are you on Data Hub Enterprise? If not, HubSpot's integration is not available to you.
| Question | Google Data Transfer Service | HubSpot BigQuery integration |
|---|---|---|
| Who builds it | Google, inside BigQuery Data Transfer Service | HubSpot, installed from the HubSpot side |
| Launch stage | Preview, Pre-GA terms | Beta |
| HubSpot tier needed | Any tier that can create a private app | Data Hub Enterprise only |
| Price today | Not charged during Preview | Included in Data Hub Enterprise; credits apply to some Data Studio prep |
| Fastest schedule | Custom schedules and on-demand runs; every run is a full reload | Every 6 hours during beta |
| What lands | Native BigQuery tables in your dataset | External tables over parquet files in a Cloud Storage bucket |
| Sensitive properties | Supported with extra scopes | Not synced to BigQuery during beta |
| Pipelines per object | Several transfer configs allowed | One sync configuration per object, event type or association pair |
| Google permissions | BigQuery Admin, or a custom role | Data Viewer, Job User and Storage object owner |
The storage row is easy to miss. HubSpot's integration writes parquet files to a Cloud Storage bucket and creates BigQuery external tables that point at them, in a dataset named for your portal. That is cheap to land and slower to query than native storage, so heavy dashboards usually copy the external tables into native ones on a schedule. Google's connector writes native tables directly. On the Snowflake side HubSpot offers a different product again, a read-only data share, compared on the best HubSpot to Snowflake connector.
HubSpot to BigQuery connectors and integration tools compared
Billing units rather than price tags, because most vendors here quote or meter and any figure we printed would be stale within a quarter. Where a tool is the wrong fit, the last column says so, including for us.
| Tool | Approach | Best for | Billing unit | What to watch |
|---|---|---|---|---|
| BigQuery Data Transfer Service | Google's HubSpot connector, private app token, full reload each run | Small and mid-size portals on a daily schedule | Free in Preview, slot-hours after GA | Preview terms, no incremental mode, token model changing. |
| HubSpot BigQuery integration | HubSpot export to parquet in Cloud Storage, external tables | Existing Data Hub Enterprise customers | Data Hub Enterprise subscription | Beta, 6 hour fastest schedule, no sensitive data. |
| Fivetran | Fully managed ELT with schema drift handling | Zero pipeline maintenance across many sources | Monthly active rows | The initial history load is the biggest active-row month you will have. |
| Airbyte | Open source connectors, self-hosted or Airbyte Cloud | Engineering teams comfortable owning the pipeline | Credits per million API rows, or capacity | Full refresh syncs charge every row, every time. |
| Stitch | Managed replication on the Singer specification | Plain object replication on a predictable budget | Rows loaded per month | Less control over schema when HubSpot properties change. |
| Hevo Data | No-code managed pipelines | Smaller teams wanting a managed pipeline | Events loaded per month | Event metering spikes during the initial load. |
| Estuary Flow | Streaming pipelines with a change log | Low latency across several sources | Data volume and connectors | HubSpot is still polled by API, which sets your latency floor. |
| Windsor.ai | Marketing-focused connectors into BigQuery | Attribution joining CRM to ad platforms | Subscription tiers | Built for marketing reporting more than full CRM replication. |
| Coupler.io | Scheduled imports into sheets and warehouses | Light scheduled pulls of a few objects | Subscription tiers | A report-refresh tool more than a replication pipeline. |
| CRM API plus bq load | Scripted paging through the CRM API, staged file, batch load | One-time analysis or a few objects daily | Your engineering time plus storage | You own paging, rate limits, deletes and retries. |
| Adapters | Field mapping you set once, scheduled incremental sync | Teams who want types explicit and a flat bill | Flat tiers by synced records, from $49 a month, no overage fees | No sub-minute streaming, no in-warehouse modelling, not a HubSpot backup. |
What these billing units come to on the same HubSpot portal, and why a free connector that reloads everything can still be the expensive one once it leaves Preview, is worked through in HubSpot to BigQuery connector pricing. For the counting rules behind every meter on this list, see data integration pricing.
Six facts worth knowing before you choose
$0
What Google charges for its HubSpot connector while it is in Preview. Billing starts at GA, in slot-hours, at a rate Google has not published for HubSpot.
BigQuery pricing, Data Transfer Service section, read 22 September 2026
Every run
How often Google's connector reloads all available HubSpot data. No incremental mode is documented.
Load HubSpot data into BigQuery, read 22 September 2026
Oct 26, 2026
The date existing HubSpot accounts lose the ability to create legacy private apps. New accounts lose it on September 28.
HubSpot developer changelog, read 22 September 2026
Sept 2027
Enforcement date for moving legacy private apps to HubSpot's Projects model, alongside the end of support for v1 to v3 APIs.
HubSpot developer changelog, read 22 September 2026
6 hours
The fastest schedule HubSpot's own BigQuery integration offers during its beta. It requires Data Hub Enterprise.
HubSpot Knowledge Base, read 22 September 2026
625,000
Daily API calls for a Professional portal's private apps, shared across all of them. Free and Starter get 250,000, Enterprise 1,000,000.
HubSpot API usage guidelines, read 20 August 2026
Seven ways this pipeline goes wrong while every run shows success
None of these raise an error in the transfer itself. The table fills, the run turns green, and a number in a pipeline review is wrong. These are the checks we would run on any HubSpot to BigQuery setup before trusting it.
| The failure | What you see | What is actually happening |
|---|---|---|
| Deals that close a month early | Month-end bookings differ between HubSpot and the BigQuery dashboard. | Date properties land as TIMESTAMP at midnight UTC. A report that converts to US time moves a deal closed on the 1st back to the last evening of the prior month. |
| Other integrations failing at noon | The warehouse is fine. Your enrichment or billing sync starts returning 429s. | A full reload on every run spends the portal's shared daily API allocation, 250,000, 625,000 or 1,000,000 calls a day for private apps depending on tier, and every other private app draws on the same pool. |
| Runs that grow longer every month | The same schedule, and freshness quietly slipping from 1 hour to 3. | Nothing is incremental. Run time tracks total records, so a portal that doubles its contacts doubles every run, with no error to tell you. |
| Revenue that is off by cents | Pipeline totals disagree with the finance system in the last digit. | Deal amount is a HubSpot number property, and the documented mapping does not say what it becomes. If it lands as a floating point type, summing it loses exactness. |
| A pipeline that stops after a reorg | Transfers start failing with an authentication error one morning. | The private app token belonged to a user who left, or it was rotated. HubSpot recommends rotating legacy private app tokens every six months, and nobody updated the transfer config. |
| Sensitive fields missing without comment | A health or financial property is blank in BigQuery and populated in HubSpot. | HubSpot's own integration does not sync sensitive data during beta. On Google's connector, the sensitive scopes were never added to the private app. |
| Queries that got slow and costly | A dashboard that ran in seconds now takes a minute. | HubSpot's integration writes external tables over parquet in Cloud Storage. Heavy dashboards read those files on every query instead of native BigQuery storage. |
The second row is HubSpot's, not Google's. All private apps in a portal draw on one daily allocation, and a pipeline that rereads the whole CRM every run is the biggest consumer most portals will ever have. We worked through the same trade on the other warehouse on HubSpot to Snowflake integration tools.
Six steps that decide whether this project works
Step 1
Create the private app now, not next month
Google's connector needs a private app token and HubSpot turns off legacy private app creation for existing accounts on October 26, 2026. Create a dedicated private app owned by a service user rather than a person, add the required scopes plus the custom object and sensitive scopes you need, and record who owns rotation.
Step 2
Measure the portal before you pick a schedule
Every run reloads everything, so count your records per object first. A portal with 50,000 contacts can reload hourly without noticing. One with two million contacts will spend a large share of its daily API allocation on each run, and your other integrations share that pool.
Step 3
Split objects across transfer configs
Put fast-changing objects such as deals and contacts in one config and slow ones such as owners, products and pipelines in another on a daily schedule. It keeps each run short, and if one config fails the rest of the model still refreshes.
Step 4
Fix types in one staging view
Create a view per object that casts deal amount and other money properties to NUMERIC and casts date properties back to DATE in UTC. Point every dashboard at the views. It takes an hour on day one and saves a month-end reconciliation argument later.
Step 5
Log run time from the first week
Pricing is zero during Preview and slot-hours at GA. Export the run durations from the transfer history into a small table now, so that when Google publishes the HubSpot rate you can price your own workload in minutes rather than guessing.
Step 6
Reconcile on values, not row counts
Per object, compare record counts, the sum of deal amount by pipeline stage, and the count of deals closed per month in HubSpot against BigQuery. Row counts can match while every close date sits in the wrong month.
With Adapters the type decisions in step 4 happen when you map the field, so deal.amount can land
as NUMERIC and closedate as DATE from the first run, and syncs after the
backfill read only changed records. Our own field mapping for this pair is on the
HubSpot to BigQuery connector page.
Why US teams move HubSpot into BigQuery
Closed-loop attribution with Google Ads
Google Ads and GA4 transfers into BigQuery carry no Data Transfer Service charge. HubSpot deals are usually the last piece needed to tie a click to closed-won revenue.
Pipeline history HubSpot does not keep
A daily snapshot of deals in BigQuery keeps every stage and amount a deal passed through, which is the raw material for win-rate and slippage analysis.
Joining CRM to product usage
Product-led teams need account usage from the app database beside HubSpot companies to find expansion accounts. That join is a warehouse job.
Board metrics finance can audit
New bookings, net retention and CAC built from HubSpot and billing data in one place, with the SQL visible instead of a screenshot of a HubSpot report.
Lead scoring in BigQuery ML
Scoring models train where the data sits. Contacts, engagements and closed deals need to be in the warehouse, with dates and amounts typed correctly.
Consolidating HubSpot with Salesforce
After an acquisition, one team on HubSpot and one on Salesforce report from the same BigQuery tables. Tag every row with its source CRM, since IDs collide.
Five jobs where you should not pick us
A comparison that never says the competition wins is an advert. These are the cases where something else on this page is the right answer.
- A one-time export of a few objects for a single analysis. Export a CSV from HubSpot and load it. It costs less than any subscription, ours included.
- You already pay for Data Hub Enterprise and a 6 hour refresh is enough. HubSpot's own integration is included in that subscription and a third party adds little.
- A small portal, a daily schedule and a team comfortable running on Preview terms. Google's connector is free today and does that job inside your existing project.
- Very high volumes with engineers who want to own the pipeline. Self-hosted Airbyte moves the cost from a license to your servers and on-call time, and at scale that can be the cheaper trade.
- Full HubSpot backup with every version of every record kept for restore. That is a specialist product category and we are not in it.
Four questions to ask any vendor on this list
Question 01
Is the sync incremental, and what decides that?
Google's Preview connector reloads everything on each run. Ask any vendor which HubSpot property or endpoint they use to find changed records, and what happens to a record whose association changed but whose own properties did not.
Question 02
What type does deal amount become?
The fastest test of whether a vendor has run this route for a finance team. Ask for NUMERIC or the ability to choose, and ask to see a sample table with a closed deal in it.
Question 03
Which HubSpot authentication will you use after October?
Legacy private app creation ends on October 26, 2026 for existing accounts. Ask whether the vendor uses a public OAuth app, a private app or Service Keys, and what they plan for the September 2027 enforcement date.
Question 04
How many of my daily API calls will you use?
Private apps in one portal share a daily allocation. Ask for the expected calls per run for your record counts, so the warehouse does not starve the integrations that actually run the business.
Related HubSpot and BigQuery guides
HubSpot to BigQuery connector pricing
Free Preview, slot-hours at GA, and the metered alternatives on one portal.
HubSpot integration tools
API limits, tiers and the wider HubSpot vendor landscape.
BigQuery ETL tools
Every other source into the same warehouse, and how loads are billed.
Loading HubSpot into BigQuery
Objects, partitioning and incremental loads for a CRM model.
Salesforce to BigQuery integration tools
The other CRM into BigQuery, where Google's connector is already paid.
HubSpot to Snowflake integration tools
The same CRM into the other warehouse, with HubSpot's data share.
Questions buyers ask about HubSpot to BigQuery integration
- How do I connect HubSpot to BigQuery?
- Something has to copy the data, because BigQuery cannot query HubSpot directly. The options are Google's BigQuery Data Transfer Service connector for HubSpot, HubSpot's own BigQuery integration on Data Hub Enterprise, a managed pipeline such as Fivetran or Airbyte, or a script that pages through the HubSpot CRM API and loads the results.
- Does BigQuery have a native HubSpot connector?
- Yes, in Preview. The BigQuery Data Transfer Service lists HubSpot as a Preview connector under Google's Pre-GA terms, which means "as is" with limited support. It authenticates with a HubSpot private app access token, supports custom objects, and according to Google transfers all available data from HubSpot on every run.
- How much does the BigQuery HubSpot connector cost?
- Nothing while it is in Preview. Google's pricing page states that Preview connectors are not charged and billing starts once they are generally available. HubSpot is listed with the paid connectors, which Google bills in slot-hours, $0.06 per slot-hour on demand for GA connectors such as Salesforce. Google has not published a HubSpot rate yet.
- What is the best HubSpot to BigQuery connector?
- For a small or mid-size portal and a daily refresh, Google's free Preview connector is the obvious first test. HubSpot's own integration fits teams already on Data Hub Enterprise. A paid pipeline or an explicit mapping tool earns its fee when you need incremental syncs, exact money types, deletes handled, or a vendor with a support contract.
- Does HubSpot integrate with BigQuery natively?
- Yes, on one tier. HubSpot's Google BigQuery integration is a beta available with Data Hub Enterprise only. It exports objects, associations and events on a schedule of once, every 6 hours, every 12 hours, daily, weekly or monthly, and writes them as parquet files in Cloud Storage behind BigQuery external tables.
- How often can HubSpot data sync to BigQuery?
- It depends on the route. HubSpot's own integration offers every 6 hours at the fastest during its beta. Google's transfer takes a repeat frequency, a custom schedule or on-demand runs, but it reloads everything each time, so the practical ceiling is how long a full run takes and how much of HubSpot's daily API limit you can spare.
- Do I need a HubSpot private app for the BigQuery transfer?
- Yes. Google's connector accepts only a private app access token. HubSpot is disabling creation of legacy private apps on September 28, 2026 for new accounts and October 26, 2026 for existing ones. Tokens you already have keep working, but legacy private apps must move to the Projects model by September 2027.
- Can I sync HubSpot custom objects to BigQuery?
- Yes, on both native routes. Google's connector lists custom objects in its object browser in the format CUSTOM_OBJECT_NAME__c, and HubSpot's own integration exports standard and custom objects. Custom objects need the matching read scopes on your private app, and for Google's connector that means crm.objects.custom.read and crm.schemas.custom.read.
- Does the HubSpot BigQuery integration sync sensitive data?
- Not HubSpot's own one. HubSpot states that during the beta you cannot sync sensitive data to BigQuery. Google's connector documents separate scopes for sensitive and highly sensitive properties on contacts, companies, deals, custom objects and tickets, so it is the native route if those properties must reach the warehouse.
- What HubSpot data types land in BigQuery?
- Google's mapping sends String and Text to STRING, Integer to INTEGER, Boolean to BOOLEAN, Long to BIGNUMERIC, and both Date and Datetime to TIMESTAMP. The table does not list HubSpot's number or enumeration property types, the ones deal amounts and dropdowns use, so check a sample table before modelling revenue on it.
For pushing warehouse scores back into HubSpot, see reverse ETL tools, and for the whole market in one place, the best data integration tools.
Land HubSpot in BigQuery with close dates and amounts that reconcile
Map each property once, choose NUMERIC for amounts and DATE for close dates, run the backfill, then sync only what changed, with retries, alerts and per-record logs. Flat plans from $49 a month, no overage fees.
The live demo needs no card, and Starter is $49 a month.