I have just built a MOSS 2007 server farm and would like to import some of my existing WSS 2.0 SP2 sites. My WSS 2.0 STS site is a standalone server with a WMSDE database. I need to leave the WSS 2.0 environment as it is currently configured, so upgrading to WSS 3.0 is not an option. Does anyone have experience or recommendations on how best to accomplish the site migration? thanks

Yes, Backup the databases for the sites you want to upgrade. Restore these backups as new databases on the SQL server in your WSS 3.0 farm. Create web applications in WSS 3.0 for the sites that you are going to upgrade.Remove the databases that are created with these web applications through WSS 3.0 central configuration. Now attach the WSS 2.0 databases you just restored to SQL using stsadm -o addcontentdb to the web applications you created in WSS 3.0 for the migrated sites. This is done through the command prompt.To do this navigatec:\program files\common files\Microsoft shared\web server extensions\12\bin andtype this commandfilling in the appropriate information. stsadm.exe -o addcontentdb -url http://<server>:<port> -databasename <WSS v2.0 content database> -databaseserver <DB Server name> for example stsadm.exe -o addcontentdb -url http://MyServer:80 -databasename WSS_V2_ContentDB -databaseserver Sample This will do anin place upgrade of the database. Note: If youSQL box has instances on ityou will need to specify the instance the database is in for example <SQL Server Name>\<SQLInstanceName> in the <DBServer name> spaceabove. Hope this helps you get started.

I definitely agree with that. Worked well for our WSS2.0. sites (about 100 sites in a dozend content dbs on 5 virtual servers). One thing that needs to be done before backup is to run prescan.exe from the WSS3.0 bin directory (12 hive). This tool scans the database and sets a bit that it is ready for upgrade. That doesn't affect the operation of the database for WSS2.0Be careful with document libraries that have content approval turned on. We had some difficulties with that. RegardsRen

Hey, I am going to try same steps as you described. In my scenario, Ialready have sites on SharePoint Portal 2007, If I attach content database from wss2.0 to wss3.0 whats going to happen to the exisiting sites on wss3.0. If you don't mind , can you send me steps for above procedure? Thanks SAURABH

The existing sites are not affected by the new content db. They are in their own DBs and can be accessed normally during the migration process. Despite that, I would recommend to do the migration not during production hours.The steps are the same no matter how many sites you already have on 2007.RegardsRen

When you look at the content database in central admin does it have sites listed? If not, I would try deleting the content db you just added through addcontentdb and retrying the process. If there are sites shown in the content database through central admin, after you try to access the site look at the event viewer of the server, this might give you some hints as to what is going on. Make sure you keep track of the exact time you make the attempts.

hi - what are the next steps after stsadm.exe -o addcontentdb -url http://<server>:<port> -databasename <WSS v2.0 content database> -databaseserver <DB Server name> i have done that but i don't know how to go back and see my sites. thanks

here is what you will have to do and i have tried at my end too.ususall to Migrate from WSS 2.0 to MOSS, it says that we need to bring the Database in WSS 3.0 and then to Moss.i would like to propose the following steps.1.Take a backup of your sites beofre the Prescan is Run.2. Run the prescan tool on the 2.0 environment which you need to download from http://www.microsoft.com/downloads/details.aspx?FamilyID=e8a00b1f-6f45-42cd-8e56-e62c20feb2f1&displaylang=en3. check the Bitflag value in teh SQL sites table if it has been upgraded to 262144 which means teh database is good to move to teh next environment.4. Move the Database to your new Server.5. Create a new Web Allpication with a Blank Template which will create a blank Database.6. Remo the Blank Database and Add the Upgraded Database to the site using the stsadn -o addcontentdb7. Do an IISRESET and you should be able to browse the site perfectly.

when you say wss 3.0 farm, do you mean moss 2007 or is it different environment than MOSS 2007..net Architect