I've just finished migrating my home blog server to CS v1.1.

I spent much of the previous day performing a migration of my blog system from the venerable .Text v0.95 to CommunityServer v1.1.  There were a number of issues that turned what should have been a couple hours of work into a day of work.

You'll notice that I didn't adopt the v1.0 of the product when it came out, but rather waited for v1.1.  The reasons for this are:

1. CommunityServer supports and comes configured for multiple blogs on a single server, whereas .Text was a single blog.  There were difficulties in configuring CS to behave as a single blog server, which was what I needed.
2. There was no support at the time of release for a migration tool to take your .Text content and add it to your newly installed CS server.
3. It's a v1.0.

The first issue, the configuration as a single blog server, was resolved by a web-based configuration tool that provides detailed enough instructions on just how to configure CS v1.1 as a single blog server.

The second issue, the migration of .Text v0.95 to CS1.1 was resolved by this DotText-CS-Converter migration tool.  It's not perfect, there are a number of manual steps that you still need to perform that I think should have been built into the application itself, but you can't have everything.

The third issue...   1.1 > 1.0.  ;)

Related to the first issue, I've set up an alternative DNS entry dedicated for use by the blog.  So you'll now notice that the blog is hosted on http://blog.geeqs.net.  I've redirected requests going to the old blog to the new blog.

The migration and conversion took me 3 or 4 hours.  The setup as a single blog system took another hour.  I wanted to migrate my old .Text skin which was the "cogitation" skin to CS, but there is no skin migrator available.  As a result I had to spend another 4 or 5 hours customizing two of the packaged skins.  What you see in use now is a modification of the "PoisonIvy - air" skin. 

The modifications I made were to the CSS style sheets, which is my first serious use of CSS so far.  I've found it handy for "skinning" capabilities and very useful for maintaining a consistant style throughout a web page, but quite limiting in others.