SNIP
>
>>, or if your main objective is just to "tighten" the code further as you migrate it.
>Always! I'm a refactoring addict:)
>
SNIP

Well I contend that you do yourself a HUGE (in case you didn't get that... HUGE) < s > disservice when you refactor for virtually any reason, particularly if the application has any degree of complexity to it..

I've got the recommended book on the topic and I've read the salient parts, and to me it is easily subject to mis-interpretation. The "yardstick" in the book are wide open to personal preferences because "smell" is highly subjective and always a personal thing.

But the most danger arises from inadequate testing of refactored code. It's easy to see the code you're refactoring but significantly more difficult to confirm correct operation of all other code that may depend on it. In many cases one inadvertently changes the prior sequence of events, usually with negative consequences somewhere.

I remain of the opinion that "refactoring" has been used as license by people who love to program, and who are in love with their own style (or, more correctly, hate any other style) of coding, to change code willy-nilly at their whim.
This simply leads to extended project schedules, breaking formerly working code and upsetting others who may also have to work in the same code base.

Anyway, good luck with your refactoring.