Upgrade and Migration from Sharepoint 2007 To Sharepoint 2010

 

Migrate sharepoint 2007 to sharepoint 2010 using database attach method

Upgrade/Migrate SharePoint 2007 to SharePoint 2010 using content database attach method

When you upgrade from Microsoft Office SharePoint Server 2007 to Microsoft SharePoint Server 2010 by using the database attach approach, you upgrade only the content for your environment and not the configuration settings. Using a database attach upgrade is useful when you are changing hardware or want to reconfigure your server farm topology as part of the upgrade process.

Before you can upgrade the data, you must configure a new server or server farm by using SharePoint Server 2010. This article explains the elements you need to configure to create that new environment. For more information about the general process of upgrading by using the database attach upgrade approach,

To perform the steps in this article, you must have administrator rights on the local server computer. For more information

Before you begin to create the new environment for a database attach upgrade, review the following information about permissions, hardware requirements, and software requirements.

• Ensure that you have met all hardware and software requirements. You must have a 64-bit version of Windows Server 2008 or Windows Server 2008 R2. For server farms, you must also have a 64-bit version of SQL Server 2005 or SQL Server 2008. For more information about these requirements (such as specific updates that you must install), https://technet.microsoft.com/hi-in/library/cc262485(en-us).aspx .
• Ensure that you are prepared to set up the required accounts by using appropriate permissions. For detailed information, see Administrative and service accounts required for initial deployment (SharePoint Server 2010). https://technet.microsoft.com/hi-in/library/ee662513(en-us).aspx
• Run the pre-upgrade checker on your original environment. The pre-upgrade checker identifies potential upgrade issues in your environment so that you can address them before you upgrade. It can also help you identify settings that you need in your new environment. For more information, see Run the pre-upgrade checker (SharePoint Server 2010).
• https://technet.microsoft.com/hi-in/library/cc262231(en-us).aspx

It gives ypou adetailed report in the form of a html file and txt file which tells you about the warnings and erors if any which you ahve to take care before upgradadtion otherwise the upgrade may fail if all errors ae not resolved .

1. Install SharePoint Server 2010 on the server or servers.

2. Configure service applications.

3. Configure general farm settings.

4. Create and configure Web applications.

5. Reapply customizations.

.Then only use following article to upgrade your content databases by attaching the cointent databse to SQL server and then to web applications by using powershell or stsadm command i.e.

stsadm -o addcontentdb -url https://servername -databasename <wss_content> -databaseserver <sqlservername> -preserveolduserexperiece <true/false>

if you want to jkeep your old customizations , thenm selcet true fro preserverolduserexperience otherwise visual upgrade option after installation also allows you to preserver your customizations.

https://technet.microsoft.com/hi-in/library/cc263299(en-us).aspx

Presentation:
Lesson 2: Preparing to Upgrade to SharePoint 2010

Video:
WMV (204 MB)

Comments

• Anonymous
  October 14, 2010
  Thanks for giving this vital information. It will very helpful for those who are seeking problems in migration from 2007 to 2010. <a href="www.xavor.com/.../sharepoint2010migrationtool.aspx ">Free SharePoint 2010 Migrator tool</a>

• Anonymous
  June 20, 2013
  Hello, I get several errors when migating a content db: Database contains a site (Id = ., Url = .) that is not found in the site map. Consider detach and reattach the database. The orphaned sites could cause upgrade failures. Try detach and reattach the database which contains the orphaned sites. Restart upgrade if necessary. Database contains a site (Id = ., Url = .) whose url is already used by a different site, in database (Id = [.-.-.-.-.], name = [.]), in the same web application. Consider deleting one of the sites which have conflicting urls. The orphaned sites could cause upgrade failures. Try detach and reattach the database which contains the orphaned sites. Restart upgrade if necessary. One or more setup files are referenced in the database [.], but are not installed on the current farm. Please install any feature or solution which contains these files. Template MPS#0: SPSite Id=. could not be accessed due to exception. Skipping SPWeb Id=. for template upgrade. Exception: System.IO.FileNotFoundException: The site with the id . could not be found. Any help would be great!

• Anonymous
  December 16, 2013
  Thanks for the wonderful insight. You can use this visual guide to migrate from SharePoint 2007 to SharePoint 2010http://www.sharepointdiary.com/2011/09/migrate-from-moss-2007-to-sharepoint-2010.htmlTo migrate from SharePoint 2010 to SharePoint 2013: http://www.sharepointdiary.com/2013/09/migrate-from-sharepoint-2010-to-2013-step-by-step.html

• Anonymous
  February 16, 2015
  Thanks for this helpful information I agree with all points you have given to us. I will follow all of them.
  http://staygreenacademy.com">SharePoint Training Online

• Anonymous
  February 17, 2015
  Information was good, I like your post.
  Looking forward for more on this topic.
  http://khalil-kothia.com">SharePoint Freelancer