Help for owners
My rewrite stalled and now the old and new systems both run
Short answer
A half-finished rewrite means every change is made twice or one system is neglected. Stop adding features to both, write down what each system does and which customers use it, then decide whether to finish, pause or fold back, before spending more.
Does this sound like your situation?
- Staff must update data in two places.
- Some customers are on the new system and some on the old.
- The rewrite was meant to be done months ago.
- Bugs get fixed in one system and not the other.
- Nobody can say what the new system still lacks.
Why does this happen?
The old system kept earning
Because the business could not stop, the old system kept receiving changes and the new one kept chasing a moving target.
The last 20 percent is the hardest
Edge cases, odd customers and rarely used reports tend to be left until the end, and that is where the time goes.
Scope grew during the rewrite
Wanting to improve things while rewriting turns a copy into a new product that never ends.
The data move was left until last
Moving real data safely is slow and risky, so it is often deferred and then blocks the switch.
What can I do about it today?
- Freeze new features in the old systemAgree that only urgent fixes go into the old system while you decide.
- List what each system doesAsk for a plain table of features, and mark what exists in the old one, in the new one, or in both.
- Find who uses whichNote which customers, staff and reports rely on each system.
- Do not turn the old system offSwitching it off before the gaps are known can stop operations and lose data.
- Ask for a finish plan with an end dateRequest a list of what remains, in order, so you can decide whether to continue.
When should I bring someone in?
- Money is being spent on two systems with no end date.
- Data in the two systems no longer matches.
- The people who started the rewrite are gone.
How do I handle it?
- Take stockI compare the two systems feature by feature and check the state of the data.
- Estimate what remainsThe remaining work is listed in ranges with the biggest unknowns shown, not hidden.
- Offer optionsYou get clear options: finish, pause with a plan, or fold the useful parts back into the old system.
- Move in small stepsCustomers or modules move one group at a time, with a way back for each.
- Retire the old system lastThe old system is switched off only after its data is verified and a backup is stored.
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?
Should I just start over again?
Not before comparing options. A second restart often repeats the first one's problems.
Can the two systems keep running?
For a while, yes, but they double the maintenance and the risk of mismatched data. Set an end date.
Who decides whether to continue?
You do. The decision should rest on a clear list of what remains and what each option takes.
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.