Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

Should I rewrite my old software or keep fixing it?

Short answer

Rewriting everything at once is rarely the first answer. A common safer approach is to replace the system in pieces while the old one keeps running. A rewrite is justified when the code cannot be changed safely and the business rules are understood. Do not start one before you have a written list of what the software must do.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • Every small change takes weeks and breaks something else.
  • Only one person understands how it works, or nobody does.
  • A developer told me to throw it away and start again.
  • It cannot connect to new tools, or the technology is no longer supported.
  • I am afraid a rewrite will cost a lot and not match what I have now.

Why does this happen?

  1. Software gets harder to change as it grows

    Microsoft's architecture guidance describes the same situation: as systems age, the tools and architectures they are built on can become obsolete, and added features make them more complex and harder to maintain or extend.

  2. Replacing a whole system at once is risky

    The same guidance says it is difficult to replace an entire complex system, and describes migrating gradually, using the old system for features not yet migrated.

  3. Business rules are hidden in the code

    The old code contains decisions made over time, such as discounts, tax and special customers. A rewrite that does not find them loses them.

  4. Nobody can prove what works

    Without tests and documents, there is no way to compare the old and new versions and say the new one is correct.

  5. The urge to rewrite hides a smaller problem

    Sometimes the pain comes from a single slow screen, a bad database or a missing integration, and not from the whole system.

What can I do about it today?

  1. Write down what the software must doIn plain words: the ten things your business could not live without, in order of importance.
  2. List what hurts mostSlowness, errors, cost of changes, missing features, risk. The biggest pain is where to start.
  3. Keep the current system runningDo not switch it off or let anyone start deleting code. It is also your best description of what the business needs.
  4. Secure the code, data and accountsCheck that you hold copies of the source code, the database and every login.
  5. Ask for options, not one answerAsk any developer to show the cost and risk of repair, step-by-step replacement and full rewrite, side by side.

When should I bring someone in?

  • You have already been quoted a rewrite and cannot judge it.
  • No one has a full copy of the code.
  • The system is failing and you need to decide quickly.

How do I handle it?

  1. Review the code and the dataI read the code, the database and the hosting, and tell you plainly what condition it is in, and what is risky.
  2. Compare three pathsRepair what hurts, replace in pieces behind the old system, or rewrite. You receive each path with its risk and what it asks of you.
  3. Start with the smallest useful pieceIf it goes step by step, the first piece is something that matters to the business and can be checked against the old behaviour.
  4. Prove each pieceEach replaced part runs next to the old one first, with a tested rollback, before it takes over.

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 a rewrite ever the right choice?

Yes, when the code cannot be changed safely, the technology is unsupported and the business rules are understood. Even then I prefer to deliver it in parts.

How long does modernising take?

It depends on the size and state of the system, so I give an estimate only after reviewing it.

Will the new version look different?

Only if you want it to. Keeping the same screens and behaviour first lowers the risk for your staff and customers.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.