Google BigQuery to HubSpot
Serverless cloud data warehouse that usually stays in place as the system of record. Curated tables and metrics are synced into HubSpot.
Google BigQuery data can move into HubSpot, landing mainly in Data Hub. 4 of 6 mapped objects move directly (Curated tables/views of customer records, Account/organization tables, Opportunity/pipeline tables and Derived scores and metrics); 3 items need manual work and 2 do not move. Plan roughly 1-3 weeks for a small move and 8-16 weeks for a large one.
Migration checklist for Google BigQuery
Three phases, specific to this system. Tick steps off as you go.
Before
0 of 5 doneDuring
0 of 5 doneAfter
0 of 5 doneWhat will it take?
No price list: cost follows volume, custom objects and how much logic must be rebuilt. Answer four quick questions for a planning range.
The three scenarios
Small migration
<50k records, 1-3 tables
Single object sync of contacts or companies.
Mid migration
50k-1M records, 5-15 tables
Multiple objects, associations and derived fields.
Large migration
>1M records, many tables and metrics
Complex modelling, multiple pipelines and governance reviews.
What moves the number
Timeline ranges are planning estimates, not a quote. A partner confirms scope after discovery.
Access, mapping and limits
Start with how data leaves Google BigQuery: what you need to get in, what lands in HubSpot, and what will not.
BigQuery API (jobs/extract) plus SQL EXPORT DATA; HubSpot Data Hub sync tool
GCP project, BigQuery dataset access, and a GCS bucket URI for the HubSpot→BigQuery direction.
HubSpot Super Admin to install; GCP IAM rights to grant the HubSpot service account roles.
Extract jobs: up to 1 GB per single file (use wildcard URIs) and a 50 TiB/day shared-pool cap. HubSpot-side sync limits not confirmed.
Choose your route
How will you move the data?
HubSpot offers an integration for importing records from Google BigQuery.
- You need: GCP project, BigQuery dataset access, and a GCS bucket URI for the HubSpot→BigQuery direction.
- Permission: HubSpot Super Admin to install; GCP IAM rights to grant the HubSpot service account roles.
Native imports often bring over only some data, so check coverage per object in the mapping below.
Export each object, clean it, then import it into HubSpot.
- Extract job to Cloud Storage (CSV, JSON, Avro, Parquet)
- EXPORT DATA statement from a query to Cloud Storage
- Direct export to a local file, Sheets or Drive is not supported for table data; query-result downloads are limited
Limits: Extract jobs: up to 1 GB per single file (use wildcard URIs) and a 50 TiB/day shared-pool cap. HubSpot-side sync limits not confirmed.
Migration and sync tools can move more than a plain import. Confirm which objects each one supports before you choose.
Best when volume is high, custom objects are many or automation is heavy. That is the Large scenario: 8-16 weeks, usually phased.
Talk to a partnerWhere each object lands
In Google BigQuery
In HubSpot
Hover or tap anything on the left to see where it lands.
| Source object | In HubSpot | Moves | Notes |
|---|---|---|---|
| Curated tables/views of customer records | Contacts | yes | HubSpot's Data integration tool syncs BigQuery data to CRM objects; you map fields. |
| Account/organization tables | Companies | yes | Companies are a listed sync target. |
| Opportunity/pipeline tables | Deals | yes | Deals are a listed sync target. |
| Relationship/join tables | Custom objects | partial | The docs mention associations and other account data. Which custom objects are supported for inbound sync is unconfirmed. |
| Support/case tables | Tickets | partial | Likely possible through the generic object sync but not confirmed for the inbound direction. |
| Derived scores and metrics | Contacts | yes | Computed fields land as custom properties on existing records. |
What to expect
Infrastructure is retained and not replaced by HubSpot.
HubSpot does not share HIPAA-regulated data to BigQuery through this integration.
BigQuery has no native CRM schema, so keys and dedupe logic are yours to build.
Warehouse columns must be mapped to existing HubSpot properties.
HubSpot generates a service account email that you must add in your Google Cloud account.
Check the plan and credit budget, or use a third-party reverse-ETL tool.
Pilot with a small sync and keep a fallback.
Set the sync direction and field precedence per property.
Use wildcard URIs or partitioned exports.
Data governance and compliance
Decide what is allowed to move before anything is exported. Tick each gate once it is agreed.
How we researched this page
How much to trust each section, and where it comes from.
HubSpot's BigQuery connector docs and BigQuery export docs back access and export. Object mapping for BigQuery→HubSpot is only partly documented in what I retrieved, so field-level mapping and sync limits rest on category-level knowledge.
Sources
Related migrations
Frequently asked questions
How do I migrate Google BigQuery to HubSpot?
1. Confirm Data Hub Enterprise and HubSpot Credits availability. 2. Identify the BigQuery project, dataset and curated tables or views to sync. 3. Define a unique key and an email or domain match key per table. 4. Create the target HubSpot properties and association labels.
What data can move from Google BigQuery to HubSpot?
These objects move directly: Curated tables/views of customer records, Account/organization tables, Opportunity/pipeline tables and Derived scores and metrics. Check the mapping table for partial and manual items.
What does not move from Google BigQuery to HubSpot?
BigQuery datasets, SQL views, UDFs, scheduled queries and BI compute and HIPAA-regulated data in the HubSpot→BigQuery direction. Plan to rebuild or retire these.
How long does a Google BigQuery to HubSpot migration take?
Small (<50k records, 1-3 tables): 1-3 weeks. Mid (50k-1M records, 5-15 tables): 3-8 weeks. Large (>1M records, many tables and metrics): 8-16 weeks. These are planning estimates, not a quote.
What access do I need to export from Google BigQuery?
GCP project, BigQuery dataset access, and a GCS bucket URI for the HubSpot→BigQuery direction. HubSpot Super Admin to install; GCP IAM rights to grant the HubSpot service account roles.
Is there a native HubSpot connector for Google BigQuery?
Yes. Confirm the supported objects in discovery.
What compliance issues apply when moving Google BigQuery data?
Check: Health data: HubSpot does not send HIPAA-regulated data to BigQuery, Financial data, Minors' data and Hash or exclude sensitive personal columns before sync. Agree consent, retention and access rules before exporting.
Moving Google BigQuery into HubSpot?
A network of 153+ tiered HubSpot partners and 1,800+ accounts of experience. Tell us what you are moving and which hub matters most.
Talk to a partner