Graphed LogoGraphed
Graphed LogoGraphed
How It WorksAgentsIntegrationsPricing

How to Move Power BI Dataset to Another Workspace

Cody Schneider••9 min read

Moving a Power BI dataset from one workspace to another is a common need when reorganizing projects, collaborating with new teams, or managing development and production environments. This article breaks down the most effective methods to move your datasets, starting with the simplest approach for everyday users and moving on to more advanced options for enterprise environments.

GraphedGraphed

Build AI Agents for Marketing

Build virtual employees that run your go to market. Connect your data sources, deploy autonomous agents, and grow your company.

Watch Graphed demo video

Why Move a Power BI Dataset?

Before jumping into the "how," it's helpful to understand the common scenarios that require moving a dataset. You might need to:

  • Promote Content: Moving a dataset from a personal development workspace (My Workspace) to a shared team workspace for collaboration.
  • Manage Environments: Creating separate workspaces for development, testing, and production (DEV/TEST/PROD) to ensure reports are validated before being released to business users.
  • Reorganize Workspaces: Cleaning up old projects or consolidating multiple workspaces into a single one to create a unified source of truth.
  • Share with a New Team: Granting a different department or project team access by moving the dataset into their dedicated workspace.

Despite being a common goal, Power BI doesn't have a simple "move" button. The process involves creating a copy of the dataset in the new location and re-establishing connections. Let's look at what to check before you start.

Prerequisites and Key Considerations

Diving in without planning can lead to broken reports and failed data refreshes. Here's a quick checklist to review first.

1. Workspace Permissions

To move a dataset, you need adequate permissions in both the original (source) and the new (destination) workspaces. You must have one of the following roles in both workspaces:

  • Admin: Full control over the workspace.
  • Member: Can add, edit, and publish content.
  • Contributor: Can publish content but cannot manage workspace users or settings.

A "Viewer" role is not sufficient, as you won't be able to publish new content to the destination workspace.

2. Content Dependencies

Remember that a dataset is not an isolated file, it’s the foundation for reports and dashboards. When you move or copy a dataset, the original reports and dashboards in the source workspace will remain linked to the original dataset. They will not automatically switch to the new one. You'll need a plan to either reconnect existing reports to the new dataset or republish the reports alongside the dataset.

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.

3. Data Source Credentials and Gateways

When you publish a dataset to a new workspace, the data source credentials do not come with it. You will need to re-enter them in the dataset’s settings in the Power BI service. If your dataset connects to on-premises data sources (like SQL Server or a file share), you must also ensure the data gateway is properly configured and accessible from the new workspace.

Method 1: The 'Download and Republish' Technique (Most Common)

This is the most direct and universally accessible method. It involves downloading the .pbix file, which contains your data model, queries, measures, and a report canvas, and then publishing it to the desired workspace. This creates a brand new copy of the dataset and its associated report in the new location.

This method is perfect for one-off moves and for users who are comfortable working in Power BI Desktop.

Step-by-Step Instructions

Part 1: Download the .pbix File

  1. Navigate to the source workspace in the Power BI service (app.powerbi.com) containing the dataset and report you want to move.
  2. Open the report that is built on the dataset you intend to move.
  3. From the top menu, click File > Download this file.
  4. A dialog box will appear. Select the option "A copy of your report and data (.pbix)". This bundles everything - the report visuals, data model, DAX measures, Power Query transformations, and (if you’re using Import mode) the data itself - into a single .pbix file.
  5. Save the file to your computer.

Part 2: Publish to the New Workspace

  1. Open the .pbix file you just downloaded using Power BI Desktop.
  2. Once opened, you don't need to make any changes. From the Home ribbon, click the Publish button.
  3. A dialog box will appear, listing all the workspaces you have access to. Carefully select the destination workspace where you want the dataset and report to live.
  4. After selecting the workspace, click Select. Power BI will begin publishing the file.
  5. Once successful, you'll see a confirmation message with a link to open the report in the Power BI service.

Part 3: Post-Publish Configuration

The job isn't done yet. After publishing to the new workspace, you need to configure the new dataset.

  • Set Data Source Credentials: In the destination workspace, find your new dataset, click the three-dot menu (...) next to its name, and select Settings. Expand the "Data source credentials" section and click "Edit credentials" to re-authenticate with your data sources.
  • Configure Scheduled Refresh: In the same Settings menu, find the "Scheduled refresh" section. Turn it on and set the frequency (e.g., daily, weekly). If you use an on-premises gateway, make sure it’s properly mapped here as well.
  • Update Apps: If the destination workspace publishes content via a Power BI app, be sure to update the app to include the newly added report and dataset.

Method 2: Using Power BI Deployment Pipelines (For Premium Users)

If you're working in an organization with Power BI Premium or Premium Per User (PPU), deployment pipelines are an excellent way to manage content lifecycle. This feature is designed specifically for moving BI content through different stages, like development, testing, and production, in a controlled and repeatable manner.

Instead of a manual task, deployment pipelines turn the process into a structured, automated workflow.

GraphedGraphed

Build AI Agents for Marketing

Build virtual employees that run your go to market. Connect your data sources, deploy autonomous agents, and grow your company.

Watch Graphed demo video

What Are Deployment Pipelines?

A deployment pipeline is a tool within the Power BI service that you can link to different workspaces, each representing a stage. A typical setup is:

  • Development Stage: Linked to a workspace where analysts and developers create and modify content.
  • Test Stage: Linked to a workspace where QA teams or business users test the reports against a separate test dataset.
  • Production Stage: Linked to the workspace that end-users access for official reporting.

You can then "deploy" content from one stage to the next with just a few clicks. It intelligently compares the content between stages and only moves the changes.

How to Use Them for Moving a Dataset

  1. Create the Pipeline: From the main navigation pane in the Power BI service, select Deployment Pipelines and click Create pipeline.
  2. Assign Workspaces: Assign your source workspace to the "Development" stage and your destination workspace to the "Test" (or "Production") stage. Note: The assigned workspaces must reside on a Premium capacity.
  3. Compare and Deploy: After assigning workspaces, Power BI will compare the content between them. You’ll see which items (datasets, reports, dashboards) are new or different.
  4. Select the dataset and any related reports you want to move, and click Deploy.

The major advantage here is control. You can even set up deployment rules, like automatically changing a data source parameter between stages (e.g., pointing to a test database in the Test stage and a production database in the Production stage).

Method 3: Advanced Deployment with the XMLA Endpoint (Technical Users)

For highly technical scenarios, you can use third-party tools to manage dataset migration via the XMLA endpoint. This is a Premier feature ideal for data modelers and BI professionals who need granular control over the deployment process.

The XMLA endpoint allows applications like Tabular Editor and SQL Server Management Studio (SSMS) to connect directly to a Power BI dataset as if it were a SQL Server Analysis Services database. Using these tools, you can script changes, perform metadata deployments, and automate complex tasks.

How it Works

  1. Enable the XMLA Endpoint: This must be enabled in the Power BI Admin Portal for your tenant, and the setting "XMLA Read-Write" must be enabled for the Premium capacity your workspace resides on.
  2. Connect with a Tool: Use a tool like Tabular Editor 3 or ALM Toolkit to connect to your source workspace's XMLA endpoint.
  3. Deploy/Script the Model: These tools allow you to compare the schema between two datasets or script the metadata of your source dataset. You can then deploy this metadata to create a new dataset in the destination workspace, preserving complex relationships and measures perfectly.

This method doesn't move the data itself, it just recreates the dataset's structure. You would still need to refresh the dataset in the destination workspace to populate it with data. This approach is overkill for simple moves but invaluable for complex, automated BI workflows and DevOps practices.

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.

What About Dependent Reports?

After you move your dataset, what happens to the reports that were built on top of the original one? They remain in the source workspace, still pointing to the now-outdated dataset.

If you used the "Download and Republish" method (Method 1), a new report was created with the new dataset in the destination. Your best path forward is to update this new report as your primary version and, if necessary, recreate any additional reports to point to this new centralized, authoritative dataset. This ensures consistency and prevents an old version from being used by mistake.

Final Thoughts

Choosing the right method for moving a Power BI dataset depends on your specific needs and license. For most users, downloading and republishing a .pbix file is simple and effective. For organizations leveraging Power BI Premium, deployment pipelines provide a robust and structured workflow, while advanced tools using the XMLA endpoint offer ultimate control for technical teams.

While managing assets in tools like Power BI is a necessary part of data governance, the operational overhead can sometimes distract from the ultimate goal: getting clear answers. If you find yourself spending more time managing permissions, datasets, and refreshes than gleaning insights, we created Graphed to simplify that entire pipeline. We let you connect your data sources in seconds and use simple, natural language to instantly build the dashboards and reports you need - letting you focus on decisions, not deployment.

Related Articles