Hello guys,I browsed, and searched the web on how to properly migrate the data from WSS 3.0 to our new MOSS 2007 server.I couldn't find straight steps.I found TechNet articles on how to migrate databases from WSS to MOSS stating I need to backup site, and content DBsHowever, I don't know if the scenario is harder but let me put it out here:We have this SQL Server that was initially used for WSS 3.0 (which has data and content), and it was also used by the first test MOSS we tried out. So, I need to backup the WSS stie and content only, but I cannot tell which DB belongs to the WSS. The naming doesn't help.If I am successful on this step, the next one will be to retore the backup on the new SQL server for the new MOSS instance, and attach it. I have one question here: Do I still need to backup the sites on the WSS and restore them in the new MOSS?I have the steps scrambled and not properly detailed or at least lined up.I am only interested to put the data from the WSS server onto the new MOSS server -both are different boxes- I can totally recreate the sites/site collections.I think I am close, but a hand will be helpful.Thanks for reading,...Alex

The first step is going to be to find out the name of the content database you want to backup. Go into Central Admin > Application Management > Content Databases. Make sure to choose the name of the correct web application and make note of the name of the content database. Is SQL on a different server as well? John SharePoint911: SharePoint Consulting http://www.sharepointblogs.com/rossonmoss

John,Thanks for the tip (so new in MOSS that I forget the basics).I found the option reading the comments in this post:http://geekswithblogs.net/RogueCoder/archive/2007/05/08/112343.aspxI am backing up the content DB, then I will restore it on the new SQL server, and try to attach it to the new MOSS as the article describes. Do you think I am good with these steps?PS. Yes, SQL is on a different server as well.Thanks for your prompt reply....Alex

John,I could successfully migrate the site collections from the old WSS 3.0 server onto the new MOSS 2007.However, I happen to miss (they did not migrate) the sites from the root path level on the old WSS over the new MOSS 2007.In other words, in the old site there was a site under the root level (eg. site1) which was not migrated properly.http://wss_server/site1I am not sure if that site was part of the content DB backup which was restored onto the new SQL server.If it was, why it did not migrate? Could you give me hand here?Plus, is it possible to back the site from the old WSS with the stsadm tool and attach it to the new MOSS 2007?Thanks in advance,...Alex

I'm not entirely following you. Are you saying you'd want to back things up and then restore them to the root of the web application in MOSS? Here's the high level of how I'd do it: 1) Backup the content db 2) Physically move the backup to the server and attach it to SQL 3) Create a new web application in MOSS but do not create a Site Collection. 4) Attach the content db to the new web application: stsadm.exe -o addcontentdb -url http://<server>:<port> -databasename <content database> -databaseserver <DB Server name> 5) Go into Central Admin > Application Management > Content Databases. Make sure to pick the new web application. You should see two content database -- one that has sites in it and one that doesnt. The one with sites should be migrated one. Click on the one with no sites and remove it leaving the migrated one. That should get you going but doesn't solve the issue of making sure everything is at the root. If you wanted to move your site collections under the root take a look at this blog post: http://msmvps.com/blogs/shane/archive/2006/11/14/consolidating-site-collections-after-upgrading-sharepoint.aspx Like I said at the beginning of this -- I'm not sure I am following you so if I'm completely off target I apologize in advance :-) John SharePoint911: SharePoint Consulting http://www.sharepointblogs.com/rossonmoss

John,Sorry if I sound blurry I actually did what you suggested; however, my problem is that I am missing a site under the root path from the old WSS 3.0. Let's say the old WSS server is wss_server, and the site (not site collection) I am missing is "development". eg. http://wss_server/developmentI can browse the "development" site on the old WSS, but the "development" site did not get migrated on the new MOSS.All site collections from the old WSS get migrated successfully but that site I mentioned above. I wonder why? Is it because it was created under the root path? If so, how can I solve this?Thanks,...Alex

Its possible development was a separate site collection with a separate content database or maybe there's something else weird going on. Either way, you could probably do aexport/import of the site and just manually move it over. On the downside, its going to reset all your created on and modified dates but it will get where you want it (hopefully). John SharePoint911: SharePoint Consulting http://www.sharepointblogs.com/rossonmoss

John,"Development" is not a site collection, it's merely a site under the root level on the same content database.Last night, I actually exported the site and move the BAK file over the new MOSS and import it from there. It did not import it due to web templates errors.I happen to have a "Development" site collection on the new MOSS, so I guess when attaching and migrating the DB backup over the new MOSS it did not override.Plus, the manage root path on the new MOSS is set to WILDCARD INCLUSION which it's worth to say is troublesome since it messes up the SITE COLLECTION ADMIN page for some reason.Anyways, I am going to delete the DEVELOPMENT site collection on the new MOSS and try to reattach the migrated DB and see if this time I get the migrated DEVELOPMENT sites.Thanks,...Alex

Let me know how it goes. It if it doesn't come over, then you might be right that there might be some errors holding things up. You might want to try reverting to site definition on that site to see if that helps anything if you've got some custom elements. John SharePoint911: SharePoint Consulting http://www.sharepointblogs.com/rossonmoss

John,Well, the previous plan didn't work out. I still can migrate only 3 out of 4 sites. (3 site collections, and 1 site under the root path from the old WSS) over the new MOSS.However, I can see that the migrated DB has the 4 sites defined (SITES table on the content DB), but somehow they all are not attached When I retried to import the DEVELOPMENT site alone over the new MOSS, it gives me this error:Could not find WebTemplate ABSENCE#75811 with LCID 1033.Any ideas at this point will be really helpful. I am willing to recreate all the site collections on the new MOSS since I have backed them up already Thanks,...Alex

I take it ABSENCE#75811 isa custom template? You'd just need to move that over from the old server to MOSS. John SharePoint911: SharePoint Consulting http://www.sharepointblogs.com/rossonmoss

John,Yes, it's the "Absence Request and Vacation Schedule Management" template missing in the MOSS 2007.However, this template seems to be available only for WSS 3.0 Since, I tried to install it with no sucess.Instead migrating the DB, attach it to the new MOSS. I ended up exporting site by site from the root path on the WSS, and export the site collections, and restore/import them from the new MOSS 2007.So far I am good, I let you know how it ended up.Thanks for following up,...Alex

The templates should work just fine if you install them in MOSS. If you download the template, there is some exe that you need to install first before installing the MS templates. I can't remember what its called, but it is mentioned in the README.txt for all of the templates. John SharePoint911: SharePoint Consulting http://www.sharepointblogs.com/rossonmoss

John,You are referring to the Application Template Core available here http://go.microsoft.com/?LinkId=5922037I tried to install it, but it didn't work. I haven't retried since but I will once I am done migrating.Thanks,...Alex

Hey John, Is there way to migrate the other way round. I want to migrate SharePoint sites from WSS to MOSS. What are the basic steps and requirements. Any help is appreciated. Thanks Bob

Sighs (because this is the third such post - not from you - replying to a Feb/Mar 200*8* thread) Bob - you are replying to a single guy who posted to this thread almost 18 months ago. The chance of him seeing this are small (although he is still around and active in the forums) Instead of resurrecting old threads, please post new ones with your own Title and problem description. Not only John Ross will see it but many others too. (Moderator) WSS FAQ sites: http://wssv2faq.mindsharp.com and http://wssv3faq.mindsharp.com Total list of WSS 3.0 / MOSS 2007 Books (including foreign language) http://wssv3faq.mindsharp.com/Lists/v3%20WSS%20FAQ/V%20Books.aspx

1. Identify each content database associated to each site collection 2. identify and evaluate all the wsp application files deployed to WSS 3. Run a site collection backups for all the content databases except central admin with backup.dat file extension(stsadm.exe backup site collection command) 4. Design a server farm infrastructure on MOSS 2007 with SP1(small,medium,large) 5. Install/Configure MOSS 2007 Infrastructure on the new Farm 6. Create new web Applications and content databases to the new Farm 7. Restore all content databases from WSS to the new one created(using the stsadm.exe site collection restore command) 8. Re-attach all applications and SP Designer designer workflow to each list(If Applicable) 9. Re-deploy VS applications(GAC)(if Applicable) Note: Configuration,Central Admin Content and SSP databases would be recreated again)

for your scenario the way is: take the backup of ur WSS content Database and attach it to new SQL server instance. create new site collection in ur MOSS instance and use the attached content DB (use content DB migration method) migrating site collections from WSS to MOSS is of no problem because every site in SharePoint is a WSS site but make sure when you migrate the WSS/MOSS versions should be same.