Generally speaking, this post will only apply to those folks who either A) used .Text .95 as their blogging engine before migrating to CS 1.x (and are looking to upgrade to 2.0) or B) ran their CS site in “single” blogger mode (and are also looking to upgrade).  At first I thought I was the only one who experienced these issues, but I’ve seen some reports of the same behavior over on the CS.org forums.  There is the potential for either (or both) of the following behaviors:

• All comments show up under the blog owner’s name instead of the name the commenter left.  If you’re coming straight from .Text to 2.0 this will be obvious on all posts.  If (like myself) you went from .Text to 1.x, stayed on 1.x for a while, then went to 2.0, you’ll need to check your posts from prior to the date you migrated from .Text to CS.  While I haven’t nailed down the specifics as to why this happens, it appears there was a change from CS1.x in the way CS2.0 scans usernames in the cs_posts table.  A simple query will clear this up (end of this post).
• This one is a little harder to explain, but will be very obvious after the upgrade if you’re experiencing it.  On the aggregate page, there might be a hole in the dates of posts, i.e. you might see 3 posts you made recently, then it jumps to posts you made some time ago.  This one is more likely to affect bloggers who were in single blog mode in CS1.x, and the reason is that the IsAggregated bit (3) wasn’t flipped for the PostConfiguration table.  Again, the fix is trivial.

Fix for the first bullet:

UPDATE [database_name].dbo.cs_posts
SET PostAuthor = 'Anonymous'
WHERE ApplicationPostType = 4 AND PostDate < 'date_you_migrated_from_.Text'
GO
UPDATE [CS_2.0].dbo.cs_posts
SET UserID = 1001 -- your anon UserID might be different
WHERE PostAuthor = 'Anonymous' AND ApplicationPostType = 4 AND PostDate < 'date_you_migrated_from_.Text'

Fix for the second bullet:

UPDATE cs_posts 
SET PostConfiguration = PostConfiguration + 2 
WHERE PostID IN (SELECT p.PostID FROM cs_Posts p, cs_sections s WHERE s.sectionid = p.sectionid AND s.applicationtype = 1 AND p.ApplicationPostType = 1 AND p.PostConfiguration & 2 = 0)

These are the only 2 issues I’ve seen crop up (besides all out failures of course), which for a migration of this magnitude is pretty impressive IMO.  It’s worth mentioning that a migration tool to go straight from .Text to CS2.0 will be released soon.  In the interim you must upgrade to 1.1 first (you can skip 1.0), then upgrade to 2.0.  This can be done in about an hour or so.  Anyone who has already migrated from .Text to CS2.0 feel free to share your experience here, and of course if anyone needs any assistance feel free to contact me.  Happy migrating.

Sidenote:  I’ve had a couple of people contact me about my CS test site.  Seeing as 2.0 has been released (and 2.1 is still a few months off…Scott is targeting some time in May), I took it down.  As we get closer to a 2.1 release I’ll put it back up for beta testers.  If you need to see a demo of CS2.0 in action, you can go here.