This guide explains how to connect Power BI to Salesforce using Metrica Power BI Connector for Salesforce. It covers the setup process inside Salesforce, how data sources are defined, and how Salesforce data is imported into Power BI.
The focus is on a structured approach to Salesforce Power BI integration, where datasets are prepared in Salesforce before being used in Power BI. This becomes important for teams working with larger datasets, multiple reports, or ongoing reporting requirements.
Why Businesses Use Power BI to Analyze Salesforce Data
Salesforce Is Operational. Power BI Is Analytical.
Salesforce is built to run sales and customer processes. It helps teams manage leads, accounts, opportunities, activities, and day-to-day workflow. That is its job.
But once the question changes from managing records to analyzing performance, the requirements change too. Teams need to compare time periods, combine datasets, standardize metrics, and build reports that are not limited to one operational view.
That is where Power BI becomes relevant. It is used to analyze Salesforce data in a way that supports broader reporting and decision-making.
Salesforce Reporting Stops at the Operational Layer
Salesforce can show what is happening in the pipeline, but many teams need more than operational visibility. They need to answer questions such as:
- how pipeline quality changes over time
- where conversion slows down across stages
- how different teams, regions, or segments compare
- how Salesforce data relates to finance, support, or marketing data
These are analytical questions, not just CRM questions. They usually require more flexible modeling and reporting than the operational system is designed to provide on its own.
Power BI Turns Salesforce Data into Cross-Functional Reporting
This is why businesses use Power BI to analyze Salesforce data. It allows teams to move from record-level tracking to broader business reporting.
A Salesforce Power BI integration is typically used when companies need:
- deeper pipeline and revenue analysis
- reporting across multiple teams or business units
- consistent metrics across dashboards
- a way to combine Salesforce with other business data sources
So the reason is not simply that Salesforce contains important data. The reason is that Salesforce data often needs a reporting layer built for analysis, comparison, and scale.
How to Set Up a Salesforce Power BI Integration: Step by Step
There are different ways to connect Salesforce to Power BI, but they are not designed for the same reporting needs. Some are enough for simple dashboards. Others are built for larger datasets, repeatable exports, and reporting that has to stay consistent across teams.
Metrica Power BI Connector for Salesforceis a Salesforce AppExchange app for Salesforce data migration to Microsoft Power BI through reusable data sources created inside Salesforce. It is designed for teams that need more control over how data is selected, structured, accessed, and reused in reporting.
That includes creating separate data sources for different use cases, avoiding the 2,000-row Salesforce Reports limit, supporting incremental refresh for large datasets, and keeping access aligned with standard Salesforce permissions.
Metrica Power BI Connector for Salesforce is installed in Salesforce, where you create the data source and prepare the export for Power BI. After that, the data is imported into Power BI.
The main steps are:
Step 1. Install Metrica Power BI Connector for Salesforce
Install Metrica Power BI Connector for Salesforce in your Salesforce instance.
You can do this via AppExchange or direct package installation. The installation follows the standard Salesforce package flow.
Step 2. Configure Salesforce Site and Connected App
After installation, you need to configure Salesforce for API access.
- Go to Setup → Sites
- Create a new Site (or use an existing one)
- Activate the site and copy the Site URL
- Open Public Access Settings
- Add Apex class:
metrica_powerbi.OAuthProxy
Next, configure the Connected App:
- Go to Setup → App Manager / External Client Apps
- Create a new app
- Enable OAuth
- Set Callback URL:
[Your Site URL]/services/apexrest/metrica_powerbi/OAuthProxy/callback - Add OAuth scopes:
- API access
- Refresh token access
- Enable required flows (Authorization Code + PKCE)
- Save and copy the Consumer Key
Step 3. Configure Connector Settings in Salesforce
- Go to Setup → Custom Settings
- Find Power BI Key
- Create a new record
- Fill in:
- Client ID (Consumer Key)
- Base Site URL
- Base Salesforce URL
- Save changes
Wait a few minutes for activation, then open the connector and click Authorize with Salesforce.
Step 4. Set Permissions for Users
Make sure users have access to:
- the Metrica Power BI Connector app (via Profiles or Permission Sets)
- Salesforce objects and fields they need
Metrica uses standard Salesforce permissions, so users will only see data they already have access to.
Step 5. Create an Access Token
- Open Power BI Connector app in Salesforce
- Go to Access Tokens
- Click Create Token
- Enter a name (e.g., “Power BI”)
- Click Create
- Copy the token immediately (it will not be shown again)
Step 6. Create a Data Source
- Go to Data Sources → Create Data Source
- Enter name and description
- Select Salesforce objects
- Choose required fields
- Apply filters (e.g., Created Date, Owner)
- Review relationships (ERD view if needed)
- Save the data source
You can create unlimited data sources for different use cases.
Step 7. Copy Power Query Script and Prepare Power BI
- Open the created data source
- Copy the generated Power Query script
- Open Power BI Desktop
- Create a new report
- Go to Get Data → Blank Query
- Open Manage Parameters → New Parameter
- Create parameter:
- Name: metricaToken
- Value: paste your token
Step 8. Import Data into Power BI
- Open Advanced Editor in Power BI
- Replace existing code with the copied script
- Click Done
- If prompted:
- Select Anonymous authentication
- Click Connect
Step 9. Add Required Tables and Load Salesforce Data
- In query results, find the required Salesforce objects
- Right-click Table → Add as New Query
- Rename queries properly
- Repeat for all needed objects
- Click Close & Apply
- Power BI will load data
- Salesforce dataset is ready for Power BI reporting
Step 10. (Optional) Configure Incremental Refresh
For large datasets:
- set up incremental refresh in Power BI
- load only new or updated data
For a complete overview of features, setup options, and additional capabilities, see the full Power BI Connector for Salesforce Documentation.
After these steps are completed, Salesforce data is available in Power BI based on the structure defined in the Metrica Power BI Connector. Instead of rebuilding datasets separately in each report, teams work from a data source created in Salesforce with selected objects, fields, and filters already in place.
This makes the setup easier to repeat across reports and easier to manage over time. It also gives teams more flexibility, since Metrica Power BI Connector supports unlimited data sources for different reporting needs.
Use Cases for Analyzing Salesforce Data in Power BI
Build Pipeline Reporting That Is Not Limited to CRM Views
Salesforce is where pipeline is managed, but teams often need to analyze it in ways that go beyond the standard operational view. In Power BI, they can look at pipeline by stage, owner, region, segment, or product line, compare current pipeline with previous periods, and track how deal volume and value change over time.
This is especially useful when the goal is not just to see what is currently open, but to understand pipeline quality, movement, and risk. With Metrica Power BI Connector, teams can prepare a separate data source for pipeline reporting and keep that dataset consistent across multiple reports.
Analyze Conversion and Sales Process Efficiency
One of the most common reasons to move Salesforce data into Power BI is to understand how opportunities progress through the funnel. This includes stage-to-stage conversion, drop-off points, average time in stage, and differences between teams or market segments.
That kind of analysis is difficult to manage when every report has its own dataset logic. A defined data source makes it easier to build repeatable reporting around the same sales process metrics.
Build Revenue and Forecast Reporting on Top of Salesforce Data
Salesforce often contains the core data behind expected revenue, open pipeline, closed deals, and sales targets. Power BI is used when that data needs to be analyzed over time, compared across business dimensions, or combined with other planning inputs.
This is relevant for companies that want to compare forecasted and actual results, monitor revenue by sales team or geography, or build leadership reporting that goes beyond day-to-day CRM usage.
Combine Salesforce Data with Other Business Systems
A major reason to use Power BI with Salesforce is that Salesforce rarely answers the full reporting question on its own. Businesses often need to analyze CRM data together with finance, support, product, or marketing data.
This allows teams to build reporting that connects opportunity data with invoicing, customer support load, campaign performance, or account expansion trends. In that setup, Salesforce remains the commercial source of truth, while Power BI becomes the place where cross-functional analysis happens.
Create Separate Reporting Layers for Different Teams
Not every team needs the same Salesforce dataset. Sales leadership may need opportunity and activity reporting. Finance may need revenue-oriented views. Support or customer success teams may need account-level context tied to other systems.
This is where Metrica Power BI Connector unlimited data sources become practical. Instead of forcing all reporting into one large dataset, teams can create separate data sources for different analytical needs and keep each one focused on its own purpose.
Support Ongoing Reporting, Not Just One-Off Dashboards
The strongest use case for Metrica Power BI Connector is not a single dashboard. It is a reporting setup that needs to be reused, refreshed, and maintained over time. When multiple reports depend on the same Salesforce data, stability and consistency matter more than just getting the connection to work once.
In that case, Metrica Power BI Connector helps turn Salesforce Power BI integration into a repeatable reporting workflow rather than a collection of isolated report setups.
Conclusion
Connecting Power BI to Salesforce is not difficult. Making that connection work as reporting grows is where most teams run into problems.
At small scale, direct connections are enough. As soon as reporting becomes shared, repeated, and tied to decision-making, issues appear: datasets diverge, logic is duplicated, and refresh becomes unreliable.
Metrica Power BI Connector for Salesforce addresses this at the level where those problems actually happen. It gives teams control over what data is exported, how it is structured, and how it is reused across reports.
That is what makes the difference. Not the connection itself, but how consistently that connection can be used over time.