How to Combine Two Power BI Reports into One
Trying to flip between two separate Power BI reports to get a complete picture is both inefficient and frustrating. What you need is a single, unified dashboard that tells the whole story. This guide will walk you through exactly how to combine those scattered reports into one powerful, consolidated view in Power BI.
Why Combine Power BI Reports in the First Place?
Before jumping into the how-to, it’s worth clarifying the "why." Consolidating your reports isn't just about making things look tidy, it's a strategic move that unlocks several key benefits:
- A Single Source of Truth: When everyone is looking at the same report, conversations become more consistent and decisions are based on the same information. It eliminates the confusion of competing versions.
- Deeper, Cross-Functional Insights: Imagine combining your sales data from one report with your marketing campaign data from another. Suddenly, you can directly correlate ad spend with sales conversions in a single view, something that was impossible when they were separate.
- Simplified Sharing & Management: Managing access, updates, and distribution for one report is far easier than juggling two, three, or even more. It streamlines your workflow and reduces administrative overhead.
- Improved User Experience: Providing your team or clients with a single, comprehensive dashboard saves them time and makes it easier for them to quickly get the answers they need without having to hunt through different files.
The Core Challenge: What Merging Really Means
Power BI doesn't have a simple “File > Merge Reports” button. A Power BI file (.pbix) is more than just a collection of charts, it’s a self-contained package with three main components:
- The Data Model: This includes your data tables, the relationships between them, and your DAX calculations (Measures and Calculated Columns). This is the analytical engine of your report.
- The Power Query Transformations: These are the data cleaning and preparation steps you've built. All the M code in the background shapes your raw data before it even enters the model.
- The Report View: This is the front-end - the pages, visuals, charts, slicers, and bookmarks that users interact with.
Combining two reports effectively means you have to merge these components from your "source" report into your "destination" report. We'll cover two methods: a quick-and-easy approach with some limitations, and a more robust, comprehensive method.
Free PDF · the crash course
AI Agents for Marketing Crash Course
Learn how to deploy AI marketing agents across your go-to-market — the best tools, prompts, and workflows to turn your data into autonomous execution without writing code.
Method 1: The Fast 'Copy and Paste Visuals' Approach
This is the simplest way to get visuals from one report to another, but it comes with a major prerequisite: your destination report must already contain all the data needed for the visuals you're copying.
This method works best when you have two reports built from the same (or very similar) data model, and you just want to consolidate the visual layouts into one file.
Step-by-Step Instructions
- Open Both Reports: Launch Power BI Desktop and open both the source
.pbixfile (the one you're copying from) and the destination.pbixfile (the one you're pasting into). - Select Your Visual: In the source report, navigate to the page with the visual you want to move. Click on the visual to select it. To copy multiple visuals, hold down
Ctrlwhile clicking on each one. To copy a whole page of visuals, pressCtrl + A. - Copy the Visual: Press
Ctrl + Cto copy the selected visual(s). - Paste into the Destination Report: Switch over to your destination report. Create a new page or go to an existing one, and press
Ctrl + Vto paste the visual. Power BI will attempt to recreate it.
What to Do When It Breaks
If your destination report has the exact same table and column names used by the visual, it should appear perfectly. More often than not, however, you'll see a broken visual with an error. This happens because the visual can't find the specific data fields it needs.
Don’t worry, this is easy to fix. Simply select the broken visual. In the Visualizations pane, you'll see the fields that have an error icon next to them. Drag and drop the correct fields from your destination report's data model onto the mismatched fields to remap the visual. You’ll have to do this for each visual you copy over, but it's often faster than rebuilding them from scratch.
Method 2: The Comprehensive Merge
If your reports use different data sources, tables, and logic, you'll need a more thorough method. This process involves manually migrating the backend components - Power Query (M Code), the data model (Relationships), and DAX measures - before copying over the visuals. It's methodical, but it ensures everything works perfectly.
First, decide which of your reports will be the "master" file. This is the one you will merge everything else into. Always work on backups, not your original files!
Phase 1: Consolidate Your Power Query Logic
This step brings the data transformation and cleaning logic from your source report into your master report.
- Open both reports. In your source report, click on the “Transform data” button to open the Power Query Editor.
- In the Queries pane on the left, select a query you need to move.
- Go to the “View” tab and click on “Advanced Editor.” This will open a window showing the M code for that query.
- Select all the code (
Ctrl + A) and copy it (Ctrl + C). - Now, switch to your master report and open its Power Query Editor.
- In the "Home" tab, go to “New Source” > “Blank Query.”
- Right-click the new query and select "Advanced Editor," then paste the M code you copied earlier. Click "Done."
- Rename the new query in the pane on the right so it exactly matches its name in the source report. This is crucial for keeping DAX formulas and relationships intact later.
- Repeat this for every query, parameter, and function you need to bring over. Once finished, click "Close & Apply."
Phase 2: Recreate the Data Model Relationships
After closing Power Query, your master file will load all the new tables. However, it won’t know how these new tables relate to each other or to your existing tables. You need to rebuild these connections.
- In your source report, go to the Model view. Take a screenshot or make notes of the relationships between the tables you just moved. Pay close attention to which columns are connected, the cardinality (e.g., one-to-many), and the cross-filter direction.
- In your master report, go to the Model view. You will see your new tables sitting there, disconnected.
- Recreate the relationships you noted by dragging the key column from one table and dropping it onto the corresponding key column in the other.
- Click on the newly created relationship line to open the "Edit relationship" dialog box and verify the cardinality and filter direction match your source model.
Phase 3: Migrate DAX Measures and Calculated Columns
Your tables are in, and your relationships are set. Now it’s time to move over the brains of the operation: your DAX calculations.
- Create a list of all the measures and calculated columns in your source report. You might find it helpful to look at one table at a time.
- Select a measure in the source report. The DAX formula will appear in the formula bar. Copy the entire formula.
- Switch to the master report. In the "Home" tab, click “New measure.”
- Paste the DAX formula you copied into the formula bar and press Enter. Make sure the measure is placed in the same "home table" as it was in the original report.
- Repeat this copy-paste process for every single DAX measure and calculated column. This can be time-consuming but is essential for your report’s functionality.
Free PDF · the crash course
AI Agents for Marketing Crash Course
Learn how to deploy AI marketing agents across your go-to-market — the best tools, prompts, and workflows to turn your data into autonomous execution without writing code.
Phase 4: Copy Over the Visuals (The Easy Part!)
With the entire data model - queries, relationships, and DAX - now replicated in your master report, you can finally move the front-end visuals using the simple copy-paste technique from Method 1. Since the backend is a perfect match, the visuals should transfer over seamlessly without breaking.
Tips for a Smoother Merge
- Always Backup First: Before you begin, save copies of your
.pbixfiles with a new name likeMyReport_V2orMyReport_Master. This prevents any accidental loss of work. - Use Power BI Themes: To maintain consistent styling (colors, fonts, etc.), go to your source report, click the "View” tab, open the themes dropdown, and "Save current theme." You can then import this
.jsonfile into your master report. - Check Data Source Credentials: After adding new queries, you may need to enter credentials for the underlying data sources. Go to “Transform data” > “Data source settings” to update them.
Final Thoughts
Combining two Power BI reports primarily involves a methodical process of transferring the data query logic, relational model, DAX calculations, and finally, the visuals. While it isn't a one-click process, breaking it down into these distinct phases makes it a structured and manageable task that can greatly enhance your reporting capabilities.
The time you spend manually consolidating reports is a common pain point for anyone working with data scattered across different platforms. At Graphed, we focus on eliminating that friction entirely. By providing one-click integrations for sources like Google Analytics, Shopify, Salesforce, and ad platforms, we help you bring all your data into a single, unified space from the start. From there, you can use simple, natural language to instantly build the exact real-time dashboards you need, allowing you to focus on insights, not manual report merging. If you're ready to automate your reporting, you can get started with Graphed for free.
Related Articles
How to Create Facebook Ads API for Claude Code
Create a Meta Marketing API access token that never expires, using a system user, so Claude Code can pull Facebook ad reports and manage campaigns.
ClickHouse vs Postgres: When to Switch to Columnar
Comparing ClickHouse vs PostgreSQL means matching storage architecture to workload. Row storage wins for transactions. Columnar wins for scan-heavy analytics.
Google Ads for Orthodontists: Get More Booked Consults
Most orthodontic Google Ads campaigns waste money on low-intent searches. The problem is structure, not the platform.