How to connect QuickBooks to Power BI

There is no single right way to connect QuickBooks to Power BI, only the route that matches how much data you need and how often it has to refresh. QuickBooks Online exposes a cloud API that third-party tools can read; QuickBooks Desktop keeps its data in a local company file, which changes everything downstream. The three routes below run from fastest-to-start to most-robust, and each one ends in a source Power BI already supports, from the Excel workbook connector (opens in new tab) to the ODBC connector (opens in new tab).

What happened to the QuickBooks Online connector?

Power BI used to offer a built-in QuickBooks Online connector under Get Data. It no longer appears in Microsoft’s list of Power Query connectors (opens in new tab), and the address of its old documentation page now redirects to that general list. Do not start a new report on it; use one of the three routes below instead.

If you have an existing report that was built on the old connector, check whether it still refreshes before your next close, and plan its move to an export, a sync tool, or a warehouse. The measures and visuals usually survive the move; what changes is the query layer that feeds them, so the rework is mostly in Power Query and the data model rather than the report pages.

Can Power BI connect to QuickBooks directly?

Not natively any more, for either edition. QuickBooks Online data reaches Power BI through an Excel or CSV export, a third-party ODBC driver or sync tool, or a warehouse; QuickBooks Desktop, which has no cloud API, uses the same three routes. Which one you pick decides how much detail and history you can report on and how much manual work each refresh costs you.

The deeper trade-off is between speed of setup and depth of data. An export is running in minutes but has to be repeated by hand every period. A warehouse takes real setup but gives Power BI one fast, complete source, so a multi-entity group with several years of transactions can model everything in one place. Match the route to the reporting you actually need before you build a single visual.

Route 1: Excel or CSV exports through Get Data

Run the reports you need in QuickBooks — profit and loss, general ledger detail, AR aging, customer and item lists — and export them to Excel or CSV. In Power BI Desktop, choose Get Data, pick Excel workbook or Text/CSV, and load the files. Keep each export in the same shape and the same folder, and later exports refresh into the same model.

It works for both QuickBooks Online and Desktop and needs no extra tooling, which makes it the fastest way to a first dashboard. The limit is the human step: someone has to run the exports every period, and a changed column or a missed month quietly breaks the numbers. For a single company that reviews a monthly P&L, cash position, and AR aging, it is often enough. When the manual step starts to hurt, move up to a sync tool or a warehouse.

Route 2: a third-party ODBC driver or sync tool

A third-party ODBC driver or managed sync service sits between QuickBooks and Power BI. A driver lets Power BI read QuickBooks through its ODBC connector; a sync service copies a much wider set of tables on a schedule into a database Power BI reads. For QuickBooks Desktop, the tool reads the local company file so the report is never tied to one person’s export.

You trade a subscription and one more component to monitor for far more coverage than exports, plus scheduled refreshes. It is the middle ground: more setup than a spreadsheet, far less than a full warehouse, and enough detail for most operating dashboards. Choose it when manual exports can no longer keep up but you do not yet need a warehouse-grade history.

Route 3: a data warehouse

The most durable route stages QuickBooks data into a SQL or cloud warehouse through an ETL pipeline, then points Power BI at the warehouse. Because the report reads from a database rather than from QuickBooks itself, refreshes are fast, history is kept as long as you want, and you can combine several companies or blend QuickBooks with other systems in one model.

This is the right architecture for a multi-entity group, line-level transaction analysis, or any reporting that has to survive a QuickBooks upgrade or migration. It is genuine engineering, so it is overkill for a single small company, but it is the route that takes QuickBooks out of every report refresh. We build these pipelines as a service, and if a QuickBooks move is also on the horizon, our Excel and legacy BI migration work pairs naturally with standing up the warehouse.

Which route should you choose?

Start from the reporting, not the tool. One company with a monthly P&L review can live on exports; scheduled refresh, broader tables, or a Desktop file point to an ODBC driver or sync tool; line-level detail, multiple entities, or years of history call for a warehouse. Whichever route you take, the value is in the model on top — a clean chart of accounts, tested measures, and the P&L, cash, and AR views your team actually reads. That modeling is the same data model and DAX discipline behind every build.

If you would rather not wire any of this yourself, we can do it for you: our done-for-you QuickBooks Power BI dashboard build picks the right route for your edition, sets up the export, sync, or pipeline, and delivers the finished P&L, cash-flow, and AR reports. You can see the process and pricing on our how it works page.