Zendesk to Microsoft Fabric Migration: 40% Resolution Time Drop & £180K+ in Annual Costs Avoided
Numlytics delivered a complete Zendesk to Microsoft Fabric migration for a growing global SaaS business - building a fully automated incremental Fabric pipeline from the Zendesk REST API through a Bronze-Silver-Gold Medallion Lakehouse on OneLake, and serving real-time support analytics to Power BI via DirectLake. Within 60 days of go-live: average resolution time down 40%, two critical escalation bottlenecks identified and eliminated, and £180K+ in annual SLA penalty and churn costs structurally avoided.
The Challenge: Thousands of Tickets, Zero Unified Support Analytics
The client operated all customer support on a mature, well-configured Zendesk deployment - thousands of tickets, structured SLA tiers, CSAT surveys, and agent routing logic fully in place. The data existed on paper. In practice it was completely inaccessible for analytics. Teams relied on static Zendesk reports, reactive manual exports, and custom API queries that took hours to produce and were outdated before anyone read them.
- Fragmented support analytics: Tickets, agents, SLA metrics, and CSAT scores existed in separate Zendesk API endpoints with no unified Lakehouse model, no single view of end-to-end support performance existed across the organisation.
- Stale visibility during incidents: Without automated incremental pipelines, leadership saw ticket volume trends hours after the fact - making real-time response to SLA breaches impossible during high-severity incidents.
- Reactive SLA management: Breached deadlines were discovered retrospectively in weekly review meetings the intervention window had already closed by the time the breach was visible.
- Disconnected customer context: Support ticket data could not be joined with customer segments, product usage, or revenue data meaning high-value customer escalations received no differential handling.
- High analyst overhead: Two analysts spent roughly 60% of their time writing custom API queries and manually stitching data exports a direct drag on the team's capacity to produce actual insights.
Business cost of inaction: Without an automated Zendesk data pipeline and real-time Microsoft Fabric analytics layer, the client estimated £180K+ in annual losses from SLA penalty payouts, agent inefficiency caused by invisible bottlenecks, and preventable churn from delayed issue resolution, problems a Zendesk Microsoft Fabric migration was built to eliminate structurally.
The Numlytics Zendesk to Microsoft Fabric Migration Solution
Numlytics designed a complete Zendesk to Microsoft Fabric migration starting with structured data profiling of the Zendesk API before any pipeline work, building an automated incremental Fabric pipeline with watermark logic, and delivering four real-time Power BI dashboards via DirectLake on the Gold Lakehouse tier.
-
01Zendesk Data Landscape Audit and API Profiling
Numlytics mapped all Zendesk API endpoints in scope - tickets, users, organisations, SLA policies, satisfaction ratings, ticket events, and custom fields and ran structured profiling before any pipeline work began. This phase caught three critical data quality issues: tickets re-opened multiple times had ambiguous resolution timestamps; SLA thresholds had changed twice across the three-year history; and custom fields added over time were missing entirely on early records. Profiling before pipeline build is non-negotiable on any Zendesk Fabric migration without it, the Power BI numbers would have been wrong from day one.
-
02Microsoft Fabric Pipeline - Incremental Watermark Architecture
The automated Microsoft Fabric pipeline was built using four activity types: Copy Data (pulling from Zendesk REST API), Lookup (reading and writing the watermark timestamp), ForEach (looping across ticket batches), and Notebook (running PySpark transformation logic). All transformation logic was kept inside the Notebook activity within the ForEach loop making the entire journey from Zendesk API to clean Delta table a single, auditable unit. The watermark approach reads the last successful
updated_attimestamp and fetches only what changed since. Incremental runs completed in under 8 minutes versus 47 minutes for a full historical load. -
03OneLake Medallion Lakehouse - Bronze, Silver, Gold
The Fabric Lakehouse was structured in three tiers on OneLake, all in Delta Parquet format for ACID compliance and time-travel capability. Bronze holds raw Zendesk API output exactly as received. Silver applies data quality rules: deduplication, resolution timestamp standardisation, SLA policy version mapping across three years of history, and custom field backfill for early records. Gold contains reporting-ready aggregates for Zendesk Microsoft Fabric Power BI: ticket performance by agent and team, SLA compliance by priority tier, CSAT score trends, and first-contact resolution rates.
-
04DirectLake Power BI Dashboards - Four Stakeholder Views
Rather than import mode - which introduces minutes of lag and stale data between scheduled refresh cycles Numlytics implemented Zendesk Power BI DirectLake connectivity. DirectLake reads directly from Delta table files on OneLake so dashboards reflect the latest pipeline output the moment they open. Four role-separated dashboards were built: Agent (own tickets, SLA status, CSAT), Team Lead (team performance, volume trends, escalation flags), Executive (KPI summary, cost per ticket, resolution benchmarks), and SLA Operations (live breach alerting). Role-level security was configured once at the semantic model and applied across all four dashboards.
-
05Historical Backfill and Incremental Sync Go-Live
The full three-year historical backfill completed in 47 minutes loading all tickets, events, and satisfaction data through the Medallion pipeline. Incremental syncs went live immediately after, running every 15 minutes using Zendesk's incremental export endpoints with watermark tracking. The pipeline ran unattended for 30 consecutive days before handover, logging zero failures. The support team had live SLA monitoring, agent dashboards, and CSAT trend data within the same business day as go-live.
The Results
- Static Zendesk reports, hours-old data
- SLA breaches found in weekly meetings
- 60% analyst time on manual exports
- No cross-system customer context
- £180K+ annual loss from avoidable breaches
- DirectLake Power BI refreshed every 15 min
- Live SLA breach alerts - intervene before breach
- Analysts freed for insight, not data wrangling
- Gold Lakehouse joins tickets with customer data
- £180K+ cost structurally avoided year-on-year
We knew the data was in Zendesk. We just had no way to get to it in any form useful for decision-making. Numlytics built the pipeline, profiled three years of API data before touching a single dashboard, and had us live the same week. The DirectLake dashboards are instant no waiting for a refresh, no stale numbers. Within two months we identified two escalation bottlenecks we genuinely did not know existed. One of them had been costing us roughly £40K a quarter in SLA penalties. That finding alone justified the entire engagement.
Key Engineering Insights from This Zendesk Microsoft Fabric Migration
Keeping all transformation logic inside the Fabric pipeline within a Notebook activity triggered by the ForEach loop rather than a separate external layer kept the entire journey from Zendesk API to clean Delta table as a single, auditable unit. Every run produces a clear activity log showing Copy Data, Lookup, ForEach, and Notebook status in one place. One pipeline. One place to look. One place to fix. This is the architecture that makes a Zendesk Microsoft Fabric deployment maintainable at production scale.
The client's previous process pulled the full ticket history on every export the same 100K+ records every time. Watermark logic reads the last successful updated_at timestamp and fetches only what changed since. Incremental runs completed in under 8 minutes; the full historical load took 47. That gap widens every week as ticket data grows. Skipping watermark logic produces a Zendesk Fabric pipeline that gets slower and messier with every run.
The Zendesk interface looks clean. The API data is not. Tickets re-opened multiple times had ambiguous resolution timestamps. SLA thresholds had changed twice across three years. Custom fields were missing entirely on early records. Structured profiling before any pipeline work caught all of it. Without that phase, the Zendesk to Microsoft Fabric migration dashboard numbers would have been wrong from day one and wrong in ways that are difficult to detect retrospectively.
Import mode copies data into the Power BI dataset on every scheduled refresh minutes of lag, stale data between cycles, no path to near-real-time. Zendesk Power BI DirectLake reads directly from Delta table files on OneLake, so dashboards reflect the latest pipeline output instantly. This was the enabling change that made proactive SLA breach alerting possible - structurally impossible with import-mode datasets.
Pipeline reliability and dashboard accuracy are table stakes. The real measure of a successful Zendesk to Microsoft Fabric migration is what the organisation could do that it could not before. Within 60 days: two escalation bottlenecks identified and eliminated, shift patterns adjusted on actual volume data, average resolution time down 40%. Support leadership had been making staffing decisions on instinct the data existed in Zendesk but had no path to analysis until Numlytics built one.