Evaluate partner solutions that support migration from SPS 2003 to MOSS 2007

jingmeili — Tue, 13 Mar 2007 16:29:00 GMT

A customer is looking to migrate their SPS 2003 content to MOSS 2007 and also restructure their sites during the migration process.

None of the standard upgrade approach from Microsoft would accomplish that and I've been evaluating some partner solutions that support content migration from WSS V2/SPS 2003 to WSS V3/MOSS 2007. The following 2 products have been evaluated and compared based on the trial download and information I received from the indivisual product sales/support/bussiness dev team.

	Tzunami Deployer 2.01	DocAve 4.1 Migrator
Technology	Client · .NET-based Windows application Server add-on: · Web service/OM on MOSS servers	DocAve server: · Database service · Network service · Tomcat service (java-based web server) DocAve media server: · Media service · Patch service DocAve client: · Communication service (Web service/OM) DocAve database: · Builtin – MySQL · Or existing SQL Server Browser access: · Hosted by Tomcat (http://server:8080/docave)
Remote access	Windows application running on remote desktops	Browser access supported with username/password
Installation components	Client on remote desktop Web service on MOSS servers	Server on any machine Client on SPS 2003 web-front end servers Media server also required.
Site level and item level migration	Yes	Yes
Modified time and Modified by	Preserved	Preserved
Create a new site in target on the fly	Yes (Collaboration Portal and Publishing Portal not available, need to exist already)	No (target sites need to exist already)* Updated in 2/1/2007 release. Now target sites can be created on the fly in 2007
Support migration from sites based on custom sitedef	Yes	Yes
User permissions required	Farm admin rights, etc (workaround - offline support for non-admin users and then commit to SharePoint by admin)	Special power user rights granted by using Control Panel in the software
Migration sources supported	· File Shares · SharePoint Portal Server 2001 · WSS V2/SPS 2003 · Exchange Public Folders (mail items, files, discussions, contacts, appointments, etc.) · Lotus Notes · EMC Documentum and eRoom · Hummingbird · OpenText Livelink · Plumtree · Hyperwave · Custom repositories	· SPS 2003 · Exchange Public folder
Touch databases	No	No
Migrate views	No (available in later version)	Yes
List types supported for migration	All list types	· List securities not preserved · Discussion board pending · Survey pending (Update: surveys are now supported 5/12/07)
Schedule migration task in UI	No	Yes
Pricing model	based on content size + maintenance fee	· base price + price per SPS 2003 user

Note: everything listed aboved is based on personal evaluations done before 3/13/2007 and information is subject to change. Please always refer to each product web site for the updated product information.

Tzunami Deployer: http://www.tzunami.com/products/?did=11

DocAve Migrator: http://www.avepoint.com/products/sharepoint-migration/

How to migrate SPS 2003 My Sites to MOSS 2007 using the same web app hosting the Portal site

jingmeili — Mon, 26 Feb 2007 23:04:00 GMT

During my customer's migration from SPS 2003 to MOSS 2007 testing environment, we encountered some challenges while migrating My Sites. With Bill's help, I was able to fix the My Sites in testing environment. During the actual production upgrade, My Sites were sucessfully migrated.

Here's a recap of the fix I did in the MOSS testing environment:

1. Migrate the portal content db first.

stsadm -o addcontentdb -url http://sharepoint07uat.corproot.com/ -databaseserver dbserver -databasename portal_SITE

2. Create a web named something like “my” using My Site Host template under the portal

stsadm -o createweb -url http://sharepoint07uat.corproot.com/my -sitetemplate SPSMSITEHOST -title "MySite Host"

3. Then restore SSP from the old PROF db:

stsadm -o restoressp -title Restored_SSP -url http://adminserver:11111 -ssplogin DOMAIN\sharepoint -mysiteurl http://sharepoint07uat.corproot.com/my -indexserver
indexservername -indexlocation "d:\index” -keepindex -sspdatabaseserver dbserver -sspdatabasename portal_PROF -ssppassword pwd

4. Execute iisreset

Then go into the SSP admin, check My Site settings, search settings, User profiles to make sure they all look good.

5. Now as a user, when I click on My Site in portal home page, I’m brought to http://sharepoint07uat.corproot.com/personal/userid and when I click on My Profile (or others click on my name) I’m brought to http://sharepoint07uat.corproot.com/my/person.aspx?accountname=DOMAIN\userid

6. To see the old SPS2003 MySite home page, just type http://sharepoint07uat.corproot.com/MySite . The Web Part error in this page is expected due to the retirement of My Alerts summary web part in MOSS 2007. Other web parts from your old MySite home page should show up here. This link can be pinned at either SSP or site level.

I'm also linking Bill's blog here for further reference:

http://blogs.technet.com/wbaer/archive/2007/02/19/co-hosting-team-and-personal-site-collections-within-an-individual-web-application.aspx

Jingmei Li's MSDN Blog : SharePoint Migration

Evaluate partner solutions that support migration from SPS 2003 to MOSS 2007

How to migrate SPS 2003 My Sites to MOSS 2007 using the same web app hosting the Portal site