How to Build a Custom Power BI Dashboard for HubSpot CRM: A Practical Guide for Australian Businesses
- GrowthBI

- Apr 30
- 10 min read
Updated: May 2

HubSpot is one of the most widely used CRM platforms in Australia. It does what it was designed to do well: tracking deals, managing contacts, logging activity, and keeping sales teams organised. Where it falls short is in reporting.
HubSpot's native reports are useful for surface-level pipeline visibility, but they have real limitations once your business needs to answer more complex questions. You cannot easily blend HubSpot data with revenue from your accounting platform, costs from your marketing tools, or operational data from other systems. Filtering is limited. The historical data model is rigid. And for leadership teams that need a single view across the business, HubSpot alone is not enough.
Power BI solves those problems. By connecting HubSpot to Power BI, Australian businesses can build custom dashboards that pull live CRM data alongside data from any other source, apply the business logic that matches how your company actually measures performance, and give leadership a real-time view that HubSpot's built-in reporting cannot produce.
This guide covers why HubSpot reporting has limits, how to connect HubSpot to Power BI, what dashboards to build, and how to get the most value from the integration in a practical Australian mid-market business context.
Why HubSpot's Native Reporting Is Not Enough for a Growing Business
HubSpot's reporting has improved significantly in recent years, but it still has structural constraints that show up once a business grows beyond a certain complexity.
Data lives in silos. HubSpot holds your CRM data. Your accounting platform holds revenue and costs. Your marketing tools hold campaign spend and channel performance. HubSpot cannot join these together into a single report, which means leadership is always looking at a partial picture.
Custom calculations are limited. If you need gross margin by deal source, customer acquisition cost blended with campaign data, or revenue per sales rep net of discounts and returns, you cannot build that in HubSpot. The calculation engine is not designed for it.
Historical trend analysis is constrained. HubSpot snapshots data in ways that make comparing this month to the same month last year difficult, particularly for pipeline and deal stage movement.
Report sharing is awkward. Getting the right data in front of the right people requires either paying for additional HubSpot seats or exporting to spreadsheets, both of which create friction and version control problems.
Power BI removes all of these constraints. Once HubSpot data flows into Power BI's data model, you can join it to any other data source, write any DAX calculation, and build dashboards that update automatically and are accessible to the whole team without additional CRM licensing.
How to Connect HubSpot to Power BI: The Recommended Approach
For businesses looking to connect HubSpot to Power BI, GrowthBI recommends a data warehouse architecture using Fivetran as the most reliable and scalable foundation.
Data warehouse as intermediary (the recommended approach)
For businesses with higher data volumes, multiple source systems, or governance requirements, the best architecture involves extracting HubSpot data into a cloud data warehouse (such as Google BigQuery or Azure Synapse), transforming it there, and connecting Power BI to the warehouse rather than to HubSpot directly.
This is more expensive and complex to set up but provides the most reliable, scalable foundation. It is the approach GrowthBI typically recommends for businesses that need to combine HubSpot data with significant volumes of data from multiple other systems. The data engineering work to build that pipeline is a separate investment but produces substantially more robust reporting.
What HubSpot Data Can You Pull Into Power BI?
Once your connection is live, you can pull any data object from HubSpot into Power BI. The most useful for Australian mid-market businesses building sales and marketing dashboards are:
Contacts and Companies: Full contact records including lifecycle stage, lead source, owner, creation date, and any custom properties you have defined in HubSpot.
Deals: Deal stage, close date, amount, owner, associated contact and company, creation date, pipeline, deal source, and custom deal properties. This is the core object for sales reporting.
Activities and Engagements: Calls, emails, meetings, and notes logged against contacts and deals. Useful for sales activity reporting and rep performance analysis.
Marketing Emails and Campaigns: Send volumes, open rates, click rates, and conversions by campaign. Essential for marketing analytics.
Form Submissions and Landing Page Performance: Conversion data from HubSpot forms and landing pages.
Tickets: Customer support tickets if you are using HubSpot Service Hub.
The Dashboards Worth Building From HubSpot Data
The technical connection is the starting point. What creates real value is what you build on top of it. Here are the four dashboards that deliver the most consistent business impact for Australian mid-market businesses using HubSpot.
1. Sales Pipeline Dashboard
The most requested HubSpot Power BI dashboard for sales teams. This gives leadership and sales managers a real-time view of the pipeline with context that HubSpot's built-in reports cannot provide.
Key metrics to include:
Total pipeline value by stage and by owner
Weighted pipeline (deal value multiplied by win probability)
Average deal size and average sales cycle length by source
Pipeline velocity (how fast deals move through stages)
Deals closing this month versus target
Win rate by deal source and by rep
The Power BI advantage here is the ability to filter by any combination of dimensions by product line, by industry, by region, by rep, by time period without those filters being pre-set in HubSpot. A Head of Sales can answer "what is our pipeline coverage for enterprise deals in Victoria" in seconds. More detail on how GrowthBI structures these is covered in the sales analytics service area.
2. Marketing Performance Dashboard
This dashboard answers the question that every marketing team and CFO wants answered: which channels and campaigns are actually generating revenue, not just leads.
To answer it properly, you need to join HubSpot data (deals, contacts, lead sources) with marketing spend data from Google Ads, LinkedIn, or whatever channels you run. Power BI can pull from all of these simultaneously and join them on campaign or channel, producing a blended cost-per-acquisition view that neither HubSpot nor any individual ad platform can provide.
Key metrics to include:
Leads by source (HubSpot original source)
Lead-to-opportunity conversion rate by channel
Cost per lead and cost per closed deal by channel
Marketing qualified lead (MQL) volume and trend
Revenue attributed to marketing by month and quarter
GrowthBI's marketing analytics work typically involves building this blended view as one of the first deliverables, because it is where most businesses find the biggest surprises about where their revenue is actually coming from.
3. Revenue and Forecast Dashboard
This is where HubSpot data gets combined with financial data to give leadership a forward-looking revenue view that neither the CRM nor the accounting platform can produce alone.
The core idea: use HubSpot deal data (deals in late pipeline stages, expected close dates, deal amounts) to project revenue over the next 30, 60, and 90 days. Layer in actual closed revenue from your accounting platform (Xero, MYOB, or QuickBooks) to show actual versus forecast in a single view.
Key metrics to include:
Committed revenue (deals at 90%+ probability closing this quarter)
Best-case revenue (all active pipeline deals)
Actual closed revenue versus target by month
Revenue by customer segment or product line
Forecast accuracy (comparing previous period forecasts to actuals)
This dashboard is typically the most valuable for Finance and operations leaders. It is covered in depth in GrowthBI's financial analytics service area.
4. Sales Rep Performance Dashboard
For sales managers who need to coach their team based on activity and outcomes, not just pipeline. This dashboard makes individual and team performance visible in a way that does not require running five separate HubSpot reports.
Key metrics to include:
Calls, emails, and meetings logged per rep per week
Deals created, deals progressed, and deals closed per rep
Win rate per rep versus team average
Average deal size per rep
Pipeline coverage ratio per rep (pipeline value versus quota)
The combination of activity data (from HubSpot's engagement objects) and deal outcomes makes it possible to identify patterns: which reps are high-activity but low-conversion, which are closing deals faster than average, and where coaching is needed most.
Building the Data Model: How to Structure HubSpot Data in Power BI
The dashboards above are only as reliable as the data model underneath them. Before building any visuals, the data coming from HubSpot needs to be structured correctly in Power BI's data modelling layer.
The key principles for a HubSpot Power BI data model:
Separate your tables by object type. Contacts, deals, companies, activities, and any external data sources (accounting, marketing spend) should each be their own table. Do not flatten everything into one wide table.
Create relationships between tables. In Power BI's data model view, draw the relationships between tables. Deals relate to contacts via the associated contact ID. Deals relate to companies via the associated company ID. Getting these relationships right is what enables cross-table filtering.
Build a date table. All time-based analysis in Power BI relies on a dedicated date table. Create one with columns for date, week, month, quarter, and year, and relate it to any date field you want to filter by (deal close date, deal creation date, contact creation date).
Write your KPI measures in DAX. Calculated measures for win rate, weighted pipeline, average deal size, and conversion rates should be written as DAX measures rather than calculated columns. This keeps the model performant and ensures calculations respond correctly to all filters.
Set up row-level security if needed. If different sales reps should only see their own deals in the dashboard, configure row-level security in Power BI to filter the deals table by the logged-in user's email against the HubSpot deal owner email.
What the Setup Process Looks Like in Practice
For an Australian mid-market business using HubSpot that wants to get a custom Power BI dashboard live, here is what a realistic engagement timeline looks like.
Week 1: Discovery and connection setup
Map the reporting questions you need to answer. Identify which HubSpot objects and properties are relevant. Assess whether additional data sources need to be connected (accounting, ad platforms). Set up the connector and validate that data is flowing correctly.
Week 2: Data model and initial dashboards
Build the data model in Power BI. Create the relationship structure between HubSpot objects. Write initial DAX measures for your core KPIs. Build prototype dashboards covering the most critical reporting need first (usually the sales pipeline dashboard).
Week 3: Review, refinement, and additional dashboards
Present the prototype to the sales or operations team. Gather feedback on what is missing, what needs adjusting, what filters are needed. Build the remaining dashboards based on validated requirements. Set up automated refresh and publish to Power BI Service.
Week 4: Handover and training
Train the team on how to use the dashboards: how to filter, how to interpret the metrics, what each measure represents. Document the data model and any business logic applied to ensure the dashboards can be maintained and extended. For most Australian mid-market businesses, a well-scoped HubSpot Power BI engagement runs four to eight weeks and falls in the medium project range of AUD $15,000-30,000 depending on complexity and number of additional data sources.
Common Mistakes to Avoid
Having helped a number of Australian businesses build Power BI on top of HubSpot, the same issues come up repeatedly.
Poor data quality in HubSpot undermines everything. If deal stages are inconsistently used, close dates are not maintained, or lead sources are not captured correctly, no amount of Power BI work will produce reliable reports. A data quality audit of HubSpot should happen before any dashboard is built.
Building reports before defining the questions. The most common reason dashboards do not get used is that they were built around what data was available rather than what decisions the business needs to make. Start with the three or four questions leadership most frequently asks, and build only what answers those questions.
Flattening data into one wide table. Pulling all HubSpot data into a single flat table seems simpler initially but creates a performance-heavy model that is difficult to extend. Maintaining proper table structure and relationships is worth the upfront effort.
Skipping the training step. A dashboard that the team does not understand does not get used. Budget time for a proper handover session where the metrics are explained and the team can ask questions in context.
Frequently Asked Questions
Does HubSpot have a native Power BI connector?
There is no built-in, first-party connector. GrowthBI recommends connecting HubSpot to Power BI via a data warehouse architecture using Fivetran, which provides the most reliable and scalable foundation.
How often does the HubSpot data refresh in Power BI?
Refresh frequency depends on your Power BI licence and connector setup. Power BI Pro supports up to 8 scheduled refreshes per day. Power BI Premium supports up to 48. For most sales and marketing dashboards, a twice-daily refresh (morning and afternoon) gives teams current enough data without requiring a Premium licence.
Can we combine HubSpot data with Xero in Power BI?
Yes. This is one of the most common combinations for Australian businesses. Power BI can pull deal data from HubSpot and invoice/revenue data from Xero simultaneously, join them on customer or contact identifiers, and produce reports that show actual revenue against CRM pipeline in a single view.
How do we handle data that is missing or inconsistently entered in HubSpot?
Power BI's Power Query transformation layer allows you to clean and standardise data before it reaches the data model. You can handle nulls, standardise text values, fill missing fields, and flag records that do not meet quality thresholds. However, the better long-term solution is fixing data entry practices in HubSpot itself.
Is this something we can do ourselves, or do we need a consultant?
The connector setup and basic reports can be done in-house if you have someone comfortable with Power BI and basic data modelling. The more complex work, building a reliable data model, writing DAX measures for custom KPIs, integrating multiple data sources, and setting up row-level security, typically benefits from a consultant who has done it before. For most Australian mid-market businesses, bringing in a Power BI consultant for the initial build and handing over for maintenance is the most practical approach.
Getting the Most From Your HubSpot Data
HubSpot gives your sales and marketing team a well-organised place to manage relationships and track activity. Power BI turns that activity data into the reporting layer your leadership team actually needs — one that blends CRM data with financial and operational context, updates automatically, and gives everyone a consistent set of numbers to work from.
The investment is justified quickly. A sales team that can see live pipeline coverage, win rates by source, and rep performance in one dashboard spends less time in reporting meetings and more time selling. A leadership team that can see actual revenue against forecast in a single view makes faster and more confident decisions.
If you are using HubSpot and want to understand what a Power BI integration would look like for your Australian business, see GrowthBI's full range of analytics services or reach out for a discovery conversation.


