Data & AnalyticsBy High10 Team 6 min read

How to Migrate to Power BI

How to Migrate to Power BI in Australia

Migrating to Power BI means moving your reporting from wherever it lives now, usually spreadsheets, an older reporting tool such as Crystal Reports or SSRS, or another BI product such as Tableau or Qlik, onto Power BI’s data model and reports. The rule that makes it go well is to migrate the questions, not the reports: most old reports are duplicates, unused or wrong, and rebuilding them faithfully wastes the project. This guide covers what to migrate and what to leave, the five stages Microsoft recommends, the Australian settings to get right, and a worked example.

Migrate the questions, not the reports

Start by listing every report that exists, who opens it, and how often. In most businesses a third are never opened, a third duplicate each other with small differences, and the rest answer perhaps ten questions between them. Those ten questions are what gets migrated. The old reports are kept available, read-only, for a few months and then retired. Rebuilding sixty reports in Power BI reproduces the mess at greater cost, and that is the most common migration mistake.

The five stages

Microsoft’s migration guidance sets out five stages, and they fit businesses of any size.

1. Gather requirements. The list of reports and the questions behind them, who needs each, and the definitions of the numbers. Also the data sources each report draws on, because the same source will feed the new model.

2. Plan the deployment. Workspaces for each audience, who will build and who will consume, licensing, where the tenant lives, how the data will be refreshed, and which reports go first.

3. Proof of concept. One important report, rebuilt properly on a new model, compared number for number against the old one. This surfaces the definition disagreements and the dirty data before they can derail the rest.

4. Create content. The data model, then the reports, in order of value. Each report checked against the old version by the people who use it.

5. Deploy. Publish to workspaces, set up security and refresh, train users, run old and new in parallel for a period, then retire the old reports. Microsoft’s guidance notes that a formal migration almost always runs alongside the development of new Power BI solutions, because once the model exists the questions nobody could answer before become easy.

The Australian settings

Where the data lives is set by the Microsoft 365 tenant’s home region, which Microsoft’s documentation on tenant location explains how to check. For most Australian businesses it should be an Australian region, and it is far easier to confirm before migrating than to change afterwards. Row-level security, so each person sees only their own branch or region, is built into the model once and applies everywhere. And personal information in the data, such as customer names and contact details, falls under the Privacy Act, so the model should carry only what the reports need.

From Excel

The most common migration is from spreadsheets, and it is also the one with the most hidden logic. Formulas accumulated over years encode definitions nobody wrote down. The proof of concept stage matters most here: rebuild the key spreadsheet report in Power BI and reconcile every number, and the differences will reveal where the definitions were wrong or inconsistent. Expect to find at least one. Keep the spreadsheet for one-off analysis; Power BI replaces the monthly assembly, not Excel itself.

From an older reporting tool or another BI product

Reports built in Crystal Reports, SSRS or a competing BI product each carry their own data queries and calculations. These do not move across directly; the questions and definitions are extracted and rebuilt on the Power BI model. Paginated reports, the long printable kind, have a Power BI equivalent and are migrated separately from interactive dashboards. Licences for the old tool are usually the reason for a deadline, so plan backwards from the renewal date and leave a month of parallel running.

Want this as a one-page checklist? Ten steps for moving your reporting to Power BI, on one A4 page with tick boxes.

Download the checklist (PDF)

A worked example

This is a hypothetical, not a client. Take a regional Victorian council contractor with 120 staff, reporting from an older reporting tool with 70 saved reports and a dozen spreadsheets. Stage one finds that 25 reports are never opened and 30 overlap, leaving 15 questions. Stage two plans three workspaces (operations, finance, management), confirms the tenant is in an Australian region, and sets a deadline from the old tool’s licence renewal. Stage three rebuilds the job profitability report and finds that two departments calculated margin differently; the definition is settled by the finance manager. Stage four builds the model and the 15 reports over six weeks. Stage five runs both systems for a month, trains the department heads, and retires the old tool at renewal. The business ends with 15 reports it trusts instead of 70 it did not.

What to avoid

Migrating every report. Skipping the proof of concept and discovering the definition arguments in month three. Building reports before the model. Leaving security to the end. Retiring the old tool before the parallel run has settled. And not naming someone to own the reports afterwards.

How High10 helps

High10 migrates Australian businesses to Power BI from spreadsheets, older reporting tools and other BI products, starting with the list of questions rather than the list of reports, proving one report before building the rest, and training someone in your team to own it. Every project is quoted in writing after a short scoping call.

Frequently asked questions

How long does a migration to Power BI take?

Six to twelve weeks for a business with a few sources and ten to twenty real questions, including a month of parallel running. Larger estates with many sources, paginated reports and complex security take three to six months. The number of questions sets the pace, not the number of old reports.

Can Excel reports be migrated to Power BI?

Yes, and it is the most common migration. The spreadsheet’s logic is rebuilt in the Power BI model and the numbers reconciled report by report. Expect to find definitions that were inconsistent between spreadsheets; settling them is part of the value.

Should we migrate all our existing reports?

No. List them, find which are opened and by whom, and migrate the questions behind the ones that matter. Most businesses find a third of their reports are unused and a third duplicate each other. The old reports stay available, read-only, until the parallel run is over.

Is migrating to Power BI worth it for a small business?

If someone spends more than a day a month assembling reports by hand from exports, yes, and the migration is small because the number of real questions is small. If reporting is a single spreadsheet that one person maintains in an hour, probably not yet.

Want this as a one-page checklist? Ten steps for moving your reporting to Power BI, on one A4 page with tick boxes.

Download the checklist (PDF)

Not sure how this applies to your business?

A 45 minute call, no cost, no obligation. You leave with a scope, an honest timeline and a fixed written quote.

Book a strategy call