Review the sites and workspaces in the environment that is to be migrated and migrate only what is being used to the new environment to save time and resources.
To gain greater acceptance of the new SharePoint 2003 environment, keep the results of the initial migration as close as possible to the original environment from an end-user perspective. Introduce new features gradually, after users have time to adapt.
Prior to a SharePoint Team Services migration, do the following on the Team Services server:
Install the update for SharePoint Team Services v1.0.
Configure the Team Services site to be read-only.
Increase the paging file size if the site is large.
Prior to restoring a Team Services site to Windows SharePoint Services, do the following in the destination Windows SharePoint Services environment:
Increase the IIS timeout setting to at least 65,000 seconds.
Enable migration of the anonymous user in IIS if anonymous user access settings are to be migrated.
Disable full-text searching in SQL Server 2000.
If quotas are being used on the destination virtual server, set a high quota limit during the migration to enable the data to be completely migrated. The quota can be adjusted down, if necessary, after the migration.
Make sure that the virtual server upload setting is high enough to migrate all groups of files.
Configure the number of user alerts at a high enough level to enable successful migration of information with the appropriate alerts issued.
Review the blocked file types list and remove any file types from the list that may be included in the site that is to be migrated.
Make sure that all users who are to be migrated have valid email addresses.
When migrating a SharePoint Team Services site, if the SharePoint Team Services server is slow or has limited memory, run the Smigrate utility from another faster computer.
Remove Front Page 2002 Server Extensions from the SharePoint 2003 environment unless they are explicitly needed by an application.
Create a separate user account for restoring the Team Services content with an email address of a person who is knowledgeable about the migration (to be used when the owner of the content cannot be identified).
When migrating a SharePoint Team Services site that contains many subsites, back up each subsite, or logical groupings of subsites, into separate .fwp files to provide more flexibility when importing the sites to Windows SharePoint Services.
When migrating SharePoint Portal Server, log on as a member of the local Administrator's group.
Before migrating a SharePoint Portal Server 2001 server, use a combination of Ntbackup and MSDMBack Utility when backing up a SharePoint Portal Server 2001 server to ensure that both the server and the portal content are backed up.
Be familiar with the list of features and customizations that are not directly migrated and create a plan to deal with any of these items that exist.
Review the list of common issues included in this chapter to be aware of issues that may occur during the migration process, and to determine what to do should any occur.
