Connect Salesforce to Power BI

Power BI connects to Salesforce out of the box: the Salesforce Objects connector reads standard and custom objects, and the Salesforce Reports connector pulls existing Salesforce reports. These are ideal for a fast first dashboard. For larger data volumes, full history or reliable pipeline analytics, the Salesforce REST and Bulk APIs or a warehouse-backed pipeline are the more durable choice. The decision hinges on your data volume, how much history you need, and whether you must trend the pipeline over time.

Native connectors vs the API

The Salesforce Objects connector lets you select objects such as Opportunity, Account, Lead and Contact, including custom objects, and is the most flexible native option. The Salesforce Reports connector is the quickest route if your reporting already lives in Salesforce reports, but it inherits Salesforce's report row caps and exposes only what the report contains.

The Salesforce API (REST for queries, Bulk for large extracts) gives you full control and scales past the native connectors' limits, at the cost of building and maintaining the extraction. A warehouse-backed pipeline lands Salesforce data in a database you own via Data Integration and Warehousing, which is the right pattern for large orgs, multi-year history and CRM blended with finance or marketing.

Pipeline and funnel KPIs

Once data is in, build the measures that move deals. Useful Salesforce KPIs include open pipeline by stage, weighted pipeline, win rate, average deal size, sales cycle length, conversion rate at each funnel stage, pipeline coverage against quota, and forecast versus actual. Model these on a clean date dimension and a consistent stage hierarchy so the funnel reads the same across teams.

The hard part is time. Salesforce stores current state, so a snapshot of the pipeline today tells you nothing about how it looked last month. To trend pipeline and measure stage movement you either query Salesforce's opportunity field-history objects or, more reliably, capture daily snapshots into a warehouse. If pipeline trends matter to your board, plan for snapshots from day one.

Limits to design around

• API request limits. Salesforce caps daily API calls per org; aggressive refresh or many DirectQuery interactions can exhaust them. Prefer Import and a sensible schedule.
• Report row caps. The Reports connector returns only the rows the report returns, often a few thousand; switch to Objects or the API for more.
• Field-level security. The connecting user only sees fields and records their profile allows, so a restricted account can quietly omit data.
• Custom field naming. API names differ from labels and include suffixes; document the mapping so the model stays readable.
• Refresh cadence. A Pro workspace allows up to eight refreshes a day and Premium or Fabric up to 48; align this with API limits rather than maxing it out.

Choosing the right route

If you want a dashboard from existing Salesforce reports this week, the native connectors are the obvious start. If you have a large org, need historic pipeline trends, or want CRM joined to revenue and marketing data, invest in an API pipeline into a warehouse. As a rough UK guide, a scoped dashboard build starts from £6,000 with typical projects at £8,000–£14,000, and senior Power BI day rates run roughly £400–£850/day (as of 2026, confirm current pricing). Decide your snapshot strategy before building, because retrofitting history is far harder than capturing it from the start. For marketing-side analytics, the same principles apply when you connect HubSpot to Power BI.

A Trusted Numbers Review reviews your Salesforce data, agrees the pipeline and funnel definitions and recommends the right connection method. Book one to turn CRM data into decisions you can trust.