Migrate fabric warehouse data

Hi DiKi-I There is another thread on this toopic that might help.

https://community.fabric.microsoft.com/t5/Fabric-platform/MS-Fabric-migration-between-tenants/m-p/4393747

DiKi-I ,

Cross-tenant migration of Fabric Warehouse data is a scenario many teams face when moving to a client environment, and it is achievable with the right migration and transfer approach rather than manual exports.

We’ve helped organizations handle tenant-to-tenant moves smoothly with structured tooling and automation — happy to show you how in a quick demo. Reach me at [email protected]

Hi DiKi-I ,

To migrate Microsoft Fabric Warehouse data to another tenant, use the built-in Migration Assistant, which allows you to export the schema (via DACPAC), fix compatibility issues, and copy data manually or via pipelines. For other artifacts like workspaces, Lakehouses, pipelines, and reports, there's no automated cross-tenant migration tool—you'll need to export PBIX files, notebooks, and pipeline definitions, then redeploy them manually or via PowerShell/REST APIs in the client tenant, followed by reconfiguring permissions, connections, and capacities.

https://learn.microsoft.com/en-us/fabric/data-warehouse/migrate-with-migration-assistant

Hi DiKi-I 

Migrating a Fabric warehouse from your tenant to a client's tenant involves several steps because Microsoft Fabric currently does not support a direct, built-in “export and import” feature for full warehouse migration across tenants. The best approach is to extract the data and schema from your existing warehouse and rebuild it in the client tenant. You can start by exporting the schema and data using T-SQL scripts or tools like Azure Data Factory, SQL Server Management Studio (SSMS), or Azure Data Studio, depending on your access level. You can also use PolyBase or COPY INTO commands to export data to OneLake or Azure Blob Storage in a structured format like CSV or Parquet. Once exported, you then switch to the client’s Fabric tenant, create a new warehouse, and import the exported data using either COPY INTO from OneLake or scripts to recreate tables and load data. If you have related artifacts like Power BI datasets or reports, you’ll also need to rebind them in the client’s environment and update any data source credentials or permissions. Ensure both tenants have necessary access to intermediate storage locations during the process. Though it's a manual, multi-step procedure, this method ensures a clean and auditable migration path.

Hi DiKi-I ,

Thank you for reaching out to Microsoft Fabric Community.

Thank you Wikkleyn_81 BhavinVyas3003 Poojara_D12 for the prompt response.

Microsoft Fabric does not natively support cross-tenant data movement.

If you need to move data from one Microsoft Fabric tenant to another-say from your environment to a client’s-the best way to do it is by using service principals, storage in between, and data pipelines. You’d start by setting up a service principal (an app identity) in your source tenant and give it the right permissions to access your Fabric workspace and the warehouse that holds the data.

Once that's set up, you use Fabric Pipelines or Azure Data Factory to export your warehouse data into a temporary storage location, like Azure Blob Storage or Data Lake, saving it in a standard format like CSV or Parquet.

Now, since you can’t directly connect two Fabric tenants, the next step is to move the exported files into the client’s tenant. You can use tools like AzCopy, Azure Storage Explorer, or ADF again to do this. Depending on the security setup, you might share access using SAS tokens or configure cross-tenant sharing using Azure B2B features if the client allows it.

After the files are in the client’s environment, you’ll repeat a similar setup on their side: create another service principal, give it access to their Fabric workspace and warehouse, and finally use another pipeline (or a SQL COPY INTO command) to bring the data into their Fabric Warehouse.

This approach gives you a secure, repeatable way to handle cross-tenant data transfers without needing any unsupported workarounds. 

If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it! 

Thank you.

Hi DiKi-I ,

I want to check if you had the opportunity to review the information provided and resolve the issue.If the response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.

Thank you.

Hi DiKi-I ,

May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.

Thank you.

Hi DiKi-I ,

I hope this information is helpful.If this answers your question, please accept it as a solution,so other community members with similar problems can find a solution faster.

Thank you.