BizTalk 2000/2002 is completely different to BizTalk 2004 (onwards). The base architecture and concepts are completely different. Even though Microsoft provided some tools intitially to migrate 2000/2002 projects to 2004 I don't think they are effective.
You might loose end up lot of time in the conversion, I would rather suggest you to take this opportunity to rearchitecture the solution (I know its not feasible in lot of cases). But if your organisation is thinking about migration, rearchitecture will be better approach.
Interesting one. BizTalk 2002 and 2006 R2 are so vastly different that I am wondering how much benefit would be gained. What kinds of artefacts are you wanting to update?
Personally, I would spend the time and re-architect the 2002 solution to take advantage of the new features of 2006 R2.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.