Forum Discussion
From PPU to Fabric - Incremental Refresh
Yes, that's correct—you will not lose any historical data during the migration from a Power BI Premium Per User (PPU) workspace to a Fabric Shared Capacity, even if your semantic model uses incremental refresh. The migration process preserves the existing partitions in the dataset, including the historical ones that were previously loaded and stored. When you perform the initial refresh after migration, only the incremental partitions—those defined by your refresh policy (such as the most recent 7 days or 1 month)—will be updated. The historical partitions remain intact and are not overwritten unless you explicitly change the incremental refresh policy or perform a full refresh by disabling and re-enabling incremental refresh. Therefore, as long as you don't modify the refresh policy post-migration, your history remains preserved, and only the most recent slices of data will be queried and updated during the refresh. Still, it's important to ensure that the data source credentials and gateway configurations are properly set up in the new capacity, as any failure in these settings could impact refresh behavior.
Thank you for a quick answer.
Ok, so based on your reply if we refresh only partitions we will not lose any history data right during migration ?
Super UserYes, that's correct—you will not lose any historical data during the migration from a Power BI Premium Per User (PPU) workspace to a Fabric Shared Capacity, even if your semantic model uses incremental refresh. The migration process preserves the existing partitions in the dataset, including the historical ones that were previously loaded and stored. When you perform the initial refresh after migration, only the incremental partitions—those defined by your refresh policy (such as the most recent 7 days or 1 month)—will be updated. The historical partitions remain intact and are not overwritten unless you explicitly change the incremental refresh policy or perform a full refresh by disabling and re-enabling incremental refresh. Therefore, as long as you don't modify the refresh policy post-migration, your history remains preserved, and only the most recent slices of data will be queried and updated during the refresh. Still, it's important to ensure that the data source credentials and gateway configurations are properly set up in the new capacity, as any failure in these settings could impact refresh behavior.