← All work

Claims Migration · SHV (Adaptfy) · 2024

Moving business reports to one trusted data platform

Data migrationData platformReportingScope management
Moving house, keeping the numbers. Vintage-style collage of papers flying from an old filing cabinet into a blue safe

Overview

What is it?

Every quarter, teams report on the status of legal claims across the group. They upload spreadsheets, and the results show up in a dashboard used to follow risks and compare quarters.

I was the product owner of the migration.

The problem

A new home for the data

This reporting ran on an older platform. Meanwhile, SHV and Adaptfy were building Pulse, a shared data platform to bring the group’s data together and support faster, better-informed decisions. Claims reporting had to move there.

The challenge

Change everything behind the scenes, nothing in front

Files, processing and storage all had to move. For users, nothing could change: same files, same dashboard, same numbers.

Migration approach

How we moved it

1

Understand what’s there

We mapped the old setup: the files, the queries and what each part was used for.

2

Decide what to move

One part had been failing for months without anyone noticing, so we left it out. Exchange rate data already existed on the new platform, so we reused it.

3

Move only the history people need

Two years of data, enough to compare quarters and years.

4

Rebuild without changing the experience

New processing and a data contract behind the scenes; the dashboard stayed the same.

5

Automate the manual steps

Teams used to upload their files in pieces, and someone had to combine them by hand before the report could update. On the new platform, uploaded files are picked up, combined and processed automatically, and the team gets a message when it’s done.

6

Prove the numbers match

We tested that the new platform gave the same results as the old one.

Tech stack

What it’s built with

Data platformDatabricks
Transformationsdbt
WorkflowsAzure Logic Apps
ReportingPower BI
Data qualityYAML data contracts

Reflection

What I learned

1Treat a migration like a product.

A migration has users too. Success isn’t “the pipelines were moved”; it’s “people still trust and use the dashboard”.

2Parity first, improvements later.

We kept the scope to moving what existed, with no new features. Matching the old results first made the move safer; improvements can come once people trust the new setup.

3Silence is data too.

One part had been failing for months and nobody complained. That told us more about its value than any requirements document could.

4Discovery before estimates.

Hidden details, like current and historical data arriving in different structures, only showed up once we looked closely. Mapping the old setup before committing to a timeline made the plan more realistic.

5Reuse what the platform already has.

Exchange rate data had already been moved for another project. Reusing it saved work and kept one version of the truth.