Services Work Blog Get in touch →

Legacy BI doesn't fail loudly.
It just gets expensive.

Tableau and Qlik licences renew at a premium. SSRS quietly rots. Reports multiply until no one trusts the numbers, and every month-end starts with manual reconciliation. A migration to Power BI and Microsoft Fabric isn't about a new tool — it's about consolidating onto one governed platform your team can actually run. We do that as a fixed-scope engagement, so the move itself doesn't become the next open-ended project.

Source platforms.

If your stack isn't listed, ask — we'll tell you honestly whether a clean migration path to Power BI exists.

Tableau

Workbooks, published data sources and Tableau Server / Cloud content rebuilt on Power BI semantic models.

Qlik Sense / QlikView

Qlik apps and the associated script-based data model re-platformed onto a governed Fabric Lakehouse.

MicroStrategy

Dossiers, reports and the metadata layer migrated to Power BI with a certified semantic model. See the MicroStrategy migration →

SSRS

Paginated SQL Server Reporting Services reports moved to Power BI paginated reports or modern dashboards.

Cognos

IBM Cognos reports and framework models reconstructed on Power BI and Microsoft Fabric.

Excel-based reporting

Spreadsheet sprawl and manual month-end packs replaced with a single source of truth.

Assess, rationalise,
rebuild, validate.

A migration is more than a port. Here's what's in scope — agreed in writing before work starts.

01

Migration Readiness Audit

We map your current stack, data sources and dependencies, and assess what's ready to migrate cleanly versus what needs a rebuild first.

  • Source platform and data-source inventory
  • Data model health assessment
  • Risk register and migration approach
02

Report Inventory & Prioritisation

Every report catalogued and analysed by usage. We decide together what to migrate, rebuild, consolidate or retire — no copying clutter forward.

  • Full report inventory with usage data
  • Migrate / rebuild / consolidate / retire decisions
  • Prioritised migration backlog
03

Data Model Rebuild

Where the underlying model is the real problem, we rebuild it on a Fabric Lakehouse or Warehouse so reports sit on a clean, governed foundation.

  • Lakehouse / Warehouse target design
  • Ingestion from existing sources
  • Certified semantic model with shared measures
04

Power BI Rebuild

The prioritised reports rebuilt for Power BI's strengths — not a forced copy of an old Tableau or Qlik layout.

  • Dashboards and paginated reports as needed
  • DAX measures and row-level security
  • Published with correct workspace access
05

Parallel-Run Validation

New reports run alongside the legacy system and we reconcile the numbers field by field until they match within tolerance. Sign-off is against the reconciliation.

  • Field-by-field number reconciliation
  • Agreed parallel-run period
  • Documented sign-off criteria
06

Cutover, Handover & Training

A controlled switch-off of the legacy system, with documentation and training so your team owns the new platform from day one.

  • Cutover plan and legacy decommission support
  • Technical and user documentation
  • Handover workshop and team training

A migration in six phases.

Scope is agreed after a short discovery session, then locked. The phases below are fixed; their length scales with the size of your estate.

Phase
01 · Discovery

Understand the estate

A short discovery session to size the migration: which platforms, how many reports, what data sources, and where the pain is. Output is a fixed scope, timeline and price.

Phase
02 · Audit

Readiness audit & inventory

We catalogue every report, profile the data sources, and assess model health — producing the migrate / rebuild / consolidate / retire decisions and a prioritised backlog.

Phase
03 · Foundation

Data platform & semantic model

Where needed, we build the Fabric Lakehouse or Warehouse, ingest from your sources, and stand up a certified semantic model the new reports will share.

Phase
04 · Rebuild

Rebuild the prioritised reports

Reports are rebuilt in Power BI in priority order, reviewed with stakeholders as they land so feedback is incorporated before validation rather than after.

Phase
05 · Validate

Parallel run & reconciliation

New and legacy reports run side by side. We reconcile the numbers until they match within tolerance, and capture sign-off against that reconciliation.

Phase
06 · Cutover

Cutover & handover

A controlled switch to Power BI, legacy decommission support, documentation, and a handover workshop so your team operates the platform independently.

Who this is for.

BI Platform Migration is a fixed-scope engagement. Here's how to know if it fits.

On Tableau, Qlik, MicroStrategy or SSRS

A legacy BI estate that has become a licensing, maintenance or trust burden.

Consolidating onto Microsoft

You're standardising on Power BI and Fabric and want the legacy stack retired cleanly, not left running in parallel forever.

Too many reports, too little trust

Report sprawl and competing numbers mean month-end starts with manual reconciliation.

Need it done, then handed over

You want a migration delivered and your team trained — not a multi-year programme or a permanent dependency.

When this is not the right fit

If any of these apply, a different starting point is more honest:

  • You're not sure what to migrate yet — start with a Migration Audit first
  • You're building net-new on Fabric with no legacy estate — see Fabric Fast-Track
  • You need a few specific reports built on an existing model, not a platform move
  • Hard requirement to keep the legacy tool running indefinitely alongside Power BI

Not sure which applies? Book a 30-minute scoping call and we'll tell you honestly.

Scoped per engagement.
Fixed once agreed.

Migration cost depends on the number of reports and the state of the underlying data models — so we scope after a short discovery session rather than guessing. Once agreed, the price is fixed.

BI Platform Migration

Scope and price are agreed after discovery and a short written brief. You receive a quote with a clear deliverable set — not a rough estimate we revise later.

  • Migration readiness audit
  • Report inventory and prioritisation
  • Data model rebuild where required
  • Power BI report rebuild
  • Parallel-run validation
  • Cutover, handover and team training
How pricing works

Discovery, then fixed

After discovery we define the exact report set and rebuild scope. The quote reflects that — locked before any work begins.

Scope changes are priced separately

Anything outside the agreed scope is a separate, priced change request. No creeping invoices mid-migration.

Not ready for the full move?

Start with a fixed 5-day Migration Audit — a written roadmap and readiness score you can act on, with no commitment to the full migration.

Common questions

Something not covered here? Ask directly.

We regularly migrate from Tableau, Qlik Sense, MicroStrategy, SSRS (SQL Server Reporting Services), Cognos and heavy Excel-based reporting. The target is Power BI on Microsoft Fabric. If your source platform isn't listed, get in touch — we'll tell you honestly whether a clean migration path exists.
No — and that's deliberate. Most legacy estates have heavy duplication and dashboards no one uses. We inventory every report, analyse usage, and split them into migrate, rebuild, consolidate or retire. Clients typically end up with 30–60% fewer reports that cover the same decisions, because we rationalise rather than copy clutter.
Parallel-run validation. The new Power BI reports run alongside the legacy system for an agreed period, and we reconcile the numbers field by field until they match within tolerance. Sign-off happens against that reconciliation — not against a screenshot that looks about right.
They'll deliver the same decisions, not necessarily the same pixels. We rebuild for Power BI's strengths rather than forcing a Tableau or Qlik layout into a tool it doesn't fit. Where a specific visual or interaction is business-critical, we replicate it; where the legacy design was a workaround for an old tool's limits, we improve it.
It depends on the number of reports and the complexity of the underlying data models, which is why scope is agreed after a short discovery session rather than guessed upfront. A focused single-department migration can run a few weeks; a full multi-source estate is longer. Whatever the size, the scope, timeline and price are fixed before work starts.
We assess them as part of the readiness audit. Where the existing data model is sound we connect to it; where it's the root cause of slow or unreliable reporting, we rebuild it on a Microsoft Fabric Lakehouse or Warehouse so the new reports sit on a clean, governed foundation rather than inheriting old problems. For the architectural decisions involved, see our guide on Microsoft Fabric architecture decisions.

Ready to leave
legacy BI behind?

Book a free 30-minute scoping call. We'll size the migration, tell you honestly whether it's the right move, and send a fixed-price quote.