Power BI Tenant Merger
Consolidating two enterprise reporting environments through the Sprint–T-Mobile merger
Overview
When Sprint and T-Mobile merged, two complete reporting ecosystems with separate Power BI tenants, schemas, and developer teams had to become one without business users losing access to their numbers. As Reporting & Analytics Manager, I owned that consolidation end to end.
The Challenge
Both organizations depended on their dashboards daily, so there was no downtime window. Sprint's data assets used different schemas that had to be standardized and validated against T-Mobile's, sensitive corporate data required governance controls during the transition, and Sprint's developers needed to become productive on an unfamiliar platform.
The Solution
Ran both Power BI tenants in parallel while migrating Sprint's data assets into T-Mobile's analytics ecosystem, standardizing schemas and validating data integrity at each step to enable unified post-merger reporting. Automated dataset refreshes with PowerShell and API connectors, implemented Row-Level Security across data models for governance compliance, and onboarded Sprint developers onto T-Mobile's platforms and best practices.
System Architecture
Ingest
High-volume ETL processes pulling training data from third-party LMS vendors and Sprint source systems, supporting 80,000+ daily active users
Transform
Schema standardization and data-integrity validation of Sprint assets against T-Mobile models, with complex stored procedures powering national retail sales metrics
Serve & Govern
Consolidated Power BI tenant with automated refreshes and Row-Level Security enforcing data governance across executive and field dashboards
Key Features
Zero-Interruption Consolidation
Managed both tenants in parallel through the merger, keeping analytics access uninterrupted for both organizations.
Schema Standardization
Migrated Sprint data assets into T-Mobile's ecosystem with schema standardization and integrity validation enabling unified reporting.
Automated Refresh Pipeline
Replaced manual dataset refreshes with PowerShell scripting and API connectors, ensuring data timeliness without intervention.
Row-Level Security
Implemented RLS within data models to meet governance standards and protect sensitive corporate information during and after the merger.
Results & Impact
Two enterprise reporting environments consolidated with uninterrupted access
Supported by high-volume ETL ingesting third-party LMS training data
Stored procedures backing national retail sales metrics on executive dashboards
Tech Stack Deep Dive
Platform & Governance
Data & Pipelines
Lessons Learned
Merging reporting platforms is a data-integrity problem first and a tooling problem second; validate before you cut over.
RLS designed early scales through a reorg; bolting it on later doesn't.
Onboarding the other team's developers is as critical to the migration as moving the data.