HubSpot to Snowflake integration for analytics-ready CRM data

Authenticate HubSpot with a private app token, select the objects you need (contacts, companies, deals, engagements), map properties to Snowflake columns, and schedule an incremental run on the last modified date. Deals and their stage history are usually the reason the pipeline exists, so map the stage timestamps explicitly.

Deals first, then contacts and companies for the associations, then engagements if you report on activity. Association tables matter more than people expect: without the contact to company and deal to contact joins, a warehouse copy of HubSpot cannot answer any account-level question.

Map each custom property to an explicit, readable Snowflake column rather than dumping a properties blob. HubSpot property internal names are stable even when the label changes, so map on the internal name. Properties nobody reports on are worth leaving out; they cost load time and add columns your analysts have to ignore.

Yes. HubSpot enforces per-account limits over a rolling ten second window plus a daily request cap, and the ceiling depends on your subscription tier. Incremental loads and batch read endpoints keep a normal sync well inside both, while repeated full extracts of every contact are what exhaust the daily cap.

The HubSpot to Snowflake integration from Adapters loads contacts, companies, deals, and engagement events from HubSpot into Snowflake tables on an incremental schedule, so pipeline and attribution models run on a full history instead of a manual export. Field mapping is no-code.

Yes. This HubSpot to Snowflake connector ships prebuilt: the field mapping is wired the moment you pick the pair, transforms are included, and the first sync can run within minutes. No code or engineering sprint required.

Pricing is flat and monthly: Starter at $49, Growth at $149, Scale at $399. Every plan includes this pair, visual field mapping, and per-record logs. There are no per-task or per-row fees, so the bill stays the same as volume grows.

Hourly on Starter, every 5 minutes on Growth, and down to every minute on Scale. Failed records retry automatically with backoff, and alerting plus a full per-record log come standard on every run.

No. Fields are auto-mapped the moment you pick the pair, and you can rewire any mapping visually before the first sync. Incremental loads use the HubSpot hs_lastmodifieddate watermark so each run moves only changed records into Snowflake; deal amounts cast to NUMBER, millisecond timestamps become TIMESTAMP_NTZ in UTC, and deals, contacts, and companies land in their own tables so attribution and pipeline models read one clean, deduplicated dataset.