Forum Discussion
Migration to Power BI
- 2 months ago
Hello PBI_Developer2 ,
This is a common challenge in BI migrations. While it may be tempting to recreate the MicroStrategy model exactly as users see it today, doing so can negatively impact Power BI performance and scalability.
My recommendation would be to separate the physical model from the business-facing model:- Build the semantic model using Power BI best practices (Star Schema, Fact and Dimension tables, surrogate keys, optimized relationships, etc.).
- Expose business-friendly names, folders, hierarchies, and measures so that users see a familiar experience.
- Use display folders, descriptions, perspectives, and friendly naming conventions to make the model resemble the structure users are accustomed to in MicroStrategy.
This approach allows you to retain the performance benefits of a properly modeled semantic layer while
minimizing the learning curve for business users.
You may also consider:- Creating Perspectives for different user groups.
- Hiding technical columns and surrogate keys.
- Using calculation groups and standardized measures where appropriate.
- Conducting short enablement sessions so users understand any unavoidable differences between MicroStrategy and Power BI.
In my experience, trying to replicate the source BI tool's structure 1:1 often results in compromises that affect performance and maintainability. A well-designed star schema with a business-friendly semantic layer usually provides the best balance between user adoption and long-term scalability.
Best regards,
Omkar Shinde
Microsoft Fabric Enthusiast | Power BI Consultant
💡 If you found this response helpful, please consider giving it a Kudos.
✅ If this resolves your question, please mark it as the Accepted Solution to help others in the community.
Hello PBI_Developer2 ,
This is a common challenge in BI migrations. While it may be tempting to recreate the MicroStrategy model exactly as users see it today, doing so can negatively impact Power BI performance and scalability.
My recommendation would be to separate the physical model from the business-facing model:
- Build the semantic model using Power BI best practices (Star Schema, Fact and Dimension tables, surrogate keys, optimized relationships, etc.).
- Expose business-friendly names, folders, hierarchies, and measures so that users see a familiar experience.
- Use display folders, descriptions, perspectives, and friendly naming conventions to make the model resemble the structure users are accustomed to in MicroStrategy.
This approach allows you to retain the performance benefits of a properly modeled semantic layer while
minimizing the learning curve for business users.
You may also consider:
- Creating Perspectives for different user groups.
- Hiding technical columns and surrogate keys.
- Using calculation groups and standardized measures where appropriate.
- Conducting short enablement sessions so users understand any unavoidable differences between MicroStrategy and Power BI.
In my experience, trying to replicate the source BI tool's structure 1:1 often results in compromises that affect performance and maintainability. A well-designed star schema with a business-friendly semantic layer usually provides the best balance between user adoption and long-term scalability.
Best regards,
Omkar Shinde
Microsoft Fabric Enthusiast | Power BI Consultant
💡 If you found this response helpful, please consider giving it a Kudos.
✅ If this resolves your question, please mark it as the Accepted Solution to help others in the community.