Step by step migration from MOSS 2007 to Sharepoint 2010
Migration from MOSS 2007 to Sharepoint 2010
By Bhavin Sankhat
I have done migration for one of the my project. I hope this migration process will help someone.
Step1: Perform below task if required.
Upgrading SharePoint 2007 32 Bit to SharePoint 2007 64 Bit
By default, the SharePoint 2010 is available only in 64 bit mode. To be able to upgrade the SharePoint 2007 32 bit to SharePoint 2010, you will first need to upgrade your SharePoint 2007 32 bit to SharePoint 2007 64 bit if you are interested in migrating only some of the SharePoint sites. The stsadm command for taking a backup of a site stsadm –o backup –url <url of the SharePoint 2007 site> –filename <Path and file name of the backup file> you can also use –force switch to force the backup process in case of any issues.
Step 2: Create 64 Bit Moss Server
How to Install Office SharePoint Server 2007 SP1 on Windows Server 2008 R2
Well, you can’t do it out of the box, you need to slipstream the updates into the installer. I have read lots of instructions including the official ones and I don’t think they are clear at all, so I’ll give it a shot. These instructions are assuming you are installing on a 64-bit system, which most likely you are since R2 has no 32-bit version
What You Need
- Installation bits of Office SharePoint Server 2007 SP1 (these are your installation files). I have put these files in the following path: C:\Temp\RTM-Bits\Office SharePoint Server 2007 SP1
- Installation bits of Windows SharePoint Services 3.0 SP1 (these are your installation files). I have put these files in the following path: C:\Temp\RTM-Bits\Windows SharePoint Services 3.0 SP1
- Windows SharePoint Services 3.0 x64 with Service Pack 2 (place the Sharepoint.exe folder on C:\temp)
- The 2007 Microsoft Office Servers Service Pack 2 (SP2) (the 64-bit version, place the officeserver2007sp2-kb953334-x64-fullfile-en-us file.exe on C:\temp)
What needs to be done
- Extract the WSS files by typing: c:\temp\SharePoint.exe /extract:”C:\temp\WSS\Updates”
- Open the C:\temp\WSS\Updates folder, select all files and copy them
- Open the C:\Temp\RTM-Bits\Windows SharePoint Services 3.0 SP1\x64\Updates and paste all files (merge and replace)
- Extract the MOSS files by typing: c:\temp\officeserver2007sp2-kb953334-x64-fullfile-en-us.exe /passive /extract:”C:\temp\MOSS\Updates”
- Open the C:\temp\MOSS\Updates folder, select all files and copy them
- Open the C:\Temp\RTM-Bits\Office SharePoint Server 2007 SP1/x64\Updates and paste all files (merge and replace)
Step 3: Backup and Restore
Taking the version backup of a site collection:
stsadm.exe -o backup -url “http://localhost/” -filename “D:\Sharepoint Backups\My backup\backup.dat” -backupmethod full
Restoring the version backup of a site collection:
The web application should be present and running for restoring the site collection.
stsadm.exe -o restore -url “http://localhost/” -filename “D:\Sharepoint Backups\My Backup\backup.dat” -restoremethod overwrite
Your 64 Bit moss Version will be ready to migrate into Sharepoint 2010.
Step 4: Determining how to handle customizations
Although customizations for SharePoint come in many forms (Site templates , Site definition, Feature, Workflows and server controls, Event handler, Web Parts, Master pages and CSS files, etc.) I would like to focus now on the compiled code. There were many questions I have read on Forums and Blogs about “Do we have to recompile or rewrite the code for a migration to SharePoint 2010?”. I have found several answers and the good news is that in many cases neither rewriting the code nor even recompile it won’t be necessary. But I would like to display two excerpts of the Microsoft documentation that illustrates what you have to deal with:
Excerpt 1: Existing applications
You must recompile existing 32-bit applications and custom assemblies (for example, Web Parts and event receivers) to run on the 64-bit architecture because the 64-bit edition of SharePoint cannot load a 32-bit assembly. Before you recompile existing applications or custom assemblies, verify that they are compiled to run on both architectures. If this is the case, do not compile them for a single architecture. (In Microsoft Visual Studio this build option is Any CPU.)
If the existing applications are third-party applications, check with the third-party vendor regarding 64-bit versions and compatibility. In the case of custom contracted solutions for which you do not have the source, verify the solutions in a test 64-bit environment to ensure compatibility.
Excerpt 2 : Obsolete Classes and Namespaces
Because the changes to the API in the upgrades are backward compatible, you should not have to make any changes to your Windows SharePoint Services 3.0 or Office SharePoint Server 2007 custom solutions before you redeploy them in either SharePoint Foundation 2010 or SharePoint Server 2010. Some classes and namespaces are obsolete, but they will continue to work as expected. If you want to start upgrading your applications so that they use the most current classes and methods, recompile your code. The compiler warnings will tell you which elements of the object model are obsolete, and which newer alternatives you should use. Figure 3 shows an example compiler warning and the corresponding mouse-over warning in Visual Studio 2010.
Step 5: Redeploying Customizations and Solutions in SharePoint Foundation 2010 and SharePoint Server 2010
You can deploy a dll compiled for MOSS 2007 using the “Any CPU” or x64 build option on a SharePoint 2010 server and it will work using the 64-bit process, but if you want an optimized code you should recompile it with the new SharePoint 2010 object model. So in many case it won’t be necessary to recompile but it is recommended to do it to optimize your code and to learn the new SharePoint 2010 object model.
Looking to the table listing the different kinds of customizations and the migration impact on it, presents in the Microsoft documentation, I see 4 main important areas to review:
- Information architecture – sites provisioning
Site definition and site templates
Managed paths (inclusions/exclusions)
- Look and Feel – UI Experience
Master pages and CSS files
- Custom code
Workflows and server controls
Search provider or security trimmer
Step 6: Before migrate content DB to sharepoint server 2010 make sure below steps:
- SQL server version both end must be same (Update Version if required)
- Database backup version must be same. (Got to Version table under table tab and update appropriate version)
Step 7: Migrate the Content database of MOSS 2007 to Sharepoint 2010.
Attach the Content DB to SharePoint 2010 Application
The process of attaching the content DBs in the SharePoint 2010 Web Application should be done through STSADM tool. For Attaching the Content DB to a SharePoint 2010 Web application, you should perform the tasks in the following order:
- Restore the Content DBs to New SQL Server Instance
- Delete the existing content DB of the Web application
- Attach the Content DB of the Root Site collection
- Attach the Content DB of other Site / Site Collections if any
- perform an IISRESET
- Open the SharePoint 2010 Web Application
- Perform the Visual upgrade to get the SharePoint 2010 Look and Feel
Upgrade My Site
To upgrade the My Site to SharePoint 2010, you should perform the following activities
- Configure the My sites in SharePoint 2010
- Perform the Content DB attachment method as discussed earlier.