As you can see from the above screen shot I have managed to migrate my public facing SharePoint site (http://supportweb.ciaops.net.au) into SharePoint 2010. I tried this a number of ways (in place migration, database swing, etc) all with abject failure. The most likely reason was a number of additional features and templates that I’ve added over time.
This time I used stsadm –o backup to save a complete copy of the site and then used ststadm –o restore to recover the site to a new clean SharePoint v3 installation. From there I did a database swing migration across to SharePoint 2010 which finally resulted in success.
That migration also migrated the blog that you are now viewing but as the screen shot above shows I don’t think it is as nice as what I have in SharePoint v3. So at this stage I think I’ll leave the existing site as it is until I can ‘tart’ SharePoint 2010 up a little. However, what this experience has shown me is that the quickest way to do a migration (and strip away the incompatibilities) seems to be to use stsadm to do a back and restore of the site to a new clean SharePoint v3 installation and from there to do a database swing migration.
Perhaps what it has also taught me is that the less modifications you make to SharePoint the easier it is to migrate, but that is pretty much the same with any other application then isn’t it?