> It's also not that easy to just go rip out one processor 
  > for another on a huge legacy code base.

Unfortunately true. It's always a good idea to support more than 1 processor, ideally all used actively.

I've see many companies get burned by only having one. It takes ages to get another processor up and running.