by Shams Zuha

I have recently completed a SharePoint 2010 upgrade project for a large technology firm. During this project, I took the time to compile a list of the roadblocks that popped up and I’d like to share them with you. I’m sure that anyone who’s worked on SharePoint 2010 for an extended period of time will have their own list, so please feel free to comment below on other issues that have popped up and I’ll do my best to answer them!

Without further delay, the following is a list of “gotchas”, recommendations and other things to consider:

  • Always execute the Pre-upgrade checker to get your SharePoint inventory.
  • Make sure that your portal is consistent and there are no issues because if you proceed with issues in the current environment then it would be like the old saying says: garbage in, garbage out.
  • Make sure that your content databases do not have too many site collections because it will impact the performance of the upgrade process. I would recommend having no more than 1000 collections per database. In our case, it took almost a day and a half to upgrade the database that had 6000 site collections. After splitting the site collections into 6 databases, we could execute the upgrade process for all six databases concurrently and it took around 5 hours. So basically it depends on your upgrade window, you might decrease the number of site collections per database to expedite the process even further.
  • Test your custom master page with your content during the analysis phase to accommodate ribbon functionality and ensure that your master page is compatible with 2010 version.
  • During capacity planning, consider the increase in content database files, both data and log files. I would recommend documenting the change in file size during your test upgrade and pad a few extra gigs to ensure smooth completion. It will be critical to the success of your final upgrade process because if you database upgrade fails, you will have to start the database upgrade from scratch.
  • I would recommend upgrading the site collections right away so any potential issues can be identified and resolved right away. If you go live with a 2007 visual interface and leave it up to the site owners to choose themselves, it will be a bigger effort to fix it later. You may apply the upgrade using the following PowerShell script for all sites in the site collection

$SiteCollection=Get-SPsite http://sitecollectionURL

foreach($SPWeb in $SiteCollection.AllWebs){$SPWeb.UIversionConfigurationEnabled=$true;$SPWeb.update();}

  • You may experience issues with some of the web parts that were upgraded initially from 2003 to 2007. I would suggest using a newer version of the web part to resolve the issue.
  • We had trouble with some of the Content Query Web Parts and the XSLT had to be adjusted a little bit.
  • There might be a case that you do not want to use a feature that was installed in your 2007 platform anymore and at the same time, you do not have the liberty to get rid of it in 2007 production. In that instance, I would suggest using the Feature Admin tool to get rid of the unwanted features. It allows you to remove a feature based on the GUID from the whole farm.
  • I would recommend reviewing Site Columns deployment features because SharePoint 2010 expects ‘Required’ attribute which was optional in 2007 and might be missing.
  • In SharePoint 2007, you had the option to enable Audience targeting on a list and then group the list results using the Audience that the logged-in user belongs to. SharePoint 2010 allows selecting the <Audience> as a group however the functionality does not work. I would suggest looking for these scenarios and identify an alternate mechanism before converting to 2010.
  • I would recommend using the Search Migration tool to migrate all search settings from 2007 environment to 2010.

http://msdn.microsoft.com/en-us/library/ff828776.aspx

  • SharePoint 2010 does not support the site & list templates created in SharePoint 2007. I would recommend the following steps:
    • Creating a new site collection with a separate database
    • Create all the sites and lists using the templates in 2007 version
    • Upgrade the database to 2010
    • Save the lists and sites as template in 2010 to be used after migration

Click Here to view a SharePoint 2010 Webinar! [vimeo http://vimeo.com/38657516]

Do you have any more tips or tricks you’d like to share? Comment below!

Read more about SharePoint here!