Xplan manages your clients. Midwinter models their futures. Power BI answers the question neither platform was built to ask: how is your practice actually performing? This is the integration architecture that connects all three — and the dashboards that make the investment visible from day one.
Most financial advice practices are data-rich and insight-poor. They have years of client records in Xplan, cashflow models in Midwinter, and revenue data scattered across a practice management system, accounting software, and a collection of Excel workbooks that only one person in the office fully understands. The information to run a genuinely data-driven practice is already there. The gap is the intelligence layer that sits above the platforms — and that is exactly what a well-designed Power BI integration delivers.
This is not a theoretical exercise. Connecting Xplan and Midwinter data to Power BI is a practical, implementable project for practices of any size. This article explains the architecture, the key reports to build, and the common pitfalls that derail these integrations before they deliver value.
The Platform Data Problem
Xplan and Midwinter are excellent tools for what they were built to do. Xplan manages your client records, SOAs, review schedules, and compliance documentation. Midwinter models retirement projections, cashflow scenarios, and strategic advice outputs. Neither platform was designed to be an analytics layer — and that is not a criticism; it is simply not what they do.
The result is that answering basic business questions — which advisers are generating the most FUA growth, which client segments have the highest fee-for-service revenue, which review backlog is creating the most compliance risk — requires manual extraction, reconciliation, and formatting. For a practice principal, this is at best a monthly exercise. In fast-moving advice environments, month-old data is not the basis for good decisions.
What Xplan and Midwinter Expose
Xplan exposes data via its API and through scheduled data exports in CSV and XML formats. The most useful data entities for practice analytics are: client demographics and segmentation, portfolio and product holdings, FDS generation dates and status, review dates and completion status, SOA status and advice type, and fee revenue by client and adviser. Xplan's reporting module can produce many of these as scheduled exports, which then serve as the input to your integration pipeline.
Midwinter's data is typically accessed via export from its modelling environment or, in larger implementations, via database-level access to the Midwinter SQL database. The key data for integration is cashflow modelling outputs by client, strategic advice assumptions, and projected retirement balances — data that, combined with Xplan's actual holdings, allows you to compare modelled vs actual outcomes across your client book.
Xplan stores your client history. Midwinter models your cashflows. Power BI answers the question neither platform was built to ask: how is my practice actually performing?
Building the Integration Architecture
The standard architecture for a Xplan-Midwinter-Power BI integration uses a three-layer model. The extraction layer pulls data from both platforms on a scheduled basis — typically nightly — via API calls or automated file exports. The transformation layer, implemented in Power Query or a lightweight staging database, cleans, deduplicates, and joins the data across systems. The presentation layer in Power BI applies the business logic — revenue calculations, compliance status flags, segment definitions — and renders the dashboards.
For practices without a dedicated IT resource, Microsoft's Power Platform provides a practical low-code path: Power Automate handles the scheduled extractions and file movements, Dataflows in Power BI handle the transformation, and the Power BI service handles scheduling, refresh, and distribution. This stack is deployable by a data-literate practice manager with support from an external data partner for the initial build.
Key Reports Every AFSL Holder Should Have
The first dashboard to build is the FDS compliance tracker — a real-time view of which clients are due for their annual fee disclosure statement, which have been issued, and which are overdue. This single report, built on Xplan data, eliminates the most common source of ASIC compliance risk in financial advice practices and pays for the integration project by itself.
The second priority is the practice revenue dashboard: fee income by adviser, by client segment, and by advice type — tracked monthly against budget. The third is the review pipeline tracker: upcoming client reviews, adviser capacity, and review backlog by risk tier. With these three dashboards, a practice principal has a real-time view of compliance exposure, revenue trajectory, and operational capacity that previously required a full-time practice manager to assemble manually each week.
Common Integration Pitfalls
The most common failure mode in Xplan-Power BI integrations is data quality debt. Xplan records that were manually entered, inconsistently formatted, or never cleaned accumulate over years of use. When this data is extracted and loaded into a reporting layer, inconsistencies surface as errors in aggregated metrics — different spellings of product names, duplicate client records, fee structures recorded in incompatible formats. Resolving data quality issues is always part of the integration project and should be scoped explicitly, not treated as an afterthought.
The second pitfall is building too many reports too quickly. Practices that try to replicate every manual report they currently produce in Power BI end up with a cluttered, low-adoption dashboard environment. The better approach is to identify the three to five metrics that the principal and senior advisers check most frequently, build those first, and add to the model incrementally as adoption grows. A dashboard that is used daily is worth ten that are viewed once at launch.
The goal is not to replace your platforms. It is to build the intelligence layer that sits above them — surfacing patterns your CRM was never designed to reveal.
Ready to apply these patterns in your stack?
Book a free 45-minute AI readiness call with the Precision Data Partners team.
Book a Free Audit
