HubSpot System Integrations · Snowflake

HubSpot + Snowflake Integration

Both HubSpot and your ERP can land in Snowflake. Your warehouse becomes the layer where customer, order, and pipeline data meet, not a direct wire between the two systems.

Do you need a direct HubSpot-to-ERP integration if you already have Snowflake? Often, no.

If your goal is getting HubSpot and ERP data into the same reports, a warehouse pattern using HubSpot’s existing Snowflake capability solves that without a point-to-point connector. If your goal is operational, like triggering something in one system based on the other, the warehouse pattern alone does not solve that, and a direct integration may still be needed.

Talk to Our Integrations Team
Getting data into the warehouse
HubSpotData Share · Native
Your ERPNo first-party connector
Snowflake
Native HubSpot path
ELT, partner, or custom pipeline
HubSpot has a native path into Snowflake. Your ERP does not.
Two Patterns

Which Pattern Fits Your Company?

Point-to-Point PatternWarehouse Pattern
Typical CompanyHubSpot and one ERP, a defined sync needLarger, more data-mature; already running Snowflake, already has a BI function
What It SolvesSpecific operational handoff between two systemsGetting data from many systems, including HubSpot and ERP, into one place to report on
Who Asks for ItSales or ops leadership wanting a specific sync to workSales leadership asking why HubSpot reporting doesn’t match the ERP, routed to a data team that already owns Snowflake
Point-to-Point Pattern
Typical Company
HubSpot and one ERP, a defined sync need
What It Solves
Specific operational handoff between two systems
Who Asks for It
Sales or ops leadership wanting a specific sync to work
Warehouse Pattern
Typical Company
Larger, more data-mature; already running Snowflake, already has a BI function
What It Solves
Getting data from many systems, including HubSpot and ERP, into one place to report on
Who Asks for It
Sales leadership asking why HubSpot reporting doesn’t match the ERP, routed to a data team that already owns Snowflake

If your company already has a data team and a warehouse, and the complaint is “the numbers don’t match,” the fix usually isn’t a tighter connector between HubSpot and your ERP. It’s getting both systems’ data into Snowflake, where it can be reconciled and reported on consistently.

Self-Check

Which Snowflake Pattern Are You?

Warehouse pattern

You’re likely here if:

  • You already have Snowflake or another data warehouse in place
  • You already have a BI function or data team
  • The complaint you’re hearing is “the numbers don’t match” or “I don’t trust this report”
  • You’re trying to reconcile HubSpot with more than just one ERP
Point-to-point pattern

You’re likely here if:

  • You don’t have a warehouse or BI function today, and standing one up isn’t on your roadmap
  • The problem is operational: something needs to happen automatically across systems
  • You have one ERP relationship to solve for, with no broader data consolidation behind it

Some companies are both: a warehouse for reporting and a direct integration for the one or two things that need to happen in real time.

If you read the point-to-point list above and recognized your own situation, now’s a good time to take our Integration Readiness Check.

Two Different Problems

HubSpot-Snowflake Reporting Alignment vs. Operational Sync

“HubSpot’s numbers don’t match the ERP’s numbers” and “HubSpot needs to trigger something in the ERP” sound like the same category of problem, but they aren’t.

Warehouse pattern

Reporting Alignment

Getting a consistent, reconcilable view across systems for analysis and decision-making. This is what the warehouse pattern is built for. Land HubSpot and ERP data in Snowflake, and a BI team can build the reporting that shows how pipeline connects to revenue and how revenue connects to the ERP’s numbers, without either system needing to change how it operates.

Direct integration

Operational Sync

One system acting on the other in real time (e.g., a HubSpot deal creating a job in the ERP, a shipment in the ERP triggering an email in HubSpot). This requires a connection between the two systems, something acting on data as it changes.

Your Options

Point-to-Point vs. Warehouse Pattern

Point-to-Point IntegrationWarehouse Pattern (Snowflake)
Best ForA specific, defined operational handoff between HubSpot and one ERPCompanies already running Snowflake and a BI function, who need HubSpot and ERP data reconciled for reporting
ProsSolves real-time, two-way operational needs; the only option if something has to trigger across systemsUses infrastructure and expertise you likely already have; scales to every other system in your stack (not just one ERP); read-only Data Share requires HubSpot Data Hub Enterprise, but has no separate build cost beyond that plan and what you’re already paying for Snowflake
ConsBuilt and maintained around one ERP relationship; doesn’t extend to other systems without additional workDoesn’t solve operational sync by itself; ongoing Snowflake compute cost; requires a data team to build and maintain the reporting layer
Our TakeThe right call when the problem is operational, not reportingThe right call when the problem is reporting, and you already have the team and warehouse to act on it
Point-to-Point Integration
Best For
A specific, defined operational handoff between HubSpot and one ERP
Pros
Solves real-time, two-way operational needs; the only option if something has to trigger across systems
Cons
Built and maintained around one ERP relationship; doesn’t extend to other systems without additional work
Our Take
The right call when the problem is operational, not reporting
Warehouse Pattern (Snowflake)
Best For
Companies already running Snowflake and a BI function, who need HubSpot and ERP data reconciled for reporting
Pros
Uses infrastructure and expertise you likely already have; scales to every other system in your stack (not just one ERP); read-only Data Share requires HubSpot Data Hub Enterprise, but has no separate build cost beyond that plan and what you’re already paying for Snowflake
Cons
Doesn’t solve operational sync by itself; ongoing Snowflake compute cost; requires a data team to build and maintain the reporting layer
Our Take
The right call when the problem is reporting, and you already have the team and warehouse to act on it
Where Snowflake Stops

What You’d Still Need a Direct HubSpot ERP Integration For

The warehouse pattern doesn’t make point-to-point integration obsolete. You’d still need a direct HubSpot-to-ERP integration, warehouse or not, for:

Anything that has to happen in near real time, like a deal closing and immediately creating a job or sales order in the ERP
Anything where one system needs to trigger an action in the other, not just report on what already happened
Operational workflows that can’t tolerate the lag of a reporting layer, even a fast one
The warehouse pattern is additive to good reporting, not a replacement for operational sync.
The Asymmetry

How Does ERP Data Get Into Snowflake?

HubSpot has a native path into Snowflake. Your ERP does not.

Native

HubSpot side

Data Share is a connection you turn on at the right subscription tier, with no pipeline to build or maintain.

No first-party connector

ERP side

There is no first-party Snowflake connector for NetSuite, Epicor, or Vista. Getting that data into the warehouse means one of three things:

  • Managed ELT connector
  • Snowflake Marketplace partner connector
  • Custom pipeline your team owns

That asymmetry is the part most warehouse conversations skip, and it’s where the real cost of the pattern sits.

Scoping + Budgeting

Cost Comparison: Snowflake Warehouse vs. Point-to-Point

A warehouse is the more expensive option.

Snowflake’s pricing is consumption-based: you pay for compute (billed in credits, scaling with warehouse size and runtime), storage, and data transfer. On the HubSpot side, Data Share only comes with Data Hub Enterprise, so if you’re not already on that plan, that’s a cost to account for before anything Snowflake-side even enters the picture.

If your company already runs Snowflake for other data, the incremental cost of adding HubSpot and ERP data through Data Share is usually modest. However, if Snowflake isn’t already part of your stack, standing it up to solve what a point-to-point integration could solve more directly is a much larger commitment.

Point-to-Point Integration
One relationship
Costs what it costs to build and maintain, against one relationship.
  • Build
  • Ongoing maintenance
Warehouse Pattern
Your entire data strategy
Costs what it costs to build and maintain, against your entire data strategy.
  • Data Hub Enterprise
  • Snowflake compute
  • Storage
  • Data transfer
  • ERP pipeline
Before Build Work Starts

For Your Data Team

Everything above is what shapes the pitch and the budget. Everything here is what your data or BI team will actually be asked to configure or confirm before this gets built. Forward it to them directly, or walk through it together on our Integration Readiness Check.

Key HubSpot Snowflake Integration Terms

Snowflake Data Share
HubSpot’s mature Snowflake feature, included with Data Hub Enterprise, that exposes HubSpot data inside your Snowflake account, read-only.
Snowflake Direct Sync
HubSpot’s newer, beta Snowflake feature that supports syncing in either direction, including Snowflake data flowing into HubSpot records.
Reverse ETL
Tools like Hightouch and Census that sync modeled warehouse data back out into operational systems, such as a CRM.
Point-to-Point Pattern
A direct, dedicated connection between HubSpot and one ERP, built for a specific operational need.
Warehouse Pattern
Routing HubSpot and ERP data into a shared warehouse like Snowflake, where it’s reconciled and reported on in one place.

What Does HubSpot’s Snowflake Capability Do?

HubSpot offers two Snowflake capabilities: Snowflake Data Share and Snowflake Direct Sync.

Snowflake Data Share
Read-onlyData Hub EnterpriseSecure Data Sharing

The mature, read-only capability, available with HubSpot Data Hub Enterprise. It runs on Snowflake Secure Data Sharing, so your HubSpot data stays in HubSpot’s Snowflake account and is queryable from yours with no pipeline, no ETL, and no copy to maintain. You query it with SQL alongside your other data, and you pay Snowflake compute for the queries you run.

Freshness depends on which schema you query:
SchemaRefreshUse It For
V2_LIVEUp to every 15 minutesCurrent-state views where recency matters
V2_DAILYOnce per dayMost reporting; table-based and faster to query, what HubSpot recommends for querying directly in Snowflake
V2_LIVE
Up to every 15 minutes
Current-state views where recency matters
V2_DAILY
Once per day
Most reporting; table-based and faster to query, what HubSpot recommends for querying directly in Snowflake

A few views inside V2_LIVE still refresh only once a day: association definitions, owners, pipelines, and pipeline stages.

Snowflake Direct Sync
BetaSnowflake to HubSpotData Hub Enterprise

A separate, newer capability, still in beta as of HubSpot’s January 2026 documentation and also gated behind Data Hub Enterprise. Unlike Data Share, the sync runs the other way: Snowflake data flows into HubSpot records, not out. Setup requires a Super Admin to opt the account into the beta.

A single Snowflake table or view can sync to multiple HubSpot objects, and associations between those objects can be defined during mapping.

Limits worth knowing before you plan around it:
10 GBper table or view
200columns per table or view
30Mrecords per sync run
Runs on a schedule rather than in real time.
Can’t filter mid-sync, so filtering means building the view in Snowflake first.
Neither capability gives Snowflake a way to write back into your ERP.

Snowflake Direct Sync can enrich HubSpot records with Snowflake data, but Snowflake still has no path of its own back into NetSuite, Epicor, Vista, or any other ERP. That’s a separate problem, usually solved with reverse-ETL tooling or the ERP’s integration surface.

FAQ

Frequently Asked Questions

What is Snowflake?

Snowflake is a cloud data warehouse, not an ERP or a CRM. Companies use it to combine data from many systems, HubSpot and an ERP included, into one place for reporting and analysis. It’s the warehouse pattern this page describes, not another system you connect point-to-point.

Does HubSpot integrate with Snowflake?

Yes, through two separate capabilities. Snowflake Data Share is a mature, read-only feature that exposes HubSpot data inside your Snowflake account for querying. A newer Snowflake Direct Sync feature, gated behind Data Hub Enterprise, allows data to flow in the other direction as well.

Is HubSpot’s Snowflake integration read-only?

Partially, depending on which feature you use. Snowflake Data Share is read-only: HubSpot data flows into Snowflake, not back. A separate, newer Snowflake Direct Sync feature in beta allows Snowflake data to flow into HubSpot records as well, but it’s gated behind Data Hub Enterprise and doesn’t give Snowflake a path back into an ERP.

Do we still need an ERP integration if we have Snowflake?

Possibly, depending on what you’re trying to solve. If the need is operational, meaning something has to happen in real time across systems, Snowflake doesn’t solve that by itself and a direct integration is still the answer. If the need is reporting, Snowflake usually is the answer.

Why doesn’t HubSpot reporting match my ERP’s numbers?

Usually because the two systems are each reporting from their own definitions and timing, not because either is wrong. A warehouse pattern, reconciling both systems’ data in one place like Snowflake, is usually a more durable fix than trying to force tighter real-time sync between the two.

Which is more expensive: a data warehouse or an ERP integration?

It depends on whether you already have the warehouse and the team. If Snowflake and a BI function are already part of your stack, adding HubSpot and ERP data is a modest incremental cost. If you’d be standing up Snowflake for this reason alone, it’s a larger and more ongoing cost than a point-to-point integration would be.

What’s the difference between HubSpot’s Data Share and Direct Sync with Snowflake?

Data Share is the older, broadly available, read-only feature: HubSpot data flows into Snowflake for querying. Snowflake Direct Sync is newer, in beta, requires Data Hub Enterprise, and supports syncing in either direction, including Snowflake data flowing into HubSpot records.

What HubSpot plan do I need for Snowflake Data Share?

Data Hub Enterprise. Data Share is included with this plan and isn’t available on lower tiers, and you’ll also need your own Snowflake subscription (Standard, Enterprise, or Business Critical) to receive the share on Snowflake’s side.

Warehouse, Direct, or Both?

Start Your HubSpot System Integration Project

If the real question behind “we need a HubSpot-ERP integration” is actually “our reporting doesn’t add up,” that’s a different conversation and a different kind of project. Our integrations team can help you figure out which problem you have, and whether a warehouse pattern, a direct integration, or both is the right call.

Talk to Our Integrations Team