1. Migrating from SharePoint 2003 to SharePoint 2007 December 7, 2007 Captaré Consulting, LLC Coskun Cavusoglu Senior Consultant, MCP Microsoft Certified Technology Specialist for SharePoint® Portal Server Malcolm Eaton Director of Operations Microsoft Certified Technology Specialist for SharePoint® Portal Server

2. Agenda  Before Upgrade  Upgrade Approaches  In-Place  Database Migration  Gradual  Gradual Upgrade Demo  How Search is Affected  Best Practices  Common Issues  A Different Approach  Third-Party Option:  CorasWorks Data Migrator 2

3. SharePoint Roadmap Content Management Server 2002 Microsoft Office SharePoint Server Windows SharePoint Services “v3’ SharePoint Portal Server 2003 Windows SharePoint Services v2 3

4. Before Upgrade  Run and test a full backup  Install Windows Server 2003 SP1  Install SharePoint SP2 across entire farm  Run the pre-upgrade scan tool  Reports common issues you must address  Lists ghosted and unghosted pages  Lists all site definitions in use  Updates WSS lists (requires WSS SP2) so they can be upgraded 4

5. Before Upgrade (Continued)  Determine how to handle FrontPage customizations AKA unghosted pages  Install other prerequisites  ASP.Net 2.0  TIP: Test custom Web Parts with ASP.Net 2.0  Windows Workflow Foundation 5

6. Upgrade Special Cases  Changing languages  Moving to Microsoft’s "Longhorn”  Upgrading from:  SharePoint Portal Server 2001  SharePoint Team Services  Microsoft Content Management Server 2002  Windows SharePoint Services v2  SharePoint Portal Server 2003 using the SPARK connector for Microsoft Content Management Server 2002  An environment that included the Microsoft Office Web Components 6

7. Determine Upgrade Approach  Three Possible Upgrade Approaches:  In-place  Database migration  Gradual  For Shared Services 7

8. In-Place Upgrade  Description  Original sites are upgraded in-place  Cannot view the previous versions of the sites after upgrade  Content and configuration databases are changed at one time  Sites are unavailable during upgrade  Outage window is the full time it takes to upgrade the entire server or server farm  Good for  Single server farm  Minimal customizations 8

9. In-Place Upgrade  Pros  Easiest approach  Sites retain original URLs  Upgrades existing databases on current hardware  Cons  Offline when running  Not a reversible process 9

10. Database Migration  Description  Need to install new version on a separate farm or separate hardware  Manually migrate databases (except config. database) to new environment  Attach the databases to the new farm  Upgrade process runs and upgrades the data in place  Good for  Moving to new hardware/architecture  Required for WSS v2 scalabable hosting mode or AD service account creation mode 10

11. Database Migration  Pros  Good for new farm/hardware install  SPS 2003 environment untouched  Cons  Very complex process  Many manual steps  Higher risk of error  Additional steps to retain original URLs for sites  Search scopes must be recreated and settings reapplied  Requires new server farm 11

12. Gradual Upgrade  Description  Process copies data from original database to new database before upgrading the data  Original data is maintained in the original database until explicitly deleted  Upgraded sites can be easily rolled back to the previous version, if necessary.  Good for  Medium or large server farms  Sites where minimizing downtime is critical  Sites with a lot of customizations 12

13. Gradual Upgrade  Site Availability  Most sites are available during the upgrade  Only site collections currently being upgraded are offline  Site URLs  Original URLs point to the upgraded version of the sites  Users can continue to use the same URLs they used before the upgrade 13

14. Gradual Upgrade  Pros  Can move site collections one at a time  More granular approach  Sites retain original URLs  Can revert to original site  Uses existing hardware  Cons  More complex and resource intensive  Must redirect URLs  Extra storage necessary 14

15. Gradual Upgrade for Shared Services  Same as Gradual Upgrade  Can upgrade parent and child portals individually  Two search crawls are active for 2003 and 2007 environments  Good for any size server farm 15

16. Gradual Upgrade Process 16

17. Gradual Upgrade – Step 1 17  Install Office SharePoint Server 2007 to the first front-end Web server in farm and choose Gradual Upgrade

18. Gradual Upgrade 18  Run the pre-upgrade scan tool  Customized Site Templates  The existence of orphaned objects  The existence of custom Web Parts Use the information gathered from the pre-upgrade scan tool to determine:  Whether to perform an in-place or gradual upgrade.  Whether to upgrade some or all site collections  Which sites may need to have customizations reapplied or redone

19. Gradual Upgrade 19  Contoso’s Pre-upgrade SharePoint Server 2003 Portal

20. Gradual Upgrade 20  Upgrade and Migration  Click on "Site content upgrade status"

21. Gradual Upgrade 21  Site Content Upgrade Status

22. Gradual Upgrade 22  Set Target Web Application

23. Gradual Upgrade 23  Set Target Web Application

24. Gradual Upgrade 24  Set Target Web Application

25. Gradual Upgrade 25  Set Target Web Application

26. Gradual Upgrade 26  Site Collection Upgrade

27. Gradual Upgrade 27  Sites Selected for Upgrade

28. Gradual Upgrade 28  Upgrade is Started and Running

29. Gradual Upgrade 29  Upgrade is Started and Running

30. Gradual Upgrade 30  Contoso’s Post-upgrade MOSS 2007 Portal

31. Gradual Upgrade Walk-Thru  Show Gradual Upgrade demo  Also discuss  Best Practices  Common Issues  Show final site upgraded 31

32. How is Search Affected  Most search settings are upgraded, with the following exceptions:  Index files are not upgraded  Scopes are not upgraded  Search alerts are not upgraded  Any installed filters, word breakers, and thesaurus files are not upgraded  SPS 2003 search settings are stored in the registry  Database upgrade does not migrate these settings 32

33. Upgrade Best Practices  Back up your data  Back up again after initial migration goes live  Try it on a test farm first  Will help to set expectations  Run Pre-Scan Tool  Find custom sites or unghosted pages  Located in the …12\bin folder 33

34. Upgrade Best Practices  Plan for capacity  Database needs will triple with gradual upgrade  Database migration requires separate db  Do not change V2 sites after upgrade  Lock sites down  Keep for refernce purpsoses  Estimate how long upgrade will take  Communicate  Educate 34

35. Three Types of Customizations  What types of customizations have you made? 1. Sites that are ghosted (uncustomized) 2. Customized to add functionality now available in v3  Breadcrumbs, Custom Navigation 3. More than light customization  Major look and feel changes  Custom site definitions or templates  Recommendations 35

36. Issues to be Concerned About  Default content access for acount passwords  Local Server and Farm Admins can not browse the sites  Branding customizations are lost  Themes are lost  Customizations retained by stay in FrontPage  Site Definition issues  Custom Event Handlers don't work  Can't revert custom page to a template 36

37. SharePoint Issues  Upon migration of any customized sites the pages look like V2 pages and correcting them depends on how they were customized  FrontPage – must be done manually (rebuild everything for each page)  Site Definitions – must write a new update site definition to map to V3 (basically writing xml code) 37

38. A Different Approach  Unique Opportunity to rethink SharePoint architecture  Create new install of SharePoint  Run sites in parallel  Create new site templates  Utilize 2007 functionality  Migrate data manually  Create all new sites in 2007  Good for  Small installation base  Sites needing major enhancements 38

39. A Different Approach  Pros  Maximum utilization of new technology  Ability to learn from mistakes in the past  Greatest long-term benefits  Cons  Very labor intensive  Many manual steps  More time consuming  More expensive 39

40. CorasWorks Design Migrator  32 bit application can be run from the server or a client through web services  Run tool after Microsoft has completed the migration to V3  Automates the process of rebuilding V2 pages using V3 Master Pages and resulting in:  V3 features exposed properly  Sites are cleaned up, no old pages in the sites  Works on any page that was edited in v2 by FrontPage (unghosted pages)  Can be used to modify the Master Pages and the Page Layout of sites at any time, not just during migration 40

41. The V2 Page Layout (notice the zones) 41

42. Page 42 Pages After Migration – v2 Pages 42

43. Design Migrator - Settings  Log in and point to the sites to migrate 43

44. Design Migrator – Sites & Files  Select the pages and the template to use in the migration 44

45. Design Migrator - Migration  Run the migration from the template to the existing site 45

46. Design Migrator – Revert/Undo  Undo changes if you do not like the layout or if there are any issues 46

47. V3 Page Look and Feel 47

48. Design Migrator Corrects This Problem  The Design Migrator corrects this problem  It can be pointed to a collection of sites and the pages are:  Stored away in case you want to undo the changes  Collect all of the web parts on the page  Map them to the new zones on the new page layout  Create a new page and add the web parts to it  Currently in Beta until mid-January 48

49. Further Information  Determine how to handle customizations  Site Definitions  Uprgade custom Web Part packages  New Terminology 49

50. Questions / Contact  Questions?  Contact:  Malcolm Eaton  malcolm@captare.com malcolm@captare.com  312-953-5072  Coskun Cavusoglu  coskun@captare.com coskun@captare.com  (847) 445-6307  Jamie Story  jamie@captare.com jamie@captare.com  312-884-7638  info@captare.com info@captare.com 50