A family funeral home with thirty years of records trapped in a system it was leaving
Built an extraction agent that lifted three decades of client and case records out of a retiring legacy system and landed them, structured, in one consolidated platform that now holds every file as a single source of truth, with the firm's legal retention obligations preserved.
A small family-run funeral home, three people sharing the desk, the technical work, and the management, had thirty years of records sitting on an internal server inside an aging back-office system the trade was quietly retiring. Some of it they were legally required to keep for years. They wanted to move to a newer platform, but the obvious path was to retype it all by hand, decades of family files, contracts, and account history, one record at a time. For a three-person office, that was not weeks of work. It was months no one could spare without stopping everything else.
Underneath the migration sat a quieter problem. No single platform fit the way the trade actually runs, so the firm had spread its work across several tools and a server full of archives. Finding the current version of a file, knowing what had already been done on an account, and keeping the legally required history intact all got harder as the years piled up.
We started where the fear was: the data. Rather than re-key thirty years of records, we built an extraction agent that read the old system directly and pulled every client, case, and account record out automatically, structured into clean rows the new platform could accept. The extraction is AI-driven with a deterministic fallback behind it, so messy or inconsistent old entries still produced a usable record instead of failing or being silently dropped.
That structured history landed in one consolidated platform built around how the firm actually works: a single source of truth holding every client and every case file, a structured intake so the same detail is entered once at the right spot, role-based access for the small shared team, notes kept by role, and a view of every open file at a glance. The records they are legally required to keep came across intact and stayed searchable instead of frozen on a server no one wanted to touch.
The migration that would have meant months of manual re-keying happened in weeks, with none of the thirty-year archive retyped by hand. The full history moved across in one pass, structured and searchable, and the legally required records came with it unbroken.
The firm also stopped working out of several tools and a shared drive. There is one source now, the status of every file is visible in one place, and the small team can find any record without remembering which system it last lived in. The work left for a person is checking and judging the file, not copying it.
“Thirty years of files were sitting on our server, and the only way forward looked like retyping all of it. There are three of us. We did not have the months that would have taken.”
Have a mess like this?
Tell us where time and money are leaking. We’ll map the fastest high-ROI win, usually a Pilot that pays for itself.
