Ah, the joys of legacy code. :) The "right" approach depends on how much code there is ... and what are the consequences if you break it. Millions of lines of crufty old business-critical code is the nightmare I've faced (and is faced daily by P5P ;-).

My mandatory list of references on this topic: Re: Strategies for maintenance of horrible code? (Legacy Code References)