Migration· Case study 03
Legacy analytics platform migration to Rill
Led migrations of enterprise customers from a legacy analytics platform and older pipelines to the new Rill application, moving data, metrics, and dashboards without disrupting daily reporting.
1:1
metric parity with the legacy system
Architecture at a glance
- Legacy platform
- Parity queries
- Rill models + dashboards
- Trained users
01 The problem
Customers depended on legacy dashboards for revenue-critical daily decisions. A migration couldn’t lose data, change numbers, or leave users stranded.
02 What I built
- 1Inventoried each customer’s legacy datasets, metrics, dimensions, and dashboards, and mapped them to Rill models, metrics views, and explore and canvas dashboards.
- 2Rebuilt metric definitions as code (SQL + YAML), including tricky cases such as integer-division ratios, unnested array dimensions, and time-zone handling.
- 3Ran old and new systems side by side, with parity queries comparing totals and breakdowns before cutover.
- 4Planned cutover timelines with customer stakeholders, migrated users and access policies with SSO, and trained teams on the new platform.
- 5Upgraded customers’ deployed projects as the platform evolved, and kept repos agent-ready with READMEs and AGENTS.md / CLAUDE.md files.
03 Impact
Customers moved to a modern, code-defined analytics stack with numbers matching the old system, faster dashboards, and self-service editing, with the same technical owner through onboarding and support.
Related case studies
- StreamingReal-time AdTech bidstream pipelinesGBs/hr of AdTech events into real-time dashboards
- MigrationWarehouse & lakehouse to ClickHouse, with reverse ETL and integrity checksEvery hop reconciled for drift, hourly
- ObservabilityFleet observability, data-freshness alerting & usage billing30+ clusters monitored from one values file