Shannon asks me the other day (general wording is mine, not his):
Will there be an option for all the .Text holdouts who didn’t want to move to Community Server 1.0? Will we have to upgrade to an interim build first and then to 2.0, or can we go straight from .Text .95 to CS 2.0?
First off, I’m ecstatic that he’s considering the move over to the CS platform as obviously it’s a kickass product, and .Text is largely dead (though subText seems to be doing pretty well). Second, that’s a fantastic question: I wrote my own migration tool back when CS1.0 was released that was essentially a database to database migration using DTS; Kevin Harder came along and trumped me with a very nice tool of his own that used the CS API to migrate the data, which became the defacto migration tool in the community and was generally easier to use and less error prone.
So I emailed Kevin and asked him just that…the answer is a resounding yes that he’ll be updating his migration tool to support a .Text .95 to Community Server 2.0 scenario. Before anyone asks…there is indeed a timeframe in place, but nothing is nailed down yet so I can’t mention it here. It’ll be done when it’s done, and it’ll definitely be done by the 2.0 RTM. This is great news though, and hopefully CS2.0 will be a compelling enough upgrade to get the rest of the .Text folks over to the new platform.