Prepare to migrate to Power BI

This article describes actions you can consider prior to migrating to Power BI.

Бележка

For a complete explanation of the above graphic, see Power BI migration overview.

The pre-migration steps emphasize up-front planning, which is important preparation before moving through the five migration stages. Most of the pre-migration steps will occur once, though for larger organizations some portions might be iterative for each business unit or departmental area.

The output from the pre-migration steps includes an initial governance model, initial high-level deployment planning, in addition to an inventory of the reports and data to be migrated. Additional information from activities in Stages 1, 2, and 3 will be necessary to fully estimate the level of effort for migrating individual solutions.

Съвет

Most of the topics discussed in this article also apply to a standard Power BI implementation project.

Create cost/benefit analysis and evaluation

Several top considerations during the initial evaluation include obtaining:

• Clarity on the business case and BI strategy to reach a specific desired future state.
• Clarity on what success means, and how to measure progress and success for the migration initiative.
• Cost estimates and return on investment (ROI) calculation results.
• Successful results for several productive Power BI initiatives that are smaller in scope and complexity level.

Identify stakeholders and executive support

Several considerations for identifying stakeholders include:

• Ensure executive sponsorship is in place.
• Ensure alignment with stakeholders on the business case and BI strategy.
• Include representatives from throughout the business units—even if their content is slated for migration on a later timetable—to understand their motivations and concerns.
• Involve Power BI champions early.
• Create, and follow, a communication plan with stakeholders.

Съвет

If you fear you're starting to overcommunicate, then it's probably just about right.

Generate initial governance model

Several key items to address early in a Power BI implementation include:

• Specific goals for adoption and where Microsoft Fabric and Power BI fit into the overall BI strategy for the organization.
• How the Fabric administrator role will be handled, particularly in decentralized organizations.
• Policies related to achieving trusted data: use of authoritative data sources, addressing data quality issues, and use of consistent terminology and common definitions.
• Security and data privacy strategy for data sources, data models, reports, and content delivery to internal and external users.
• How internal and external compliance, regulatory, and audit requirements will be met.

Важно

The most effective governance model strives to balance user empowerment with the necessary level of control. See more information, read about discipline at the core and flexibility at the edge.

Conduct initial deployment planning

Initial deployment planning involves defining standards, policies, and preferences for the organization's Power BI implementation.

Note that Stage 2 references solution-level deployment planning. The Stage 2 activities should respect the organizational-level decisions whenever possible.

Some critical items to address early in a Power BI implementation include:

• Fabric tenant setting decisions, which should be documented.
• Workspace management decisions, which should be documented.
• Considerations and preferences related to data and content distribution methods, such as apps, workspaces, sharing, subscriptions, and embedding of content.
• Preferences related to semantic model modes, such as use of Import mode, DirectQuery mode, or combining the two modes in a composite model.
• Securing data and access.
• Working with shared semantic models for reusability.
• Applying data certification to promote the use of authoritative and trustworthy data.
• Use of different report types, including Power BI reports, Excel reports, or paginated reports for different use cases or business units.
• Change management approaches for managing centralized BI items and business-managed BI items.
• Training plans for consumers, data modelers, report authors, and administrators.
• Support for content authors by using Power BI Desktop templates, custom visuals, and documented report design standards.
• Procedures and processes for managing user requirements, such as requesting new licenses, adding new gateway data sources, gaining permission to gateway data sources, requesting new workspaces, workspace permissions changes, and other common requirements that might be encountered on a regular basis.

Важно

Deployment planning is an iterative process. Deployment decisions will be refined and augmented many times as your organization's experience with Power BI grows, and as Power BI evolves. The decisions made during this process will be used during the solution-level deployment planning discussed in Stage 2 of the migration process.

Establish initial architecture

Your BI solution architecture will evolve and mature over time. Power BI setup tasks to handle right away include:

• Power BI tenant setup and integration with Microsoft Entra ID.
• Define Power BI administrators.
• Procure and assign initial user licenses.
• Configure and review Fabric tenant settings.
• Setup workspace roles and assign access to Microsoft Entra security groups and users.
• Configure an initial data gateway cluster—with a plan to update regularly.
• Procure initial Premium capacity subscription (if applicable).
• Configure Premium capacity workloads—with a plan to manage on an ongoing basis.

Важно

At times this article refers to Power BI Premium or its capacity subscriptions (P SKUs). Be aware that Microsoft is currently consolidating purchase options and retiring the Power BI Premium per capacity SKUs. New and existing customers should consider purchasing Fabric capacity subscriptions (F SKUs) instead.

For more information, see Important update coming to Power BI Premium licensing and Power BI Premium FAQ.

Define success criteria for migration

The first task is to understand what success looks like for migrating an individual solution. Questions you might ask include:

• What are the specific motivations and objectives for this migration? For more information, see Power BI migration overview (Consider migration reasons). This article describes the most common reasons for migrating to Power BI. Certainly, your objectives should be specified at the organizational level. Beyond that, migrating one legacy BI solution could benefit significantly from cost savings, whereas migrating a different legacy BI solution could focus on gaining workflow optimization benefits.
• What's the expected cost/benefit or ROI for this migration? Having a clear understanding of expectations related to cost, increased capabilities, decreased complexity, or increased agility, is helpful in measuring success. It can provide guiding principles to help with decision-making during the migration process.
• What key performance indicators (KPIs) will be used to measure success? The following list presents some example KPIs:
  • Number of reports rendered from legacy BI platform, decreasing month over month.
  • Number of reports rendered from Power BI, increasing month over month.
  • Number of Power BI report consumers, increasing quarter over quarter.
  • Percentage of reports migrated to production by target date.
  • Cost reduction in licensing cost year over year.

Съвет

The Power BI activity log can be used as a source for measuring KPI progress.

Prepare inventory of existing reports

Preparing an inventory of existing reports in the legacy BI platform is a critical step towards understanding what already exists. The outcome of this step is an input to assessing the migration effort level. Activities related to preparing an inventory can include:

1. Inventory of reports: Compile a list of reports and dashboards that are migration candidates.
2. Inventory of data sources: Compile a list of all data sources accessed by existing reports. It should include both enterprise data sources as well as departmental and personal data sources. This process could unearth data sources not previously known to the IT department, often referred to as shadow IT.
3. Audit log: Obtain data from the legacy BI platform audit log to understand usage patterns and assist with prioritization. Important information to obtain from the audit log includes:
   • Average number of times each report was executed per week/month/quarter.
   • Average number of consumers per report per week/month/quarter.
   • The consumers for each report, particularly reports used by executives.
   • Most recent date each report was executed.

Бележка

In many cases, the content isn't migrated to Power BI exactly as is. The migration represents an opportunity to redesign the data architecture and/or improve report delivery. Compiling an inventory of reports is crucial to understanding what currently exists so you can begin to assess what refactoring needs to occur. The remaining articles in this series describe possible improvements in more detail.

Explore automation options

It isn't possible to completely automate a Power BI conversion process end-to-end.

Compiling the existing inventory of data and reports is a possible candidate for automation when you have an existing tool that can do it for you. The extent to which automation can be used for some portions of the migration process—such as compiling the existing inventory—highly depends upon the tools you have.

Related content

In the next article in this Power BI migration series, learn about Stage 1, which is concerned with gathering and prioritizing requirements when migrating to Power BI.

Other helpful resources include:

• Microsoft's BI transformation
• Power BI implementation planning
• Questions? Try asking the Fabric Community
• Suggestions? Contribute ideas to improve Fabric

Experienced Power BI partners are available to help your organization succeed with the migration process. To find a Power BI partner, visit the Microsoft Power BI partners portal.