Migrate lakehouse and warehouse

[DiKi-I]

How I can migrate lakehouse and warehouse with complete data from one tenant to another?

[Anonymous]

Hi @DiKi-I 

Fabric doesn’t currently support a built-in “backup and restore” feature for Warehouses across tenants. However, you can achieve the same result by scripting the schema using SSMS or Azure Data Studio, exporting the data with COPY INTO (or using Dataflows Gen2, Azure Data Factory, or Notebooks), and storing the files in Azure Storage. Then, transfer the files to a storage location accessible by the target tenant, recreate the schema using the scripts, and load the data back using the same tools.

While not a native backup/restore, this is the most reliable and supported method available.

If this solution helps, please consider giving us Kudos and accepting it as the solution so that it may assist other members in the community
Thank you.

[Anonymous]

Hi @DiKi-I 

Thank you for reaching out microsoft fabric community forum.

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.

[DiKi-I]

no yet. I want to know how I can take the backup of warehouse and restore it to the new tenant? I'm not looking for workarounds.

[Poojara_D12 · Accepted solution]

Hi @DiKi-I 

Migrating a Lakehouse and Warehouse with complete data from one Microsoft Fabric tenant to another is not currently a fully automated, out-of-the-box process, but it can be achieved using a combination of data export/import and deployment pipelines or scripts. For the Lakehouse, you can use OneLake Shortcuts, Azure Data Factory, Dataflows Gen2, or Notebook scripts to copy data from the source tenant to external storage (such as Azure Data Lake Storage or Blob Storage), and then import it into the target tenant's Lakehouse. For Warehouses, the best approach is to export the data as CSV or Parquet files, or use T-SQL scripts to generate schema and data dumps, then recreate the schema and load the data into the new Warehouse in the target tenant. Additionally, if you have used Notebooks or Pipelines, you can export them as .ipynb or .json files and import them into the new environment. Since Fabric doesn’t yet support full cross-tenant deployment pipelines for all artifacts, this process may also involve manually recreating security settings, dataflows, and semantic models. It is recommended to script as much as possible using PowerShell, REST APIs, or Fabric Git integration to ensure consistency and reduce manual effort during the migration.

[GilbertQ]

Hi @DiKi-I 

You could use the copy activity to somewhere to migrate between tenants by logging in with the different credentials