Help for owners
My developer wants to rewrite my working software in a new framework
Short answer
A new framework is a reason for a rewrite only if the current one blocks something the business needs. Ask what exactly cannot be done today, what the rewrite will not improve, and whether the same goal can be reached by upgrading in steps. Do not approve it until you have a written plan and a way to keep the old system running.
Does this sound like your situation?
- The software works, but my developer says the framework is old and I should switch.
- The proposal for the rewrite has no list of business benefits.
- Customers see nothing new for months while the rewrite goes on.
- The developer mostly knows the new framework and not the old one.
- I cannot tell if this is good engineering or personal preference.
Why does this happen?
The framework is genuinely at the end of support
Sometimes the technology no longer gets security fixes and cannot be upgraded. Then a move is justified, but usually it can still be done in steps rather than in one big rewrite.
The developer prefers a different tool
Developers work faster in the tools they know. That is a real cost, but it is a different reason from the software being unfit. It should be stated plainly.
Hiring or cost worries
It may be hard to find people who work with the current framework. That is a valid business reason, and it can be checked against the real job market and your actual team.
The code is messy, and the framework gets the blame
Hard-to-change code is often a structure problem. Rewritten in a new framework by the same habits, it becomes hard to change again.
What can I do about it today?
- Ask for the reason in one sentenceAsk what the business cannot do today that the new framework would allow. A real reason can be said in a sentence.
- Ask what the rewrite will not changeAsk which problems stay after the rewrite. If the list is empty, the proposal is not honest yet.
- Ask whether it can be done in stepsA rewrite in pieces, with the old system running, keeps your customers served. Ask how the old and new would live side by side.
- Make sure nothing starts without a written planDo not allow work on the new version before there is a written scope, a list of what must keep working and a clear point to stop.
- Check that you own the code and accountsWhatever is decided, the repositories, hosting and store accounts should be in your company's name before big work starts.
When should I bring someone in?
- You are about to sign off on a rewrite and cannot judge the reasons.
- Your developer is the only person who knows the current system.
- A rewrite has started and releases of the working system have stopped.
How do I handle it?
- Test the claimI look at the current framework's support status from its official site, the state of the code and what the business needs in the next year, and write down whether the framework really is the blocker.
- Compare the options in writingKeep and tidy, upgrade in steps, replace one part at a time, or rewrite. Each option gets its work, its risk and what the business sees along the way.
- If a move is justified, do it in slicesOne area at a time moves, the old system stays live and every slice is checked against the list of what must keep working.
- Keep a rollbackEach switch-over has a backup and a tested way back, so a failed slice does not become an outage.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Is an old framework always a problem?
No. What matters is whether it still gets security fixes, whether you can find people to work on it and whether it blocks something you need.
Is a rewrite ever the right answer?
Sometimes, for example when the technology can no longer be run safely. Even then, replacing it in pieces is usually safer than replacing it all at once.
My developer is offended by my questions. What now?
Good engineers can explain a proposal in plain terms. An independent review of the proposal is a normal request, and it should not be taken as an accusation.
How was this page made?
I drafted this page with AI assistance. It is general guidance for business owners, not advice for your own system. Found a mistake? Tell me.