Databricks to HubSpot
Lakehouse data and AI platform. It is normally retained as the analytics warehouse, with curated tables synced to HubSpot rather than migrated.
Databricks data can move into HubSpot, landing mainly in Data Hub. 3 of 7 mapped objects move directly (Curated customer/account tables, Curated account/organisation tables and Derived fields (scores, usage metrics, segments)); 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 Databricks
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
Under 50k records, 1-2 objects
A reverse ETL tool with simple mappings.
Mid migration
50k-1M records, 3-5 objects
Includes derived fields, custom objects and dedupe.
Large migration
Over 1M records with multiple domains
Custom pipelines, rate-limit tuning and governance review.
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 Databricks: what you need to get in, what lands in HubSpot, and what will not.
REST (Databricks SQL Statement Execution API 2.0), plus SQL warehouse connections
SQL warehouse hostname and token (or OAuth), plus cloud storage if writing back; HubSpot private app token or OAuth.
Databricks SQL entitlement plus Unity Catalog or table ACL read access to the source tables; HubSpot admin for the private app or connector.
Databricks enforces per-workspace, per-API limits and returns HTTP 429. The Statement Execution API has endpoint-specific limits (see the Databricks resource limits page). HubSpot API limits apply on the write side.
Choose your route
How will you move the data?
No native connector was found.
- You need: SQL warehouse hostname and token (or OAuth), plus cloud storage if writing back; HubSpot private app token or OAuth.
- Permission: Databricks SQL entitlement plus Unity Catalog or table ACL read access to the source tables; HubSpot admin for the private app or connector.
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.
- SQL warehouse query via Statement Execution API
- Reverse ETL through a SQL warehouse (JDBC/ODBC style)
- Delta Sharing / open sharing
- Notebook/Python pipelines calling the HubSpot API
- Export to cloud storage files, then HubSpot import
Limits: Databricks enforces per-workspace, per-API limits and returns HTTP 429. The Statement Execution API has endpoint-specific limits (see the Databricks resource limits page). HubSpot API limits apply on the write side.
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 Databricks
In HubSpot
Hover or tap anything on the left to see where it lands.
| Source object | In HubSpot | Moves | Notes |
|---|---|---|---|
| Curated customer/account tables | Contacts | yes | Reverse ETL syncs modelled tables to HubSpot objects; the match key (email or an ID property) must be defined. |
| Curated account/organisation tables | Companies | yes | Sync keyed on a domain or external ID property. |
| Revenue/opportunity tables | Deals | partial | Pipeline and stage mapping must be designed in HubSpot first. |
| Derived fields (scores, usage metrics, segments) | Custom properties on Contacts/Companies | yes | Scores built in the warehouse are pushed to HubSpot properties. |
| Domain-specific entities (subscriptions, product usage) | Custom objects | partial | Needs a custom object schema defined in HubSpot beforehand. |
| Support/case tables | Tickets | manual | Analyst view: no documented standard mapping; depends on the customer's own schema. |
| Dashboards, notebooks, ML models, jobs | None | no | These remain in Databricks and are not CRM data. |
What to expect
These are compute and BI assets that stay in Databricks by design.
These are too large for CRM storage. Sync aggregates and selected records only.
The warehouse schema is customer-specific, so there is no fixed mapping.
Transformation is best done in Databricks before the reverse ETL step.
No native HubSpot connector was found.
Use a stable external ID property and dedupe before the first sync.
Sync consent and opt-out fields, and filter out suppressed records.
Use incremental syncs and batch sizes sized for HubSpot limits.
Batch syncs and set a short warehouse auto-stop.
Use a service principal with read-only access to the curated schema.
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.
Databricks access (Statement Execution API, token/OAuth auth) is backed by vendor docs. The HubSpot side rests on third-party reverse-ETL vendor pages and category-level knowledge, and no native HubSpot connector was found. Object mapping is an analyst design, not a documented migration path.
Sources
Related migrations
Frequently asked questions
How do I migrate Databricks to HubSpot?
1. Identify the curated Unity Catalog tables or views to expose to HubSpot. 2. Create a service principal and token or OAuth with read-only access to those views. 3. Provision a SQL warehouse for the sync and note its hostname and HTTP path. 4. Design HubSpot properties, custom objects and unique ID properties for the synced fields.
What data can move from Databricks to HubSpot?
These objects move directly: Curated customer/account tables, Curated account/organisation tables and Derived fields (scores, usage metrics, segments). Check the mapping table for partial and manual items.
What does not move from Databricks to HubSpot?
Notebooks, jobs, pipelines, dashboards and ML models and Raw lakehouse/event-scale tables. Plan to rebuild or retire these.
How long does a Databricks to HubSpot migration take?
Small (Under 50k records, 1-2 objects): 1-3 weeks. Mid (50k-1M records, 3-5 objects): 3-8 weeks. Large (Over 1M records with multiple domains): 8-16 weeks. These are planning estimates, not a quote.
What access do I need to export from Databricks?
SQL warehouse hostname and token (or OAuth), plus cloud storage if writing back; HubSpot private app token or OAuth. Databricks SQL entitlement plus Unity Catalog or table ACL read access to the source tables; HubSpot admin for the private app or connector.
Is there a native HubSpot connector for Databricks?
No native connector was found. Plan a CSV, API or third-party tool route.
What compliance issues apply when moving Databricks data?
Check: Warehouse tables may hold health, financial or minors' data depending on the customer; exclude it from syncs unless required.. Agree consent, retention and access rules before exporting.
Moving Databricks 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