Skip to content
January 18, 2009 / red1s

WSS 2.0 to MOSS 2007 Migration process


Over the next week I’ll be handling quite a hefty migration process. I say hefty as there is a quite a lot of documentation around the whole procedure and how the old system works and the new system will be required to work.

I am currently putting together a technical migration plan document which will be used to complete the implementation.

So far I have found the following guidelines which I’ll look to focus my document around:

(Please note that my goal for posting the suggested process would be to hopefully gather comments and ideas around migration policies, procedures, strategies, etc..)

1) To gain the best possible understanding of the project which I am involved with; I have gone through the following documentation:

a. Test plan document

b.  functional requirement specification

c.  business requirement specification

d. (Current version which I’m required to update) migration plan

2) As far as I can understand the new solution would have to be specified the client according to the current environment/business solution which has been discussed by the business and formulated into the BRS and specified in more depth within the Business Requirement Specification

3) The old/current business solution; comprising WSS V2.0 document repository structured info and the custom developed CMS database based system; the new business solution would be required to consist of MOSS 2007 and the migrated data from WSS V2.

4) Expect to foresee the process and what would be encountered:

a. Expectations from the clients and the team gathered which is located in the BRS and technical spec

b. Requirements from the client and the team which is located in the BRS and technical spec

c. Issues/Problems which could be possibly encountered during the migration/upgrade procedure

5) Investigation of third party products to be potentially used:

a) Quest Software –

I. Notes made regarding software

b) Avepoint –

II. Notes made regarding software

c) Quest Software –

III. Notes made regarding software

6) Points picked up and for query which I still need to further/better investigate:

a. With regard to the current WSS V2.0 solution will the process be a migration or an upgrade?

b. Does the migration of information have to be moved into the newly planned implementation in other words will this be

I. an initial process

i. Methodologies used in this instances or recorded past experiences noted by this process

II. or gradual migration process?

i. Methodologies used in this instances or recorded past experiences noted by this process

III. What is the clients understanding regarding this?

IV. Has this been documented in the BRS or

c. Become aware of clients current problems and ensure that these issues can be alleviated with the new solution to be proposed

I. what are the current limitations of the current system and from this list what is the client currently experiencing

d. Is and if so where is the documentation which refers to the proposed hardware solution which THE CLIENT is looking to implement ?

e. Has the current environment been documented and if so where could I possibly find the documentation?

f. Does client have a communication plan in place?

I. For who?

II. Your content managers?

III. Users?

g. If gradual upgrade/migration does client have a new URL planned and setup?

I. Is the new hardware capable of optimally performing the objectives currently and into the future? (The hardware specs have gone way up from v2)

h. What type of farm do you have now?

I. Are you upgrading to the same farm type?

i. Are there any custom site definitions?

I. Have you created mapping files for them?

j. Are there any unghosted pages?

I. Are there any of what are going to be done with them?

k. Are there any 3rd party web parts?

I. Will they work with v3?

II. What about custom web parts that have been written?

7. Review and research Microsoft best practices methodologies and white papers regarding the migration process attached to this document in the form of supporting docuemtns:

a. White Paper: Upgrading Large Microsoft Office SharePoint Portal Server 2003 Intranet Portals to Microsoft Office SharePoint Server 2007

b. Look at experienced approaches to the migration process through the form of:

I. Blogs

8. A Possible migration solution process: (which may differ from yours but may be quite valuable to note ) Here are some of the points brought up

1. Analysis of current Portal which is done by looking at:

1.1.1. Infrastructure,

1.1.2. Database,

1.1.3. Sites,

1.1.4. Usage

2. Identification & Documentation of Customization in the Existing environment

2.1. Identification of Custom Site Definitions/Templates

2.2. Identifications of Web parts

2.3. Identifications of Hidden Elements/Features

2.4. Identification of Layouts and UI Customization

3. Web Parts (Customer Decision/Sign-off on)

3.1. Usage of New Out of the Box Web parts for SharePoint 2007

3.2. Using Existing Customized Web parts

3.3. Testing of Existing Web parts on SharePoint Environment and Identification of Re-Development Effort

4. Layouts and UI

4.1. Identification and Customization of CSS Based on SharePoint 2007

4.2. Master Page Customization for Application, Site and Content Pages

5. Hidden Elements

5.1. Identification and Development of Utilities (used during provisioning)

6. Creating Local Environment of Portal

6.1. Backup old SharePoint

6.2. Restore old SharePoint to new environment

6.3. Deploy Custom Web parts and other bits

6.4. Run prescan.exe with information of Custom site definitions

6.4.1. The can be used to gain greater insight into the current environment:

Understanding PRESCAN.EXE in MOSS 2007

Prior to upgrading to Microsoft Office SharePoint Server 2007/Windows SharePoint Services 3.0 one of the prerequisites some of you may have already noticed is running PRESCAN.EXE from the installation directory.  This post will hopefully provide some insight into PRESCAN.EXE as well as best practices on when it should be run.

PRESCAN.EXE has two primary purposes:

  1. It parses and saves List definitions with the associated Lists.  SharePoint Portal Server 2003 Service Pack 2 already incorporates this feature whenever a list is modified; however, this process should be completed for all Lists, so prescan calls the SharePoint Portal Server 2003 Service Pack 2 method to persist that data.
  2. PRESCAN.EXE will report on common issues that will result in a failed upgrade; therefore, running PRESCAN.EXE, addressing reported issues, and resolving those issues, and re-running PRESCAN.EXE to verify those fixes is a best practice when planning a Microsoft Office SharePoint Server 2007/Windows SharePoint Services 3.0 upgrade.  The most commonly detected issues are:

· Database Orphans This is a class of issue where an object exists, but the pointer with the parent object is broken and/or corrupt.   Classic examples include situations where a site exists in the content database; however, does not exist in the configuration database and a web that points to a site collection that no longer exists. 

· Missing Site Definitions This issue is rare at best ad exists when a site collection has been removed/deleted – sites under this classification will not be upgraded and in addition those sites will not render in SharePoint Portal Server 2003/Windows SharePoint Services 2.0.

Typically these issues will manifest as a result of failed STSADM backup and restore sequences, but also can client restore at the SQL level.

Depending on the nature and growth of your environment, PRESCAN.EXE is best run one (1) week prior to the production upgrade allowing time to address issues uncovered, and again prior to the upgrade itself to ensure that those previous issues have been resolved in addition to identifying new issues, if any.

6.5. Clear any prescan errors if you get

6.6. Installation of MOSS 2007 as Gradual Upgrade

6.7. Run SharePoint 2007 Configuration Wizard to install SharePoint 2007 side by side

7. Development of Custom Site Definition/Templates

7.1. Identification of Custom Site Definition/Template

7.2. Matching Existing Site Definitions/Templates with SharePoint Server 2007 Site Templates

7.3. Development of Site Definition in SharePoint Server 2007 Technology

7.4. Testing Site Definition in Independent new Environment

7.5. Development of Upgrade Definition file for all site definitions

8. Testing at Local Platform

8.1. Copy the new Site Definitions on upgrade ready Environment

8.2. Copy the Upgrade Definition file for the site definition

8.3. Copy the Master pages, CSS and layout files.

8.4. Start the migration process

8.5. Record and Fix Issues Iteratively using logs files in 12\logs folder

9. Repeat step 8 on production

10. Finalize Upgrade

11. Uninstall SharePoint portal Server 2003 (Stop SharePoint Portal Server Search Service first)

12. Delete Portal Configuration and Content Databases

13. Configure MOSS Search and other services etc.

9. Once the upgrade/migration has been done how will the overall effect be on the business:

a. How will your business processes be affected by this

b. How will your users be affected

Advertisements

2 Comments

Leave a Comment
  1. Ilia / Jan 19 2009 6:18 pm

    Hi Ridwan,I am a Product Manager at Quest SharePoint group, although not for migration products. Just came across your blogpost and thought you might want to take a look at a whitepaper my fellow PM recently published. It kinda addresses some points that you are not clear about: we saw the same lack of higher level documentation that you mention, guidelines that would help decide on the migration strategies. And so we tried to compare different native approaches and moving content with a 3rd party product.Here\’s the link to the whitepaper: http://www.quest.com/documents/landing.aspx?id=8550&technology=&prod=347&prodfamily=&loc.Hope you find it helpful! If you have any questions or feedback on this, please drop me a line at ilia <at> sharepoint-recovery.com, and I will relay your feedback!Cheers,Iliahttp://blog.sharepoint-recovery.com

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: