Notes from recovery and modernization work — specific constraints, not generic praise.
AmberPath found three forgotten batch jobs that still posted stock movements after we thought that module was dead. The modernization plan finally matched how the warehouse actually worked.
— Operations lead, regional distributor · Legacy modernization
The recovery assessment was slower than our board wanted, and they said so. That honesty mattered: we learned half the “Git history” was a laptop zip from 2017. We stopped arguing about rewrites until the missing pieces were listed.
— CTO, professional services firm · Codebase recovery
Their debt audit named the payroll export path as the real blocker, not the UI everyone complained about. We funded that fix first and hiring interviews got easier because juniors were no longer afraid to touch the wrong class.
— Engineering manager, NSW manufacturer · Technical debt audit
We brought AmberPath in after a stalled .NET migration. They sat with our accounts team through a month-end rehearsal and caught a rounding difference our staging data never showed. The roadmap still asks a lot of our squad, but at least the order of work is believable.
— Product owner, membership organisation · Legacy modernization
A coastal logistics client ran a 2009 desktop console that printed run sheets for drivers. Source lived in an abandoned SVN mirror; production had patches never checked in. AmberPath’s recovery assessment compared installer hashes with the live binaries, interviewed two long-serving dispatchers, and rebuilt a branch that could compile again on a locked VM.
Only then did the modernization engagement begin. The roadmap kept the console’s print flow intact for six months while a strangler service took over address validation. Incident volume during cutover stayed within the band operations had agreed in the findings workshop — not zero, but predictable.
If your situation resembles any of the above, request an assessment and tell us what still runs in production that nobody wants to open.