← All case studies
UK mortgage lender · Fabric migration

Redshift, Tableau & Kleene.ai to Microsoft Fabric

A controlled migration from three separate data and reporting platforms to a governed Microsoft Fabric estate, reducing platform overhead while preserving critical reporting.

Amazon RedshiftTableau ServerKleene.aiMicrosoft Fabric
Redshift, Tableau & Kleene.ai to Microsoft Fabric
The migration brief

Move the work behind each platform

A UK mortgage lender's data and reporting work was split across Redshift, Kleene.ai and Tableau Server.

The move to Fabric had to cover those responsibilities while preserving critical reporting. Removing a licence was only useful once its work was covered.

Microsoft Fabric
Consolidation scope

Bring the data responsibilities together

The starting estate served three purposes: Redshift held the warehouse, Kleene.ai prepared data and Tableau Server delivered reporting.

Fabric became the connected target for data and reporting, bringing ingestion, preparation and modelling into the new estate. The scope extended beyond replacing individual products.

Reporting continuity

Reconcile before retiring dependencies

Reconciliation focused on calculations and reporting periods. Reporting meaning had to survive the move, not change silently with the platform.

Replaced dependencies could be retired once their work was covered. That condition connected the migration to a simpler estate, while keeping critical reporting in view.

Process → Architecture → Delivery

Our methodology

  1. 01DiscoverAgree the outcome, the decisions and the requirements.
  2. 02Current stateMap how the work and data flow today, with evidence.
  3. 03Root causesFind what drives the delay, rework or disagreeing numbers.
  4. 04ApproachAgree the target design, scope and measures of success.
  5. 05BuildBuild the process change, model or report the design calls for.
  6. 06OptimiseTest at real volumes; tune speed, cost and usability.
  7. 07ProductioniseRelease with managed deployment, monitoring and support.
  8. 08GovernSet owners, access and controls so it keeps working.
Swimlane process map: To-be: the retirement rule as a process. The steps are listed below the diagram.
Illustrative reference processTo-be: the retirement rule as a process Cover the work, check the reporting, then retire. Retirement is the outcome of coverage and reconciliation, never the starting point.
Steps in this diagram

Lanes: Migration team, Reporting owner, Steering group, Vendor / licensing.

  • Dependency in scope
  • Inventory its responsibilities
  • Cover each in Fabric
  • Reconcile calcs + periods
  • Matches?
  • Fix definition / data
  • Approve retirement
  • Retire + end licence
  • Simpler estate
Full size
Architecture diagram: Three platform responsibilities, one Fabric foundation. The components are listed below the diagram.
Reference architectureThree platform responsibilities, one Fabric foundation Warehouse, preparation and reporting responsibilities each get a Fabric home. The lines show consolidation scope; they do not allocate savings to individual products.
Components in this design
  • Amazon Redshift (warehouse)
  • Kleene.ai (data preparation)
  • Tableau Server (reporting)
  • Data pipelines (source ingestion)
  • Copy job (history from Redshift)
  • Dataflow Gen2 (replaces prep jobs)
  • Notebooks (complex transforms)
  • Fabric warehouse (Gold)
  • Reconciliation (calcs + periods)
  • Semantic model (same definitions)
  • Power BI reports (replace workbooks)
Full size
First page of the Platform Consolidation Tracker sample report
Delivery: interactive Power BI sample reportPlatform Consolidation Tracker Give the steering group one view of what each legacy platform did, where that work now lives in Fabric, whether calculations and reporting periods match, and what can be retired. Delivered with named owners, role-based access, release pipelines and a controlled way to change governed measures.
Full screen
Who it is for
Programme sponsor, migration lead, finance reporting owners.
Decision it supports
Approve retirement of each legacy dependency.
Report pages
Tracker

Reference design: how this pattern is typically built on Microsoft services. Component choices for a specific engagement depend on the client's environment and existing licences.

Microsoft icons are used under Microsoft's terms. Icon notices

Synthetic sample data, not client data.

Results in view

Annual platform saving

Client-reported result

Reported saving

AUD 75,000per year

Saving amount · AUD · axis starts at zero

Saving reportedAUD 75,000

Approximate client-reported annual platform and licensing saving.

Next step

Paying for several platforms that do one job?

Tell us what is happening. We agree priorities and scope before proposing any work.

Talk through your projectThe service: Fabric Migration & Power BI Optimisation