QuickBooks to Power BI in 2026
QuickBooks to Power BI in 2026: rebuild after Microsoft's connector retirement
Microsoft no longer supports the QuickBooks Online Power BI connector after March 2026. Datplan provides a different route: authorised Intuit pulls, local accounting tables and stable files for a Power BI model you control.
Reviewed and updated 5 September 2026
What should replace the retired QuickBooks Online Power BI connector?
There is no universal drop-in replacement. Preserve the existing report, identify every table, relationship and measure it depends on, choose a current data-access route, rebuild against that route, then reconcile the new report before retiring the old connection. Datplan is a scheduled local-file option, not a native connector.
Current Microsoft position
The QuickBooks Online connector is no longer a supported Power BI route
Microsoft's Power BI documentation states that the QuickBooks Online connector is not supported after March 2026, that new connections cannot be created, and that existing connections may stop working. A replacement should therefore be designed as a migration rather than an assumption that the old query can simply be redirected.
Not a drop-in replacement
Datplan has its own accounting grains, file names and refresh stages. Map the old model deliberately, then validate the replacement against QuickBooks before removing the previous report path.
Migration checklist
Protect the working report while you rebuild its data layer
The safest migration keeps old and new paths side by side until the replacement is reconciled.
- Inventory the old modelRecord its queries, transformations, relationships, measures, report periods and refresh dependencies.
- Classify every measure by grainSeparate provider financial reports, documents, document lines, payments, ageing and inventory questions.
- Build the new source path separatelyConnect the authorised QuickBooks company in Datplan and create a clean stable export folder.
- Rebuild Power Query inputsPoint new queries to the prepared files without changing the old production model.
- Recreate relationships and measures deliberatelyDo not assume a previous connector table maps one-to-one to a Datplan table.
- Reconcile the resultCheck P&L, balance-sheet and selected transaction totals across defined periods before switching users.
- Retire the old path only after acceptanceKeep evidence of the comparison and the date the replacement became authoritative.
Accounting grain
Use QuickBooks financial reports for statement KPIs, not document-line substitutes
Datplan keeps provider-report financial summaries separate from documents, lines, payments, ageing and inventory because they do not represent the same row-level event.
| Question | Starting grain | Risk if substituted |
|---|---|---|
| Profit & Loss or Balance Sheet | Provider-report Financial Summary | Document or product-line totals may not reproduce the provider's statement logic. |
| Invoice/bill analysis | Document | Joining to many lines can repeat header-level amounts. |
| Product or item detail | Document lines / inventory | Line-level facts answer a different question from statement totals. |
| Cash settlement | Payments | Payment timing is not automatically the same as recognised income or expense. |
| Receivables/payables | Ageing | Reconstructing ageing from unrelated facts can change point-in-time semantics. |
Datplan local-file route
Fits teams that want scheduled reporting snapshots, local source-data control and a visible file handoff to Power BI Desktop.
- Authorised QuickBooks pulls
- Separate accounting grains
- Stable CSV/JSON and BI exports
- Local review and reconciliation
When another route may fit better
A live or hosted connector may be the better fit when Power BI needs a continuously available endpoint, broad shared infrastructure or DirectQuery-like behaviour.
A custom API pipeline may fit when an engineering team wants to own the full integration and monitoring stack.
A QuickBooks migration is complete only when the numbers are reconciled
Connector retirement is a technical trigger, but accounting acceptance is a data question. Compare a defined P&L period, a populated balance-sheet date and selected transaction populations. For a populated balance sheet, the basic accounting equation must still hold: Assets = Liabilities + Equity.
Also record the QuickBooks company, reporting period, Datplan run time and Power BI refresh time so a later reviewer can reproduce the comparison rather than relying on a screenshot of one headline figure.
Choose the replacement architecture
Connector retirement does not mean every business needs the same replacement
| Replacement route | Use it when | Watch for |
|---|---|---|
| Hosted/live connector | Power BI needs a continuously available endpoint or vendor-managed connectivity. | Hosted processing, service dependency, pricing and the vendor's data model. |
| Cloud warehouse | You need many sources, shared transformations and centrally managed access. | Additional infrastructure, administration and another persisted copy of finance data. |
| Custom Intuit API pipeline | An engineering team needs bespoke transformations or operational control. | OAuth, pagination, query limits, schema changes, monitoring and accounting reconciliation. |
| Datplan local files | Periodic finance reporting is sufficient and you want the source reporting dataset prepared on Windows. | The Power BI semantic model, service gateway/storage and final measures remain your responsibility. |
Refresh control
Do not let a successful Power BI refresh hide an old QuickBooks extract
A Power BI refresh can succeed against yesterday's files. Treat the Datplan source run, file publication and Power BI refresh as three different timestamps. Users should know which QuickBooks period the dashboard actually represents.
If the source pull fails, preserve the previously valid reporting snapshot rather than presenting a partial replacement as current data.
Minimum acceptance evidence
- A defined P&L period compared with QuickBooks
- A populated balance sheet at a defined date
- Assets = Liabilities + Equity on the accepted balance-sheet result
- Selected invoice/payment populations traced to source records
- The new refresh path run twice without changing file contracts
- The previous connector/report retained until the comparison passes
Compare alternatives
Need a broader cloud integration platform instead?
Datplan is a focused reporting workflow. If your requirement is hundreds of data sources and many cloud destinations, compare it with Coupler.io before choosing.
See Datplan with real reporting data—without connecting a live account
The Windows app is free to download and includes Datplan Demo data, so you can test sync, dashboards, reporting grains and exports first.