SharePoint - how do i migrate from sharepoint 2007 to sharepoint 2010

1. how do i migrate from sharepoint 2007 to sharepoint 2010 without using any third party tools
2. how to migrate sharepoint 2007 list to sharepoint 2010 list without loosing data. 

First of all, let’s understand the outline of what needed to be accomplished:

• Acquire another server
• Install SharePoint 2010
• Perform a “preupgradecheck” on the old server
• Install any prerequisites on the new server
• Migrate the Content DB
• Apply the new look and feel
• Apply Joel’s theme

Acquire Another Server

Why did we need another server?  There were 2 reasons: Because we wanted both the 2007 and 2010 site to show up simultaneously and because the old hardware was running on 32-bit architecture.  As you may remember – SharePoint 2010 requires a 64-bit OS to run.

Install SharePoint 2010

This part was simple enough and to be honest, was another reason why we needed a second server.  For this demo, we had already in stalled the bits for 2010 and we couldn’t make this site live before Monday as the NDA from Microsoft was still in place.

Perform an “stsadm –o preupgradecheck”

I can’t stress enough the importance of doing this on your 2007 SP2 (or later) site.  This goes through your current site and checks all dependencies to ensure you are ready to go.  Here is a screen-capture from Joel’s:

Install any Prerequisites on the Server

This means that any packages (WSP’s, Features…)  that are installed on the source server need to be installed on the target server.  In Joel’s case, this included the Community Kit for SharePoint.

Confession: I forget to do this the 1st time I attempted the migration and the upgrade on the content DB failed.  Good thing I had another copy of the source content DB (you should too!)

So off to codeplex I went and downloaded the install files.  It is certainly nice when a package comes with an INSTALL.BAT but guess what? Any and all of those install files out there have to updated if they drop any files in

c:\program files\common files\microsoft shared\web server extensions\12\*

Know why???  Because in SharePoint 2010 the install directory changes to:

c:\program files\common files\microsoft shared\web server extensions\14\*

After updating their install.bat, all worked well.

Migrate the Content DB

Part of this step does including creating a new site collection.  It doesn’t much matter what template you use, as you will be detaching and deleting it’s database.  Once you have it created, go into central admin and delete the content DB from the WEB app.

Now, when I made a copy of Joel’s production DB, I just made a SQL Backup of the content.  I could have copied the MDF and LDF files and moved them to the new server.  But being lazy and only wanting to move one file, I opted for the “backup” method.

So now over on the 2010 server I opened SQL Studio and performed a “restore” of Joel’s content db.  Note: you may need to either kill SQL connection or just restart the SQL service. 

Now that I had a copy of the Content DB on the new SQL server, it is was time to connect it to SharePoint 2010.  To do
this, you have to use the command line as the GUI interface can not handle the upgrade.  Open a CMD interface and navigate to the BIN directory:

c:\program files\common files\microsoft shared\web server extensions\14\bin

and perform the following:

stsadm –o addcontentdb –url enter your url –databasename enter your db name

For complete article follow this-

http://www.social-point.com/migrating-a-sharepoint-2007-blog-to-2010-part-1

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), http://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). http://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).
• http://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 http://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.

http://blogs.technet.com/b/nitinsha/archive/2010/07/27/migration-from-sharepoint-2007-to-sharepoint-2010.aspx

Microsoft released the SharePoint Server 2010 beta recently. Also Microsoft states that migration process from SharePoint 2007 to 2010 is fairly easy and straightforward, however as far as my knowledge goes migration process from SharePoint 2003 to 2007 is difficult and painful with several incompatible elements to be dealt with.

The SharePoint 2007 site presented in this blog is using Windows Server 2008 R2 64-bit (which is minimum requirement for SharePoint 2010) with SQL Server 2008 Express Edition 64-bit as underlying operating system and database.

First, let’s look at the SharePoint 2007 site we migrate. For this demonstration I created a simple MOSS 2007 Enterprise environment based on the Collaboration template, which contains some generic web parts we’ll test on SharePoint 2010, Document Center and Search Center. I setup and double checked the search, because I wonder if the migrated SharePoint would be able to use the search database crawled in the previous, 2007 version of SharePoint. Search is an important issue for migrating SharePoint installations with large amount of data where a full crawl of the content may take weeks.