Skip Navigation Get In Touch
Case Study · Managed Services & Infrastructure

Migrating Salad and Go from Tableau
to Power BI.

A two and a half month migration from Tableau to Power BI, delivered as part of an ongoing managed services partnership with Salad and Go.

Salad and Go
QSR · Retail · Fresh Food
100+ locationsPhoenix, AZ
Microsoft Azure FabricPower BITableau MigrationManaged Services
Industry QSR · Retail
Engagement Ongoing managed services
Migration Window 2.5 months
Stack Azure Fabric · Power BI
01

Where they started.

Salad and Go's analytics and business intelligence reporting was built on Tableau. As the company grew and its technology strategy evolved, the decision was made to centralise the data platform around Microsoft Azure Fabric.

Tableau, while functional, no longer fit the target architecture. The company needed to migrate its existing reports and dashboards to Power BI without losing functionality, and ideally improving on what already existed. The Zig team took on the migration alongside Salad and Go's internal data engineering team.

Original BI Architecture
02

What was breaking.

Running Tableau alongside an Azure-centric data platform created unnecessary complexity and cost. The analytics layer was the outlier in a stack that was otherwise converging around a single ecosystem.

Maintaining two platforms meant duplicated effort, fragmented governance, and a slower path to building the unified data infrastructure the company needed to support its growth. The longer the migration was delayed, the more entrenched Tableau became, and the more expensive the eventual switch would be.

Inside the stack Microsoft Azure
  • Fabric
  • Azure SQL
  • Active DIrectory
  • Functions
  • Data Factory
Unified · Governed · One bill
Outside the stack Tableau
  • Report
  • Dashbord
External · Separate license · Fragmented governance
03

The approach

Rather than performing a lift-and-shift of existing reports, the team took the opportunity to redesign and improve the visualisations. The resulting Power BI dashboards weren't replicas. They took advantage of Power BI's native integration with Azure Fabric and its more flexible visualisation capabilities.

Step 01 · Audit

Map every report. Understand the intent behind each one.

Before touching Power BI, we catalogued the existing Tableau reports and worked with Salad and Go's data engineering team to understand what each dashboard was actually answering for the business.

Step 02 · Rebuild

Redesign on Power BI. Lean into Fabric integration.

Reports were rebuilt natively in Power BI rather than translated. We took the chance to improve filtering, drill-throughs, and visual clarity, using capabilities Tableau couldn't offer in this stack.

Step 03 · Hand-off

Knowledge transfer. Continued ownership.

The work happened in close collaboration with Salad and Go's internal team. Documentation, walkthroughs, and shared sessions ensured the new analytics layer was fully understood and owned in-house.

By the numbers
2.5months
Migration Delivered
1platform
Unified Analytics Stack
0
Tableau Licenses Retained
100+ stores
Reporting Without Disruption
04

The outcome.

Salad and Go achieved a fully unified analytics stack on Azure Fabric, eliminating the cost and complexity of maintaining a separate Tableau instance. The improved Power BI dashboards gave stakeholders better visibility into business performance.

The centralised platform created a foundation for more advanced analytics capabilities as the company continues to scale.

Before Tableau
  • Platform Standalone vendor
  • Azure integration External connector
  • Visualizations Limited by stack
  • Governance Fragmented
  • Licensing Two platforms
After Power BI on Azure Fabric
  • Platform Native to stack
  • Azure integration Built into Fabric
  • Visualizations Redesigned, improved
  • Governance Unified
  • Licensing One platform
What This Taught Us

Migrations are most valuable when they're treated as an opportunity to improve, not just replicate. A lift-and-shift preserves the status quo. A thoughtful migration improves on it.

Got a stack
that's holding you back?

We work with operators who can't afford downtime and won't settle for parity. Tell us what's getting in the way.

Start a conversation