Sync data from
Google BigQuery to HubSpot

You have a few options to activate your data from Bigquery so your data doesn't end its journey in a BI dashboard. We've outlined the 5 most best options to sync your data to Hubspot below:

Option 1: Reverse ETL (Hightouch)

Reverse ETL is easy to implement because it runs on top of your warehouse. With Hightouch, you can sync data directly from BigQuery to Hubspot in real-time to support your various business teams. Better yet, Hightouch lets you map on any unique object and doesn’t store any of your data. You can define your data using SQL or the custom data models that your data team has built within BigQuery. Using the Hightouch UI you can easily map the appropriate columns to Hubspot in a matter of minutes. All you have to do is follow these steps.

Step 1: Connect to Your Data Source

Step 2: Connect Hightouch to Your Destination

Step 3: Create a data model or leverage an existing one

You can use SQL to define your data directly in the Hightouch UI or even leverage your existing data models.

Step 4: Choose Your Primary Key

With Hightouch you can map on any unique key, not just users and accounts.

Step 5: Create Your Sync

Once you have created your sync, you simply have to choose the appropriate columns and map them to the fields in your end destination.

Step 6: Schedule Your Sync

Once your sync is created you can run it manually, define a set interval, or schedule it to run after a dbt job is completed.

The first integration with Hightouch is completely free so you can actually get started today. If you want to learn more about Reverse ETL, download our guide.

Option 2: Manual CSV Files

An easy option for moving data from BigQuery to Hubspot is to simply download a CSV file and then upload that same CSV. This method is relatively simple as there is no barrier to entry and you can do it immediately. The problem with this method is that there is no continuous flow of data.

You have to manually download a dataset every time you receive a request. When data is stored in this format it becomes stale really fast, making it really difficult for your marketing and sales teams to actually act on the information in their business tools.

Option 3: Custom Integrations

Building your own in-house data pipeline is one way to tackle the challenge of moving data from BigQuery to Hubspot, but this requires your engineering team to spend a substantial amount of time not only getting this integration up and running but also managing and maintaining it.

BigQuery and Hubspot are constantly changing/updating their APIs and this usually translates into upstream or downstream failures unless properly addressed. If your data needs are relatively small this option could be worthwhile pursuing, but if you need to sync data to additional SaaS applications, this will quickly become unscalable and you will find that your engineers are spending all of their time building/maintaining data pipelines.

Option 4: iPaaS (Integration Platform as a Service)

Integration platforms like Tray and Workato, are great solutions for moving data from one source to another. They let you build intuitive workflows to automate tasks and processes between different SaaS applications.

The problem is, these workflows can get complex really quickly depending on your business needs, and most likely you will find yourself neck-deep trying to manage massive workflows with numerous if/then statements and various dependencies within each individual step. There is a high chance that you will even have to write custom code to get your workflows functional.

Option 5: CDPs (Customer Data Platform)

CDPs are probably the single most popular solution for moving data from one source to another. CDPs come with a number of built-in features, but the main use case they solve is enabling you to easily consolidate all of your customer data into a managed platform where it can then be sent directly to 3rd party SaaS applications and tools.

Pushing your data into a CDP means that it is no longer in your own cloud environment and this can sometimes cause problems around compliance. Additionally, it's important to note that CDPs have a long-drawn-out implementation process. It can take anywhere from six months to a year to start seeing value. In addition to this, CDPs do not let you map on custom objects, you are forced to use fields like users and accounts.