Microsoft Sharepoint Products and Technologies Resource Kit eBook

1132 Part XI: Upgrading and Migrating to SharePoint Products and Technologies
Summary
The chapter detailed how you might plan and implement a migration and an
upgrade to SharePoint Products and Technologies, as follows:
■ SharePoint Team Services to Windows SharePoint Services. Both of
these products might seem to have similar functionality, as well as a similar
look and feel; therefore, you might find that you need little or no training for
you or your users to use the new version. However, there are some significant
differences between these two versions, and these were listed in this chapter,
such as document management, content approval, and the use of the ASP.NET
Framework that supports Web Parts. This is to become a Microsoft core technology
in the next version of ASP.NET. Web Parts are the same in Windows
SharePoint Services as they are in SharePoint Portal Server, so any Web Part
should work in either platform, with certain exceptions. You can migrate Share-
Point Team Services sites to Windows SharePoint Services websites by using the
Smigrate.exe tool. This tool migrates all site content and security settings and can
also be used to migrate sites between Windows SharePoint Services servers, site
collections, and to different locations within a site collection’s hierarchy.
■ SharePoint Portal Server 2001 to SharePoint Portal Server 2003. These
two products use different technologies to store their content. You can use an
upgrade strategy in which documents remain in the Web Storage System,
known in SharePoint Portal Server 2003 as the backward-compatible document
library. In this way, you can access these documents from the new portal,
while maintaining the features of the previous version, such as approval routing
and the ability to maintain multiple document profiles per document
library. Using the backward-compatible document library with SharePoint Portal
Server 2003, you can also maintain most of the PKMCDO application that
you might have created. The upgrade program will also migrate categories and
content sources to the new portal; however, digital dashboards are no longer
supported and you might need to migrate to the newer ASP.NET Web Part
Infrastructure rendering technology. Depending on the nature of your legacy
Web Part, you might be able to use a built-in Web Part such as the Content Editor
Web Part, the XML Web Part, the Page Viewer Web Part, or the Image Web Part,
or you might have to write a custom Web Part. If you need to continue developing
dashboard Web Parts, you need to design them to ease future conversion to
the Web Part infrastructure.