Best Practices

• Review the pre-upgrade scan results files and address issues documented by the tool before beginning the upgrade process.

• Perform the chosen migration technique in a prototype lab environment before running it in the production environment.

• Use the in-place upgrade process only for those environments that are smaller than 30GB and for those environments without a large amount of customized web parts or other complexities.

• Examine third-party and custom designed web parts for interoperability with SharePoint 2010, checking the Microsoft Software Development Kit for the types of code supported in a SharePoint 2010 environment.

• Reset unghosted sites to standard SharePoint site definitions where possible to ensure consistency across sites.

• Use the STSADM utility to export and import sites from one server to another for the creation of a prototype server or to support an advanced migration scenario.

• Use the visual upgrade process to ease the transition to the new SharePoint 2010 visuals.

• Consider the use of an application layer inspection-capable HTTP filter device such as TMG Server 2010 to provide for the ability to split HTTP traffic to multiple servers, thus enhancing the ability to migrate a single namespace to a new server using a phased approach.