I've been there in the last 2 years, and we went for massive spaghetti ball to about 50% rewrite and 60% under tests. I second most comments against the "full

I've been there in the last 2 years, and we went for massive spaghetti ball to about 50% rewrite and 60% under tests. I second most comments against the "full rewrite" here: - source control it - get a local environment if you can - write tests before changing/deleting something Adding tests can be hard at first. The book "Working Effectively With Legacy Code" by M Feather contains useful techniques and examples. Be wary of the Chesteron's fence : "reforms should not be made until the reasoning behind the existing state of affairs is understood". Don't fix or remove something you don't understand.