Rewrite or migrate a legacy Java application: how to decide

Somewhere in your company there is a Java app that runs the business. It works, the rules inside it took years to get right, and the people who wrote most of it have moved on. Now it needs to reach the browser, and the meeting keeps circling back to one question. Do we start over, or do we move what we have?
This page is for the architect who has to recommend an answer and the budget holder who has to sign it. Whether to rewrite or migrate a legacy Java application is mostly a question of risk, and a rewrite carries the most of it. Our case is simple: keep your Java app running, and move it to the web one screen at a time, with your own Java team.












