Legacy System Modernization: Refactor, Replatform or Rebuild?

Modernization moves an aging application to a secure, maintainable base. The main question is how much to change. Most successful projects change in stages while the system keeps running.

Signs a system has become a problem

• Security support has expired.
• Delivery has slowed and costs are rising.
• Performance has hit its limits.
• Hiring for the stack is getting harder.
• Compliance gaps are appearing.

The options

• Retain: leave it alone if it isn't needed in two years.
• Rehost: move it to new infrastructure, unchanged.
• Replatform: change the runtime or database with small code edits.
• Refactor: improve the code without changing behavior.
• Rearchitect: change the structure, often in slices.
• Rebuild: rewrite when it fits in a few months or nothing is worth keeping.
• Replace: buy a product instead.

Typical budgets for mid-size apps

• Rehost: 2–6 weeks, $10–40K.
• Replatform: 1–3 months, $25–100K.
• Refactor: 1–4 months, $30–120K.
• Rearchitect: 6–18 months, $100–500K.
• Rebuild: 4–12 months, $80–400K.

How to reduce risk

• Record baseline metrics and test critical paths first.
• Migrate in slices, using the strangler fig pattern where it fits.
• Run old and new in parallel, and rehearse data migration.
• Keep a rollback for each step.
• Use AI tools for repetitive upgrades only with automated test verification.