Forum Discussion
Migrate fabric warehouse data
- 1 year ago
Hi DiKi-I ,
We cannot generate scripts after connecting SSMS , but still we can generate scripts from Fabric Warehouse itself using download sql database project as shown below:
As of now, Fabric Warehouse does not support generating data scripts for data. A recommended approach is to create two Azure service principles, grant them access to the respective workspaces, and use ADF pipelines with Copy Data activities to move data from one tenant to another.
Below is the link for another workaround:
Solved: Re: MS Fabric migration between tenants - Microsoft Fabric Community
If this post helps, then please consider Accepting as solution to help the other members find it more quickly.Thank you.
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.