Migrating Access Reports to Power BI
Access reports are powerful but static. Power BI replaces them with interactive dashboards that refresh automatically. Here is how to make the transition without losing your reporting logic.
Access reports are one of the platform's genuine strengths. Grouped summaries, calculated totals, conditional formatting, mailing labels, invoices — Access can produce polished printed output that takes real skill to build.
But Access reports have a fundamental limitation: they are static snapshots. You run the report, you get the data as of that moment, and you print or export it. There is no interactivity, no drill-down, no automatic refresh.
Power BI replaces static reports with interactive dashboards that connect directly to your data and update automatically. The transition requires learning a new tool, but the payoff — reports your team can explore rather than just read — is significant.
What Maps and What Does Not
Before diving into the how, it helps to understand what translates directly and what requires rethinking.
What maps well:
- Grouped summaries with subtotals → Power BI matrix visuals
- Bar and line charts → Power BI bar and line charts (more interactive)
- Calculated fields based on table data → DAX measures
- Filtered reports (parameter queries) → Power BI slicers and filters
- Tabular detail reports → Power BI table visuals
What requires rethinking:
- Pixel-perfect printed layouts → Power BI is not designed for print; use paginated reports (Power BI Report Builder) for invoices, labels, and print-formatted output
- Subreports → separate visuals on the same page, or drill-through pages
- Access-specific formatting (conditional formatting based on VBA) → DAX-based conditional formatting
What Power BI does that Access cannot:
- Interactive filtering — click a bar in a chart to filter all other visuals on the page
- Automatic data refresh — connect to a live data source and the dashboard updates on a schedule
- Mobile-optimized layouts
- Sharing via browser — no Access installation required
Connecting Power BI to Your Data
Power BI Desktop (free download) connects to dozens of data sources. For Access migrations:
If you have migrated to SQL Server:
- Get Data > SQL Server
- Enter your server name and database
- Select the tables or views you need
- Load or transform the data
If you are still on Access (pre-migration reporting):
- Get Data > Access Database
- Browse to your
.accdbfile - Select the tables and queries to import
If you are using Dataverse:
- Get Data > Dataverse
- Sign in with your Microsoft 365 account
- Select your environment and tables
For live reporting, use DirectQuery (data stays in the source, queries run on demand) or Import (data is copied into Power BI and refreshed on a schedule). Import is faster for most reporting scenarios; DirectQuery is better when you need real-time data.
Recreating Grouped Summary Reports
The most common Access report pattern: group records by a category, show detail rows within each group, and display subtotals at the group level.
In Power BI, this becomes a Matrix visual:
- Insert a Matrix visual on the report canvas
- Drag your grouping field (e.g., Category, Region, SalesPerson) to the Rows well
- Drag your date or secondary grouping to the Columns well (optional)
- Drag your measure (Sales Amount, Order Count) to the Values well
The matrix automatically calculates subtotals and grand totals. You can expand and collapse groups interactively — something Access reports cannot do.
Adding calculated totals with DAX:
DAX (Data Analysis Expressions) is Power BI's formula language. It replaces the calculated fields and running totals you built in Access reports.
-- Total Sales measure
Total Sales = SUM(Orders[TotalAmount])
-- Average Order Value
Avg Order Value = AVERAGE(Orders[TotalAmount])
-- Year-over-year growth
YoY Growth =
VAR CurrentYear = [Total Sales]
VAR PriorYear = CALCULATE([Total Sales], SAMEPERIODLASTYEAR(Calendar[Date]))
RETURN DIVIDE(CurrentYear - PriorYear, PriorYear, 0)
-- Running total
Running Total =
CALCULATE(
[Total Sales],
FILTER(
ALL(Calendar[Date]),
Calendar[Date] <= MAX(Calendar[Date])
)
)
DAX measures are reusable across all visuals in the report — define once, use everywhere.
Recreating Parameter-Based Reports
Access parameter queries prompt the user for input (a date range, a customer name) before running. In Power BI, slicers replace parameters.
A slicer is a visual that filters other visuals on the page:
- Insert a Slicer visual
- Drag your filter field (e.g., OrderDate, Region, Status) to the Field well
- Format it as a date range picker, dropdown, or list
When a user selects a value in the slicer, all other visuals on the page filter automatically. Multiple slicers interact — selecting a region and a date range filters to that combination.
For more complex filtering (e.g., "show only orders above a threshold the user specifies"), use Power BI's What-If parameters to create a numeric slicer that feeds into a DAX measure.
Conditional Formatting
Access reports use conditional formatting rules to highlight values — red for negative numbers, green for targets met. Power BI has equivalent functionality, and it is more powerful.
To add conditional formatting to a table or matrix:
- Select the visual
- In the Format pane, find the field you want to format
- Click the conditional formatting icon (fx)
- Choose Background color, Font color, or Data bars
- Set rules based on field values or measures
You can also use DAX to return a color value:
Status Color =
IF([Total Sales] >= [Sales Target], "#2E7D32", "#C62828")
Then use this measure as the conditional formatting source for a visual.
Paginated Reports for Print-Formatted Output
Power BI's standard reports are designed for screen interaction, not print. For invoices, statements, mailing labels, and other pixel-perfect print output, use Power BI paginated reports (built with Power BI Report Builder, a free download).
Paginated reports are the closest equivalent to Access reports in terms of layout control:
- Precise control over page layout and margins
- Grouping, subtotals, and running totals
- Subreports
- Export to PDF, Word, Excel
- Parameters that prompt the user before running
The learning curve is similar to Access report design — if you are comfortable with Access reports, paginated reports will feel familiar.
Distributing Reports
Access reports are distributed by sharing the database file or exporting to PDF. Power BI reports are distributed through the Power BI service (cloud):
- Publish your report from Power BI Desktop to the Power BI service
- Share the report with specific users or groups
- Users view it in a browser — no Power BI Desktop required
- Set up automatic data refresh (daily, hourly, or near-real-time)
This eliminates the "email the PDF every Monday" workflow. The report is always current, always accessible, and always interactive.
Licensing note: Viewing Power BI reports requires a Power BI Pro license ($10/user/month) or Power BI Premium capacity. Power BI Desktop is free for building reports; the service requires licensing for sharing.
A Practical Migration Approach
Start with your most-used reports — the ones people run every week. Recreate them in Power BI and run them in parallel with the Access versions for a month. When users confirm the Power BI versions are accurate and they prefer the interactivity, retire the Access versions.
Save the complex print-formatted reports (invoices, statements) for last. These require paginated reports and more effort. Prioritize the analytical reports first — they deliver the most visible value and build confidence in the new platform.
Work With Access Evolved
If you found this article useful, Access Evolved specializes in exactly this kind of work — from hands-on Microsoft Access support to full database modernization projects.
Replacing Access reports with Power BI as part of a migration? Schedule a free call and get a reporting migration plan.
Thinking about migrating?
Ready to move beyond Microsoft Access?
Access is a great starting point, but growing businesses often hit its limits. Anthony Passeri specializes in migrating Access databases to modern platforms — Power Platform, Power Apps, SQL Server, Azure, and more — so you keep your data and workflows without the headaches.
Written by
Anthony Passeri, MBA
Access Expert and Editor
Bridging the gap between Access and the Future
Explore Topics
Keep reading
More on Power Platform
Building Your First Power App: A Guide for Access Developers
Power Apps looks nothing like Access at first. But the concepts map more closely than you might expect. Here is how to build your first canvas app if you already know Access.
Dataverse Explained for Access Developers
Dataverse is the database behind Power Apps. If you are migrating from Access, understanding how Dataverse tables, relationships, and security differ from Access is essential.
Power Automate: Replacing Access VBA Automation
Much of the automation built into Access VBA — email notifications, file exports, scheduled tasks — can be rebuilt in Power Automate with less code and better reliability.