Salesforce Power BI Integration: Pipeline, Bookings and Cash in One Model
Salesforce knows what sales expects to close. Your accounting system knows what was invoiced and paid. Leadership wants both on one page, and an export to Excel every Monday is not a plan.
Salesforce Power BI integration means connecting your Salesforce org to Power BI so opportunities, accounts and activities land in a model next to invoices, payments and targets from your other systems, refreshed on a schedule with no manual export. Lightray Solutions builds that model, and Edward Pinela, MBA, does the work himself, remotely, inside your own Microsoft tenant.
The first step is a free 30-minute strategy call. After it, a first build is priced as one fixed figure, or you can buy Power BI Flex Support hours, from $2,500 for 20, and use them as needed. If you don't like working with us within the first 4 hours of Power BI work, you get your money back.
“Amazing! Lightray Solutions built us a Power BI dashboard based on my busy restaurant’s quickbooks data that allows me to see my entire business on a daily basis which has been a game-changer! Excellent communication and service!”
— Quinn R., Google review
When does Salesforce data belong in Power BI?
When the question crosses a system boundary. Salesforce's own dashboards are good at pipeline by stage or rep. They struggle once the answer needs data Salesforce doesn't hold: invoiced revenue from accounting, margin from an ERP, targets kept in a spreadsheet, or marketing spend. Power BI is where those sources meet in one model.
Typical triggers are a forecast that never matches booked revenue, a board pack assembled by hand from three exports, or a commission calculation nobody wants to own. If every question you have is answered inside Salesforce, a cleaner org may help more than a second tool; Salesforce CRM setup services covers that work.
Salesforce Objects or Salesforce Reports: which connector should you use?
Usually Objects. Power BI offers two Salesforce connectors. The Reports connector reads a saved Salesforce report, which is convenient, but Microsoft's Salesforce Reports connector documentation states that Salesforce limits it to 2,000 rows. The Objects connector reads tables such as Opportunity and Account directly, without that cap.
Reading objects also keeps the logic in one place. Instead of depending on a report someone in sales may edit, the measures for win rate, pipeline coverage and average deal size live in the Power BI model, written down and tested. The table below compares the two connectors on the points that matter for a build.
| Point | Salesforce Objects connector | Salesforce Reports connector |
|---|---|---|
| What it reads | Salesforce objects (tables) such as Opportunity, Account, Contact | A saved Salesforce report |
| Row limit | No 2,000-row cap; Microsoft names it as the workaround | Limited by Salesforce to 2,000 rows |
| Salesforce API access | Required: API Enabled permission, not available on trial accounts | Same requirement |
| Where business logic lives | In the Power BI model, documented and tested | In the Salesforce report, editable by its owner |
| Suited to | Production models and anything joined to other systems | Quick checks on a small, stable report |
How does Power BI connect to the Salesforce API?
Through Salesforce's API, which has to be switched on for the account Power BI signs in with. Microsoft's Salesforce Objects connector page lists the requirements: the user profile needs the API Enabled permission, trial accounts have no API access, and the session setting that locks sessions to their originating IP address must be off.
Two other points shape the design. The connector requires a supported Salesforce API version, which may need setting explicitly when tables appear to be missing. And Salesforce limits how many queries one account runs at once, counting every app using the API, so busy orgs stage the data in a dataflow and let reports read from there. We recommend a dedicated read-only integration user so access can be audited and revoked without touching anyone's login.
- A Salesforce user with the API Enabled permission, ideally a dedicated integration user
- The IP-locked session setting turned off for that user's sessions
- A supported API version pinned in the query
- Only the fields reports need, since a query with too many fields is rejected
How current will the numbers be?
As current as your refresh schedule, which is honest about what the integration is: imported data, not a live feed. According to Microsoft's guidance on data refresh in Power BI, a semantic model on shared capacity can be scheduled up to eight times a day, and up to 48 times on Premium, Premium Per User or Fabric capacity.
For most sales teams, a refresh before the morning stand-up and another after lunch is plenty; pipeline reviews rarely need minute-by-minute data. If a team genuinely needs hourly figures, that changes the licensing, and we would say so on the strategy call rather than after the build.
Which Salesforce reports do teams build first in Power BI?
The ones that need a second system. Bookings against invoiced revenue comes first for most firms, because it settles the argument between sales and finance. Joining opportunities to invoices needs a shared key, usually the account and an order or contract number, which is agreed and tested during the first week. For NetSuite users, NetSuite Power BI integration covers the ERP side of that join.
Access matters as much as content. With row-level security in Power BI, each rep or regional manager sees only their own territory, mirroring how ownership already works in Salesforce, while leadership sees everything in the same report.
- Bookings vs invoiced revenue by month, account and product
- Pipeline coverage against quota, by rep and region
- Win rate and sales cycle length by lead source
- Forecast accuracy: what was committed last quarter against what closed
What does a Salesforce to Power BI build cost, and how does it run?
A first build is quoted as a fixed price once Edward has seen the org and the second system, and its size depends mostly on how many objects and custom fields are involved and how clean the join to accounting is. Later reports draw on prepaid Flex Support hours at $100 to $125 each, and unused hours never expire.
The work runs over screen share in four steps: access and data review, the model and its tie-out to Salesforce's own totals, the report pages, then handover with a scheduled refresh and a recorded walkthrough. Lightray holds a 4.9 rating on Google, and Edward brings 20+ years and 200+ delivered projects. The wider service is described under Power BI consulting services.
Further reading: Microsoft Learn — Salesforce Objects connector.
Ready to see pipeline and revenue side by side?
Book a free 30-minute call with Edward Pinela, MBA. You get an honest read on what to fix first — and if we are not the right fit, you will hear that on the call.
Frequently asked questions
How much does Salesforce Power BI integration cost?
A first build gets a fixed quote after the free strategy call; the main drivers are the number of objects and custom fields and how cleanly Salesforce accounts match the accounting system. Ongoing additions use Flex Support hours, from $2,500 for 20. Power BI licences are billed by Microsoft.
How long does a first integration take?
The quote gives the timeline. Most of the variable time goes into agreeing definitions, such as when an opportunity counts as booked, and matching accounts to invoices. Getting API access and a read-only integration user set up on day one removes the most common delay.
Will you need admin access to our Salesforce org?
No. Power BI only reads data, so a dedicated integration user with read access to the needed objects and the API Enabled permission is enough. Your Salesforce administrator creates it, and everything else happens remotely by screen share inside your Microsoft tenant.
What do we need to provide?
A Salesforce administrator who can create the integration user, access to the second system such as accounting or ERP, the spreadsheets or exports people use today, and an hour with the sales and finance owners to agree what booked, won and invoiced mean.
Our Salesforce data is messy. Should we fix it first?
Not necessarily. The data review shows which gaps actually affect the reports, such as missing close dates or duplicate accounts, and those get fixed in Salesforce at the source. Cosmetic issues can wait. If the org needs a wider cleanup, that is a separate Salesforce setup project.
You Won’t Get Handed Off to Junior Staff.
At most consulting firms, the senior person who sold you shows up for the kickoff — then you get handed to a team of juniors learning on your dime. That’s not how we work.
When you hire Lightray Solutions, you work directly with Edward Pinela, MBA — a principal consultant with 20+ years of experience across Power BI, web development, SEO, and CRM systems. Edward architects every engagement personally, stays involved through delivery, and answers his own phone.
Read Edward’s Full Bio“Mid-market companies deserve senior-level expertise without paying enterprise-agency prices. That’s the gap Lightray fills.”
Simple. Transparent. Proven.
No black-box processes. No endless discovery phases. A straightforward three-step approach designed to deliver measurable results fast.
Discovery Call
Free 30-minute strategy session where we assess your data landscape, website, marketing — and where AI would genuinely pay off versus where it's hype.
Free · No ObligationCustom Roadmap
You receive a tailored plan with clear deliverables, realistic timelines, and expected ROI. You approve every detail before we start.
Fixed Scope · Clear PricingMeasurable Results
We execute, measure, and optimize. You get dashboards, regular check-ins, and full visibility — so you always know the impact.
Data-Driven · TransparentGet a clear plan in one free call.
Tell us what you are trying to fix. Your request goes to Edward Pinela, MBA — the principal consultant who would do the work — and you hear back within 4 business hours.
Prefer to call? +1 (714) 872-9606