How to Move Power BI Report from One Workspace to Another

Moving a Power BI report from one workspace to another is a common task, whether you're promoting a report from a development area to a final production space, reorganizing projects, or moving your personal drafts over to a collaborative team workspace. This guide will walk you through the different ways to accomplish this, from the simple and manual to the more advanced and automated.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

Before You Begin: Understanding Workspaces

First, it’s important to understand the relationship between a report and its dataset in Power BI. A Power BI report (.PBIX file) usually contains two key components: the report itself (the visuals, pages, and layouts) and the dataset (the data model, connections, and DAX measures).

When you publish a report to the Power BI service, both the report and the dataset are uploaded. They exist as separate items in the workspace but are intrinsically linked. You can't move just the report without considering what happens to its underlying dataset.

Here are a few common reasons you might need to move a report:

• Collaboration: Moving a report from your personal "My Workspace" into a shared team workspace for others to view and contribute.
• Lifecycle Management: Promoting a report from a "Development" workspace to a "Testing" or "Production" workspace in a controlled manner.
• Project Organization: Reorganizing reports into new, more logically structured workspaces as company projects evolve.

With that context in mind, let’s look at the different methods you can use.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

Method 1: The Simple "Download and Upload"

This is the most direct and common method for one-off moves. You simply download a copy of the report file (.PBIX) from the source workspace and upload it to the destination workspace. This creates a brand-new copy of both the report and its dataset in the new location.

Step-by-Step Instructions:

1. Navigate to the Source Workspace: Open your web browser, go to Power BI Service, and find the workspace containing the report you want to move.
2. Open the Report: Click on the report to open it in the viewer.
3. Download the .PBIX File: In the top menu, go to File > Download this file. You might see a dialog box asking what to download. Choose the option to download a copy of your report and data (.pbix).
4. Save the File: Save the .PBIX file to your computer in a location you can easily find, like your Desktop or Downloads folder.
5. Go to the Destination Workspace: In the Power BI service, navigate to the new workspace where you want to move the report.
6. Upload the Report: Click the "Upload" button (usually found at the top of the workspace view) and then select "Browse." Find and select the .PBIX file you downloaded in step 4. Power BI will then upload the report and dataset into the new workspace.

What to Check After Moving (Don't Skip This!)

This method creates a completely new, independent copy. Nothing is carried over from the original location except what is inside the file itself. You must reconfigure the new dataset.

• Data Source Credentials: The connection settings are in the file, but your credentials are not. In the new workspace, find the new dataset, click the three dots (...), and go to "Settings." Expand the "Data source credentials" section and click "Edit credentials" to re-enter your username, password, API key, or other authentication details.
• Scheduled Refresh: Your refresh schedule is not part of the .PBIX file. While in the dataset Settings, configure the "Scheduled refresh" section to set up the daily or weekly cadence you need.
• Gateway Connection: If your report uses an on-premises data source, you'll need to re-map it to your gateway in the "Gateway connection" section of the dataset settings.
• Sharing and Permissions: App permissions and user access rights from the old workspace do not transfer. You will need to re-share the report and reconfigure access with your colleagues from the new workspace.
• Row-Level Security (RLS): The RLS roles are saved within the .PBIX file, but the user assignments are not. You will need to go into the dataset's "Security" settings in the service to assign users and groups to the appropriate RLS roles.
• Dashboard Tiles: If you had any visuals from the original report pinned to a Power BI dashboard, those tiles still point to the old report. You will need to delete those tiles and re-pin them from the newly uploaded report.

Method 2: Using Deployment Pipelines (For Premium Users)

If you're working in a more structured environment and need to move content consistently - especially for a development-to-production workflow - Deployment Pipelines are a much better option. This feature is designed specifically for managing the BI content lifecycle.

Note: This feature requires a Power BI Premium license (either Premium Per User - PPU, or a Premium capacity).

How Deployment Pipelines Work

Deployment pipelines let you manage content as it moves between different stages, typically: Development > Testing > Production. When you move content, Power BI intelligently copies it to the next stage and can help maintain settings automatically.

Step-by-Step Instructions:

1. Create a Pipeline: In the left navigation pane of the Power BI service, click on "Deployment pipelines" and then "Create pipeline." Give it a name and a description.
2. Assign Your Workspace: You'll see stages like "Development," "Test," and "Production." Assign your original workspace (the one with the report you want to move) to the "Development" stage. Select the workspace and click "Assign."
3. Deploy to the Next Stage: Once assigned, Power BI will scan the workspace content. You can now click the "Deploy" button. Power BI will automatically create a new, empty workspace for the "Test" stage and copy all the content from the "Development" stage into it. If you already have a "Test" workspace, you can assign it instead.
4. Manage Changes: After making changes to your report in the "Development" workspace, the pipeline will show a comparison between stages. Icons indicate what's new, different, or missing. This allows you to selectively deploy only the items that have changed, which is much more efficient.
5. Configure Deployment Rules: This is the most powerful feature. You can set up rules to automatically change dataset parameters or data source connections between stages. For example, you can have a rule that points the dataset to a test database in the "Test" workspace and to a production database in the "Production" workspace. This prevents you from having to manually change connections every time you deploy.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

When Should You Use Deployment Pipelines?

• When you have a formal process for promoting reports from development to production.
• When you need to maintain different data sources for different environments.
• When you want to reduce the risk of manual errors associated with the download/upload method.
• When you work collaboratively on reports and need a single source of truth for each lifecycle stage.

Method 3: PowerShell and APIs (For Automation and Scale)

For BI developers and administrators who need to automate the report migration process, especially for moving dozens of reports at once, Power BI offers robust APIs and PowerShell cmdlets.

Who is this For?

This approach is best suited for scenarios where manual processes are too slow or impractical. For example:

• Migrating an entire department's content to a new Power BI tenant.
• Automating deployments as part of a DevOps/CI/CD (Continuous Integration/Continuous Deployment) pipeline.
• Programmatically cloning a workspace and all its content.

The General Process

This method replicates the "Download and Upload" process programmatically. While a full tutorial is beyond the scope of this article, the basic steps are:

# 1. Connect to your Power BI account
Connect-PowerBIServiceAccount

# 2. Define your source and target variables
$sourceWorkspaceId = "..."
$reportId = "..."
$targetWorkspaceId = "..."
$filePath = "C:\Temp\ExportedReport.pbix"

# 3. Export the .pbix file from the source workspace
Export-PowerBIReport -WorkspaceId $sourceWorkspaceId -Id $reportId -OutFile $filePath

# 4. Import the .pbix file into the target workspace
New-PowerBIReport -Path $filePath -WorkspaceId $targetWorkspaceId -Name "My New Deployed Report"

# 5. Potentially continue with more scripts to update parameters and credentials...

Just like the manual download method, this process creates a new copy of the dataset that requires you to update data source credentials, scheduled refresh settings, etc. These can also be updated using additional PowerShell cmdlets.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

Final Thoughts

Moving a Power BI report and its data between workspaces is a fundamental skill. For single moves, the direct download-and-upload method is perfectly fine, as long as you remember to re-configure the dataset afterwards. For those with Premium licenses managing an application lifecycle, Deployment Pipelines offer a governed, repeatable, and less error-prone process. Finally, for large-scale automation, the PowerShell and API approach provides ultimate flexibility and power.

Frustrations often arise not from the tools themselves, but from the manual time and complexity involved in managing reporting across many platforms. At Graphed, we've focused on eliminating these hurdles. Instead of manually moving files, configuring dashboards, or managing data sources across platforms, you can simply connect your data and use natural language to create and receive insights instantly. We automate the busy work of connecting data, so you can go straight to asking a question like, "What were my top performing campaigns last month?" and get a live dashboard back in seconds — no PBIX files, deployments, or credentials needed. To experience it yourself, feel free to try Graphed.