Mickel Tech · Field Guide 04
Is your legacy codebase
agent-ready?
20 checks that decide whether agent-led modernisation will hold up, and what to build first if it will not.
- For
- CTOs, VP Engineering, heads of platform
- From
- Gordon Mickel · mickel.tech
- Practice
- Agentic SDLC · legacy migration and modernisation
- Use
- Answer honestly, per system, with someone who knows it
01 / How to use this
20 checks, one afternoon.
Agents read a legacy codebase faster than any team you can hire, and they can do the bulk of a migration. Whether the result holds up depends less on the model than on what surrounds it: what the agent can verify, what it may touch, and who signs off. Most of that lives in your codebase and your organisation rather than in the tool.
Work through the checks with someone who knows the system. Tick what is true today, not what is planned for the quarter. Each check carries a line on why it matters, so an unticked box tells you what to build rather than only what you lack.
Score per system. A single organisation is routinely ready in a young service and nowhere near it in the core that carries the revenue, and the gap between those two answers is usually the more useful finding.
The checks are deliberately technology-agnostic. COBOL, Delphi, VB6, an ageing Java or .NET monolith, a PHP application that grew for fifteen years: readiness looks much the same from the outside.
Agents do the heavy lifting on old code. What keeps that work correct is the engineering around them, and most of it is built before the first agent runs.
PAGE 1 / 6 · MICKEL TECH · LEGACY READINESS CHECKLIST
05 / Reading your answer
What the count tells you.
16-20
Ready. Move one bounded context end to end, check it against the old system, and use what it cost to estimate the rest.
Ticked
10-15
Workable. Close the gaps in the safety net and in the room-to-move rows first; those two gate everything else on the list.
Ticked
under 10
The first phase of the work is building the ground the rest stands on. That is the normal starting point for a system of this age, and it is far cheaper to find here than mid-migration.
Ticked
What an expert adds
Everything above you can do yourselves, and if you do, the migration gets easier whoever ends up running it. That is a fine outcome for this document.
What I add is a fixed-shape engagement, sized in scoping. A typical shape is about a third of one team for about three months: we generate a documentation layer for the whole codebase, move one bounded context checked against the old system, and turn what that cost into an estimate for the rest. If it stalls, you keep far better documentation than you had.
The context crosses over by one of two routes. Strangler-fig rebuilds it feature by feature while old and new run side by side; clean-room rebuilds the whole context from its specs and switches it over in one step. Whether the data can move in stages usually decides which.
Engage
A 30-minute discovery call is the cheapest way in.
Bring your answers. We go through where the gaps are, whether agent-led modernisation is the right shape for this system, and what a first slice would look like. If it is not a fit, I say so on the call.
- Book
- cal.com/gmickel/discovery30
- Email
- gordon@mickel.tech
- Read
- mickel.tech/sdlc/legacy-modernisation
- Practice
- Binningen, CH · DE / EN