Forum Discussion
Migration to Power BI
Hello Community,
Actually I work on a Migration Project from Microstrategy to Power BI.
The idea is to prepare the semantic model to the Functional users (Non technical) and they will build their own visuals.
The semantic model should be as the same "Shape" they used to see in Microstrategy, same columns, same tables, same attributes.
The challenge here is if we recreate the same structure, I will not reach the needed performance (No surrogate keys, no dim and fact tables, so no Star schema model, etc).
Is there any recommantion to have that balance between delivering the shape they needed, and the performance I need?
Thank you.
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.
4 Replies
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.Hi PBI_Developer2 ,
I did a couple of Microstrategy migrations and the ones I did were based on cubes so the dimensions vs fact tables was how it was also built altough users did not had that experience in the Microstrategy UI/UX. I recommend that you try and built a star schema even if the overall Microstrategy that you are working with is not in the same way.
We are talking about different tools with different specifications, has I refered on my experience I was able to recreate the models and even get better performances than the users had previously.
On an additional note is difficult to tell you the best options without further details, if you have a huge data amount with a "poor" semantic model for sure performance will suffer. The best practice is the star schema, and then with the use of field parameters, calculations groups, DAX user define functions, visual calculations you can get the user to make the transition.
If you need anything just let me know.
Hi PBI_Developer2,
Thank you for reaching out to the Microsoft Fabric Community Forum and thanks to MFelix and Omkar_1712 for sharing helpful insights.
Just checking in, were you able to resolve the issue? If not please feel free to share an update and we will be happy to assist further.
Your feedback will also help others facing similar challenges.
Thank you.Hi PBI_Developer2,
Could you please confirm whether the issue has been resolved or is still occurring? Your update may help others with similar concerns. Please let us know if you need any further assistance.
Thank you.
