Business Upgrade Conversions
Taking your systems of the past
into the future
The software running your business was probably written a long time ago — and it still works, which is exactly why replacing it feels impossible. We convert it. Same rules, same numbers, same behaviour your people rely on, rebuilt on a foundation that will still be supported in twenty years.
The situation
It still works. That is the problem.
Nobody replaces working software for fun. It gets replaced when the last person who understood it retires, when the hardware it needs stops being made, or when a customer asks for something it simply cannot do. We meet businesses at exactly that moment.
One person knows it
The logic lives in someone's head as much as in the code, and that person is not going to be there forever.
It cannot be extended
Every new requirement is quoted as impossible, because touching one part of it risks breaking three others.
It is stranded on old hardware
A machine in the corner nobody is allowed to reboot, running an operating system that stopped getting patches years ago.
The spreadsheet became the system
What started as a workaround now holds real business rules, and no two copies of it agree any more.
How a conversion runs
Five stages, and you can stop after any of them.
No twelve-month black box. Each stage produces something you can read, use and judge for yourself before deciding whether the next one is worth it.
Excavate
We read the whole system — source, data, and the undocumented habits around it — and write down what it actually does today.
Agree the rules
You get the business logic in plain language. This is where the surprises surface, while they are still cheap.
Convert
The rebuild, on a current, supported stack. Your table and field names survive where it helps you recognise your own data.
Prove it
Old and new run against the same real inputs until every number matches. Differences get explained, not waved through.
Hand over
Source, tests, documentation and a walkthrough. Keep us on afterwards or don't — either way you are not locked in.
Why we are quick without being reckless
AI does the reading.
People sign the work.
We use AI seriously — to read decades of code faster than any team could bill for, to draft the conversion, and to generate the tests that check it. That is where the speed comes from, and we are not coy about it.
What we do not do is ship what it produces unread. Every rule it infers is confirmed against the original. Every converted path is reviewed by a person who is accountable for it. When the machine and the source disagree, the source wins and a human decides what to do about it.
Anything that touches money gets read by a person twice. That rule has never been worth breaking to save a day.
What you are left holding
A system your next developer can pick up.
The point of a conversion is not that it is new. It is that it is legible — to the person who maintains it after us, including you.
Talk it through with us- 01Your source, in your handsHanded over in your own repository. No escrow, no dependency on us continuing to exist.
- 02Tests that describe the businessNot coverage theatre — the rules you agreed in stage two, written down as something a machine checks.
- 03Data that came across wholeReconciled record by record, with the exceptions listed rather than quietly dropped.
- 04Documentation worth readingWhy the odd decisions are the way they are, which is the part that is always missing.
- 05A stack that gets security patchesCurrent, mainstream and supported — chosen for boring longevity over novelty.
Start here
Tell us what you are still running.
What it is, roughly how old, and what finally made you look into replacing it. We read every one of these ourselves and reply with a straight answer about whether a conversion is worth doing — including when it is not.
No sales sequence. No obligation. A real reply from a person.