Home » Microsoft Technologies

Site migration for MOSS 2007 to SP 2010


Can any one give me the steps to migrate my MOSS 2007 Sites Collection to 

Sp 2010 Environment. because i can't use .stp in SP 2010 so i am stuck with it 

 Please help me out.


Thanks Inadvance.



3 Answers Found


Answer 1

First see this link to decide which approach you want for migration


if you are using inplace migration  approach then go through this link


or else

Install and configure SharePoint 2010, on a new environment

-          Determine hardware and software requirements (SharePoint Server 2010) http://technet.microsoft.com/en-us/library/cc262485(office.14).aspx

-          Planning Logical architecture components http://technet.microsoft.com/en-us/library/cc263121(office.14).aspx

        -       deployment guide for Microsoft SharePoint Server 2010 http://technet.microsoft.com/en-us/library/cc262957(office.14).aspx

After installing and configuring your new SharePoint 2010,

Moving Content Database from SP 2007 to SP 2010

1) Find the content Database; These are listed under Central Admin->Application Management->Site Collection List

2) Backup the content database, You could alternatively detach it, and copy it. Just doing a backup in SQL Server Management studio is easier.

3) Restore content database to new server, Copy the BAK file to new server. Create an empty DB in Management Studio, restore from backup, you may need to change an option in the "options" tab of the restore dialog to get it to work. (Overwrite db).

4) Create Web App on SharePoint 2010

5) Remove Content Database from the new web app.

Now use STSADM to add restored DB to this web app

c:\program files\common files\microsoft shared\web server extentions\14\bin on new server is where you can find the STSADM.

run this command from there. Which will upgrade the content db to 2010?

stsadm -o addcontentdb -url http://yourwebapp:port -databasename yourcontentdb -databaseserver yoursqlserver

6) Run ISSRESET from command prompt

mark it as asnwer if it is helpfull for you


Answer 2

Hi Abhijeet,

Thanks for you response......

i moved my content DB from sp2007 to sp2010 without any issues,

but  the problem is my upgraded site  still looks like a sp2007 look and feel,

how to apply sp2010 look and feel (Ribbon) to this site.

Any help appreciated. 





Answer 3

Click on your sites , site  Action link, look at the bottom for the  Visual Upgrade link. This will allow you to upgrade your sites look and feel to 2010.




Presently our client have the MOSS 2007 Portal and they want to migrate those sites in to MOSS 2010. So, We need to show case something to that client. Please anyone have idea on the same, please let us know. It's very urgent.

Thanks in advance..

Pradeep Seella




I've a site built on MOSS 2007. I did an inplace-upgrade to migrate that site in the SP 2010. After some manual changes, the site is not using any MOSS 2007 custom layouts now.

When i export the site through stsadm command or through PowerShell, it exports fine with no error. But, when i import that site either through stsadm or PowerShell, it doesn't import the site. When i do import from stsadm, it throws hundreds of error while using PowerShell, it throws following error:

Import-SPWeb : Attempted to use an object that has ceased to exist. (Exception
from HRESULT: 0x80030102 (STG_E_REVERTED))
At line:1 char:13
+ Import-SPWeb <<<<  -Identity
http://server:1000/migrated -Path "c:\MySiteMigration.cmp"
    + CategoryInfo          : InvalidData: (Microsoft.Share...CmdletImportWeb:
   SPCmdletImportWeb) [Import-SPWeb], SPException
    + FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletImportWeb

Whereas, if i do a backup and restore then it doesn't create any problem and migrated the site successfully. But, this is not a good solution as it takes a whole farm backup. Second, it doesn't restore the site if i had done so before under same web application.

Any idea ?

Thanks & Regards,


I'm about to begin a migration from our current MOSS 2007 server which is attached to a SQL Server 2000 database (running on Windows 2000) to MOSS 2010 attached to a SQL 2008 R2 database running on Windows Server 2008 R2. Since there are so many moving parts, I like some comments on my general plan, below, and any pointers that might make this a less risky project.

We can be down for a day to do the migration.

Step one - move MOSS 2007 database to SQL Server 2008. If I understand correctly the steps are: Stop MOSS 2007, Stop the databases, copy the databases (and logs) to the new server, reconfigure MOSS 2007 to point to the new databases. Done. What are the problems going to be?  Step two - Install and configure MOSS 2010 and connect it to the existing databases - a database migration. For this, if I understand properly, I stop MOSS 2007, and attach MOSS 2010 to the existing databases. I haven't studied all the documentation yet, but that seems to be what's involved. Step three - perform an Interface migration to enable MOSS 2010 Interface features.

My operational plan is to do this as a pilot - perform step one but copy the databases to the new server but keeping MOSS 2007 alive while testing goes on. Then perform steps two and three. If everything works OK, either go live - assuming few if any significant changes to the MOSS 2007 sites - other than new documents in the libraries, we don't create too many sites - we can go live or, based upon learnings do it over with configuration adjustments.

One other fact - all the new servers will be running as VMs on Hyper-V. 

Thanks in advance for your help.



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  in  advance;  We have a new 2010 farm with infopath enabled and are having issues opening a browser document migrated from our moss environment.  The template that we use is web enabled.  We have no issues creating a new doc, saving it and opening that doc in a browser;  it is only docs that have been brought over from moss.  Any thoughts?

Will web parts written for SP2007 work in SP2010 or is it neccesary to re-write? The web parts concerned make extensive use of connection interfaces and tool parts. 



After restoring and attaching the old database i get this error, when visiting moss2010.
HTTP/1.1 200 OK Server: Microsoft-IIS/7.5 Date: Thu, 06 May 2010 11:16:14 GMT Connection: close

I will show how i tried to upgrade moss 2007 to 2010, hopefulle someone can telle me, what i did wrong.

First i upgraded moss 2007 to SP2. I ran the preupgradecheck and got these errors:

FeatureInfo... Failed
OSPrerequisite... Failed (since i am moving to a new server, i assume i can ignore this error).

I took a look at the log file which shows the following line:
Name = [Unknown], Feature id = [3ead887d-cd3f-48f6-874d-c5e4fe29dfe1], Reference count = [1], Scope = [Web], Status = [Missing]
I tried googling the ID, but didn't get any hits, so i ignored the error, and continued.....

Next i took a backup of the old WSS_content database and copied it to the new moss 2010 server.
Created a new empty database, and then restored the old one, checked Overwrite the existing database option. Named the database moss2007upgrade.
ran Test-SPContentDatabase -Name moss2007upgrade -WebApplication http://moss2010:10568 (not really sure what port to use, i have tried this with both deafult port 80, and the central administartion port, in this case 10568) and got the following error:
Test-SPContentDatabase : Cannot open database "moss2007upgrade" requested by the login. The login failed.
Login failed for user 'domain\Administrator'.

Then i went into central administration and deleted the old wss_content database, that was created, when i installed moss 2010.

I tried running the following command
stsadm -o addcontentdb -url http://moss2010:10568 -databasename moss2007upgrade  (again not sure what port to use, so i tried both 80 and 10568).
After 20 sec, i got "command completed successfully".

Tried to open http://moss2010 and got the error mentioned in the beginning of this post.

Any ideas? Let me know if you need more info.


Hi All,

I am kiran and working on some migration project.

I am stuck with some basic questions,


1. I have got couple of hudred WSS 3.0 sites

2. I have got couple of hundred MOSS 2007 Enterrprise sites

I need to migrate both the above to SharePoint Server 2010 platform.

My Question is,


1. Can I directly migrate WSS 3.0 sites to SharePoint 2010 env? Is there any need to step up to MOSS 2007 and then to SharePoint 2010? Becuase all documentations talk about migrating MOSS 2007 to SS 2010.

Your help is appreiciated.

Also can you link me to some sound help links please?







I've migrated a MOSS 2007 to SharePoint Server 2010. The migration itself ran quite successful without any problems but the log states me the SharePoint Foundation error 6622 and tells me that "The field type 'BusinessData' has a double definition" (german -> english translation).

Has anyone saw the same problem or /and has a solution for me.

Guy Jascht




We have performed a test migration from Moss 2007 to Sharepoint 2010.  When performing migration testing, there are several sites where the images are not viewable.  When you click the image, the following error is generated.  In several of the picture libraries, users created folders and they all have viewing problems.  I have also seen the issue where there were no folders involved, but there were multiple picture libraries on the same site.  Some of the libraries pictures display fine, while some do not.  

An unexpected error has occurred.


Troubleshoot issues with Microsoft SharePoint Foundation.

Correlation ID: 24f9291a-d4de-45ee-821c-9eedc6cddfa2

Date and Time: 1/21/2011 12:19:11 PM


We have performed a test migration from Moss 2007 to Sharepoint 2010.  When performing migration testing, there are several sites where the images are not viewable.  When you click the image, the following error is generated.  In several of the picture libraries, users created folders and they all have viewing problems.  I have also seen the issue where there were no folders involved, but there were multiple picture libraries on the same site.  Some of the libraries pictures display fine, while some do not.  

An unexpected error has occurred.


Troubleshoot issues with Microsoft SharePoint Foundation.

Correlation ID: 24f9291a-d4de-45ee-821c-9eedc6cddfa2

Date and Time: 1/21/2011 12:19:11 PM

Is there a list available of items that don't come over from 2007? I know things like customizations and maybe workflows are a problem. Are there any others?


I have my website in MOSS 2007 it's up & running.

Is it any way that I can save this site as template and then upload to SP 2010 anc create new site based on this?

How can I migrate all sites from SP 2007 to SP 2010.

Please, suggest



i have a subsite which has only custom workflows  and is built in Moss 2007 now i need to replicate the same site in SP 2010.

Can you suggest wat is best method to do so?

Can we save the site as a template and use the template on SP 2010 site?

Please through your thoughts


Thanks In Advance!


How do I import a moss 2007 workflow into sp 2010 for a list item

Hi everybody!

We are currently evaluating a migration from MOSS 2007 to SP 2010 and getting errors with picture libraries in content databases that are upgraded and imported into our SharePoint 2010 test environment. This is done by restoring a database backup from production to a different SQL server. Backup and restore is done with SQL Server Management Studio only.

if a picture library contains a folder with a name containing spaces, thumbnails within this folder are not shown (except in the "Details" variant of the standard view). A look at the page source reveals that the space is double encoded in the thumbnail's image-url (%20 gets %2520, encoding the percent sign) if we rename the folder to a name not containing spaces, everything displays ok. if we rename it back to a name containing spaces or create a new folder containing spaces, we get the same error. a newly created picture library will not show this double encoding behaviour and display as expected. when we save the standard view of an imported picture library (doesn't matter if we really changed it before saving) navigation into subfolders will stop working on the right pane (the list view webpart). Clicking on a folder will change the breadcrumb and put you into the subfolder on the tree navigation pane, but the content of the list view webpart will not show the content of this subfolder. It shows the rootfolder's content instead. Both errors apply to the "Thumbnails" and "Filmstrip" variant of the imported default view. The "Details" variant works as expected. It doesn't make any difference if the visual update has been applied or not.

I wonder if this a known problem and hope there's a known solution, as we are talking about 490 teamsites and thousands of folders containg blanks.

The new webfrontend is 2008 R2.

Regards, Ulrich

PS: Just noticed: If I create a new view within the picture library using the standard layout, everything is cool.



we need to move an application (only a site collection/portal site)  hosted in farm using  WSS 2.0(SharePoint Portal Server 2003 integrated with Project Server 2003) to a new farm where is installed WSS 3.0 and SharePoint Portal Server 2007.

We do not care at all about the part managed by Project Server 2003 . We are interested to obtain all lists, items and users information stored in the application (basically all the content part managed by MOSS 2003).

Which is the best strategy to get the job done ?

We have tried these steps to check if our strategy could work but it didn’t:

·          Create a new virtual server and portal site in the WSS 2.0 as test environment

·          Install and use prescan.exe on the portal site (it didn’t find any error)

·          Backup the portal site (using stsadm)

·          Move the backup to the new farm

·          Restore the backup (using stsadm)

We got a message error warning that the WSS used in the backup is different then the one installed in the farm target and the operation cant be completed. Did we miss something or it isn’t just possible use this procedure to migrate content by MOSS 2003 / WSS 2.0 to MOSS 2007 / WSS 3.0?

Browsing around, I found old topics talking about this operation  like the url linked below:

·          http://shaiju-sp.blogspot.com/2007/08/wss-20-to-wss-30-migration.html

where is suggested basically these steps:

1.     Backup the WSS 2.0 site

2.     Move the backup to a new server

3.     Install WSS 2.0 in the new server and restore the backup

4.     Install WSS 3.0 (upgrading the WSS 2.0)

5.     Execute the prescan tool on the site

6.     If errors are found then run psconfig –cmd upgrade –inplace b2b –wait –force

Now, before going to apply this procedure and ask a new environment at our clients, we would like be sure that this is the right thing to do to solve our problem..

I also read that there are around third party software that can do this operation automatically, any of this tool is freeware and efficient?

Else, anyone can confirm this or suggest another procedure to follow in case you need to move WSS 2.0/MOSS 2003 to a new environment using WSS 3.0/ MOSS 2007 ?

Any help will be really appreciated!




i had installed moss 2007 in windows server 2008 r2 with 64 bit machine.

now i wanna install sharepoint 2010. will it affect exisiting moss 2007?

please help me since sharepoint 2010 is exciting me and i wanna install it in my server.




I would like to copy/paste a site collection from MOSS 2007 to a brand new 2010, along with the lists/groups 

Is this possible?

Upgrading the MOSS-2007 to moss-2010 is something I wouldn't want.

Thank you


Ok, I just treid to do something that I didn't really think would work, but now that I've seen it fail, I get to ask the question. Is there a best practice on converting site templates built for MOSS 2007 to SharePoint 2010. We have several projects that used the Visual Studio Extensions (v1.3) and the SharePoint Solution Generator to build custom site templates and the .wsp packages. I can add and deploy the solution packages using the STSADM tool, but when I try to create a sub-site based on that template, I get an Object Not Set to an Oject Reference Error. In case anyone is wondering, it works fine in MOSS 2007. I have not tried Visual Studio 2010 yet (it's downloading in the background). I'm just wondering if anyone has run into this and what they did to fix it.




<< Previous      Next >>

Microsoft   |   Windows   |   Visual Studio   |   Sharepoint   |   Azure