@xj25vm
According to Trevor, the window for the best possible time to migration was rapidly approaching with preparations barely done. That leaves a few alternatives: Skip it and put it off for another year, tell upper management to go stuff themselves, deal with the inevitable consequences, and approach your work without passion. Hire outsiders to make it happen, robbing you of the experience, the money, the adulation, and the pride, not to mention introducing even more unknowns and mistakes that you'll have to support later. Or bite the bullet and take prep to a fever pitch, get the hands-on, and build it exactly how you want it during the short time you have left. (I've done all three when I felt they were warranted.) There is no "oh, just duplicate the hardware, then buy double the software licenses and step up to the most expensive version of each product to enable the clustered changeover" option.
I don't really believe anyone who hasn't worked in an SME environment has any right to denigrate the decisions of passionate IT from the standpoint of their govt/enterprise background. Give advice, point out mistakes, offer alternatives, yes. But claiming that they should spend and best practice their way out of every jam shows an incredibly woeful misunderstanding an economic sector with constant cash shortages. Doing things under budget and early _is_ supporting business, in environments where IT is a business enabler, not a cost center always at odds with the rest of the company.
As the staff had not had previous experience with a massive switchover to 2008/Ex2010 etc, putting it off to another year wouldn't magically give them the experience to deal with every problem and make the switchover perfectly seamless. The only way to become deeply proficient is to make some mistakes and learn from them while you get everything working. That's the best possible outcome of any IT project.