In Short: HubSpot Data in Your Unified Analytics Estate
HubSpot is one of the most widely used CRM and marketing platforms. Microsoft Fabric is where organisations build their unified data estate. Without an integration between the two, sales and marketing data lives in HubSpot's own reporting tools - siloed from financial, operational, and product data that could give it full context.
Integrating HubSpot with Microsoft Fabric brings contacts, deals, companies, marketing campaigns, and engagement data into OneLake alongside your other business data - enabling revenue analytics that span the full customer journey from first marketing touch to invoiced revenue.
Integration Options
HubSpot does not have a native Microsoft Fabric connector, so the integration is built using one of three approaches: the HubSpot API with a Fabric REST pipeline, a third-party data connector platform, or Azure Data Factory.
Option 1: HubSpot API with Fabric REST Pipeline (Recommended)
HubSpot's v3 API provides access to all core CRM objects - contacts, companies, deals, tickets, engagements, and marketing emails. Fabric's REST connector queries the HubSpot API using a private app token for authentication.
The standard approach:
- Create a HubSpot private app with the scopes required for your integration (crm.objects.contacts.read, crm.objects.deals.read, marketing-email.read, and others as needed)
- Build a Fabric pipeline with REST connector pointing at the HubSpot v3 API endpoint
- Use HubSpot's cursor-based pagination and filter on the updatedAt property for incremental loads
- Land raw data in Bronze OneLake tables
- Apply Silver and Gold transformations
Rate limiting: HubSpot allows 100 API requests per 10 seconds for most endpoints. Design your pipeline to handle 429 responses with exponential backoff.
Option 2: Third-Party Connector Platform
Platforms like Fivetran, Airbyte, and Stitch have pre-built HubSpot connectors that handle pagination, rate limiting, schema changes, and incremental loading, delivering data to OneLake or ADLS Gen2. For organisations that want a managed connector with minimal pipeline maintenance, this is a pragmatic choice. The trade-off is additional platform cost and dependency on the vendor's coverage of HubSpot custom properties.
Option 3: Azure Data Factory
ADF's REST connector can query the HubSpot API with similar capability to the Fabric approach. For organisations with existing ADF pipelines, this adds HubSpot alongside other integrations in a consistent orchestration environment.
Core HubSpot Objects to Integrate
Prioritise these objects for maximum analytical value:
Contacts: Email addresses, lifecycle stages, lead source, persona, subscription status, and custom contact properties.
Companies: Account-level data - name, domain, industry, size, HubSpot owner, and lifecycle stage. The join between contacts and companies enables account-based analytics.
Deals: Pipeline stage, deal value, close date, deal owner, associated contacts and companies. The primary table for sales performance analytics.
Engagements: Calls, emails, meetings, and notes associated with contacts and deals. Enables sales activity analysis and pipeline velocity tracking.
Marketing emails: Campaign sends, opens, clicks, and unsubscribes. Combined with deal data, this enables marketing attribution analysis.
Line items: Products associated with deals, enabling product-level revenue analysis.
Medallion Architecture for HubSpot Data
Bronze: Raw HubSpot API responses in OneLake with extraction timestamp. HubSpot returns nested JSON (associations, properties objects) - preserve the raw structure for reprocessing.
Silver: Flattened and normalised tables. Unpack HubSpot's property structure into clean columns. Resolve associations by joining deals to companies and contacts via the associations API. Standardise date fields (HubSpot uses millisecond Unix timestamps in v1; ISO 8601 in v3).
Gold: Business-logic tables. Calculate deal velocity (average days from creation to close by stage), marketing attribution (first touch, last touch, linear across interactions), and pipeline coverage ratios. Join HubSpot deal revenue with financial system invoiced revenue for pipeline-to-revenue reconciliation.
Power BI Reporting on HubSpot Data
The most valuable reporting combines HubSpot CRM data with financial and operational data that HubSpot alone cannot provide:
- Pipeline vs revenue reconciliation: HubSpot closed-won deal value vs invoiced revenue from your ERP
- Marketing channel attribution: Revenue traced back through deal creation to the originating campaign or channel
- Sales rep performance: Deal volume, average deal size, and win rate by rep, cross-referenced with activity engagement data
- Customer lifetime value: HubSpot deal history joined with financial system repeat purchase data
- Lead-to-revenue cycle time: End-to-end funnel timing from first marketing touch through sales stages to closed revenue
Our Power BI consulting team and Microsoft Fabric practice build HubSpot analytics implementations that combine CRM data with financial and operational data for genuinely unified revenue reporting.
