Snowflake to HubSpot
Cloud data warehouse and analytics platform. It is retained as the system of record, and curated tables or views are synced into HubSpot.
Snowflake data can move into HubSpot, landing mainly in Data Hub. 3 of 6 mapped objects move directly (Curated customer tables/views (people), Curated account/organization tables/views and Derived fields and metrics (scores, health, usage segments)); 3 items need manual work and 2 do not move. Plan roughly 1-2 weeks for a small move and 6-12 weeks for a large one.
Migration checklist for Snowflake
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-2 views
Contacts and Companies only.
Mid migration
50k-1M records, several views and derived fields
Includes Deals and custom properties.
Large migration
>1M records, many objects, multiple sources
Needs governance, dedupe and phased syncs.
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 Snowflake: what you need to get in, what lands in HubSpot, and what will not.
REST (SQL API) plus SQL drivers and connectors
A Snowflake user with warehouse access plus READ on the database, schema and table or view to sync.
HubSpot Super Admin to opt in to the Snowflake Direct Sync beta and install the app. The Snowflake user also needs permission to create or edit HubSpot properties and records.
Choose your route
How will you move the data?
HubSpot offers an integration for importing records from Snowflake.
- You need: A Snowflake user with warehouse access plus READ on the database, schema and table or view to sync.
- Permission: HubSpot Super Admin to opt in to the Snowflake Direct Sync beta and install the app. The Snowflake user also needs permission to create or edit HubSpot properties and records.
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.
- HubSpot Snowflake data sync app (reads tables and views)
- SQL queries via SQL API or drivers
- Third-party ETL / reverse-ETL tools
Limits: To confirm
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: 6-12 weeks, usually phased.
Talk to a partnerWhere each object lands
In Snowflake
In HubSpot
Hover or tap anything on the left to see where it lands.
| Source object | In HubSpot | Moves | Notes |
|---|---|---|---|
| Curated customer tables/views (people) | Contacts | yes | Select a table or view, preview it, then map columns to HubSpot properties. |
| Curated account/organization tables/views | Companies | yes | The sync can target multiple objects. |
| Opportunity/order tables/views | Deals | partial | Likely supported as a standard object. Pipeline and stage mapping must be prepared in the view. |
| Derived fields and metrics (scores, health, usage segments) | Contacts | yes | Computed columns land as HubSpot custom properties, which can be created during the sync. |
| Reporting dimensions | Custom objects | partial | Depends on the object being supported by the sync. |
| Activity/event history | Notes | manual | Not confirmed in the sync docs. Likely needs the HubSpot import or API. |
What to expect
Infrastructure is retained and not replaced by HubSpot.
The sync is intended for curated tables and views, not a full warehouse copy.
Mapping is column-to-property and needs one clean row per record.
Warehouse values must match HubSpot property types and options.
Warehouse IDs must be stored in HubSpot to allow updates.
Test in a sandbox and use a one-way sync with clear field ownership.
Confirm the beta opt-in and tier in the HubSpot account before planning.
Check the per-sync credit estimate and sync only the needed columns and rows.
Use a dedicated read-only role limited to the sync views.
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.
Snowflake access and auth are backed by vendor docs and HubSpot's Snowflake sync is documented. Object-level mapping, limits and governance rest on category-level knowledge or non-primary sources.
Sources
Related migrations
Frequently asked questions
How do I migrate Snowflake to HubSpot?
1. Choose which Snowflake tables or views feed HubSpot and name an owner for each. 2. Create a dedicated Snowflake role and user with warehouse usage and READ on the target views. 3. Confirm HubSpot Super Admin access, the beta opt-in and the Data Hub tier. 4. Add a unique key and a last-modified column to each view.
What data can move from Snowflake to HubSpot?
These objects move directly: Curated customer tables/views (people), Curated account/organization tables/views and Derived fields and metrics (scores, health, usage segments). Check the mapping table for partial and manual items.
What does not move from Snowflake to HubSpot?
Snowflake compute, views logic, stored procedures, tasks, BI models and Raw or very large tables (full warehouse history). Plan to rebuild or retire these.
How long does a Snowflake to HubSpot migration take?
Small (<50k records, 1-2 views): 1-2 weeks. Mid (50k-1M records, several views and derived fields): 3-6 weeks. Large (>1M records, many objects, multiple sources): 6-12 weeks. These are planning estimates, not a quote.
What access do I need to export from Snowflake?
A Snowflake user with warehouse access plus READ on the database, schema and table or view to sync. HubSpot Super Admin to opt in to the Snowflake Direct Sync beta and install the app. The Snowflake user also needs permission to create or edit HubSpot properties and records.
Is there a native HubSpot connector for Snowflake?
Yes. Confirm the supported objects in discovery.
What compliance issues apply when moving Snowflake data?
Check: Warehouses often hold financial, health or minors' data. Exclude these from synced views unless the HubSpot account is approved for them.. Agree consent, retention and access rules before exporting.
Moving Snowflake 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