Should You Rewrite or Modernize Legacy Software?

“Rewrite it” is often an emotional decision dressed up as a technical one.

Start with the business asset

If the legacy system still carries revenue, compliance, or operational knowledge, treat it as an asset under renovation—not automatically as debris.

Prefer modernization when

• Core domain logic is valuable and battle-tested
• The biggest pain is UX, integrations, or deployability
• You can carve stable seams and ship value incrementally
• A rewrite would recreate poorly understood edge cases

Prefer rewrite (or major replacement) when

• The platform cannot meet non-negotiable security or scale needs
• Knowledge has collapsed and reverse-engineering costs exceed rebuild costs
• The product shape itself is wrong, not merely dated
• Incremental change has repeatedly failed for structural reasons

A better question

Not “old vs new,” but “what is the cheapest way to buy a safer future without stranding customers?”

AI helps map codebases and generate migration options. Humans still decide the commercial risk.