Migrate SharePoint 2010 to 2013
SharePoint 2013 is Microsoft's new SharePoint version (at the time of this writing) and boasts some pretty cool features. In this post, we will migrate from a Windows Server 2008 with SharePoint 2010 to a Windows Server 2012 with SharePoint 2013. This migration involves 'cookie cutter' SharePoint sites: We are going to assume you have SharePoint running on SQL Express in a single server farm and that your site collection resides in the default WSS_Content database. If you have a more complex scenario, you can still use this guide as a framework, you will just need to make the necessary adjustments.
The Server 2008 with SharePoint 2010 will be referred to as the source server and the Server 2012 with SharePoint 2013 will be referred to as the target server. In summary, here are the steps we will perform:
- Set up a Windows Server 2012 server with SharePoint 2013 farm
- Copy the SharePoint 2010 Database to the target server
- Attach and Upgrade the content database
- Upgrade the Site Collection
Set up Server 2012 Server and a SharePoint 2013 Farm
Set up Server 2012 and install SharePoint 2013 on the target server and configure a SharePoint 2013 farm. When you create your Web application and site collection, make sure that you create the same type of site, the same port and the same authentication method as the source site.
Copy the SharePoint 2010 Database to the Target Server
Before proceeding, please make a back up of your Source Server's SharePoint application.
Next, open SharePoint Central Administration on the source server and navigate to Application Management > Manage Content Databases. Locate the database pertaining to your Web application.
From a command prompt, type net stop mssqlserver to stop the SQL Server service.
Locate the database in your file system. It should be in C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA
Copy both the content database as well as the log file to a removable disk. Once database and log files have been copied, open a command prompt and type net start mssql to restart the SQL Server service.
Detach the SharePoint Database from the Target Server
Since the database we are moving is named WSS_CONTENT (the Default) we will need to detach and rename the old database from the target server. Note: Make sure your target server is not a production server with a Web application utilizing the WSS_CONTENT database before detaching it. We will assume for this exercise that you have a newly installed SharePoint 2013 and have created a new Web application.
Log in to your target server's SharePoint application management and click Manage Content Databases.
Look under database name and click on the WSS_Content database link. Place a checkmark in Remove Content Database.
Acknowledge the warning after you have read it.
Click OK to remove the default content database (WSS_CONTENT). The content database should not up for the Web application.
From the target server, open SQL Management Studio 2012. If you don't have it, you can download it from here.
Open SQL Management Studio and Expand databases.
To detach the old database from SQL, right click on WSS_CONTENT and select Tasks > Detach
Place a checkmark in Drop and click OK to detach the database.
Navigate to C:\Program Files\Microsoft Office Servers\15.0\Data\MSSQL10_50.SHAREPOINT\MSSQL\DATA and rename WSS_CONTENT to WSS_CONTENT_OLD and rename WSS_CONTENT_log to WSS_CONTENT_log_OLD.
Attach and Upgrade the Content Database on to the Target Server
Copy the source database and log files to the following folder on the target server:
C:\Program Files\Microsoft Office Servers\15.0\Data\MSSQL10_50.SHAREPOINT\MSSQL\DATA
Open SQL Management Studio 2012. If you don't have it, you can download it from here.
Right click on databases and select attach.
Click on the add button, locate the database and click OK to attach it.
Note: If you are migrating from a different domain, expand the database and in Security > users grant DBOWNER privileges to a user account or administrative account in the new domain.
On the target server, open SharePoint 2013 Management Shell.
From the SharePoint 2013 management Shell, execute the following command:
Mount-SPContentDatabase -Name DatabaseName -WebApplication URL
This command will mount the database and upgrade it to SharePoint 2013.
Enter your site and verify that it's working. You may notice that it still looks like SharePoint 2012. That's because we have not yet upgraded the site collection.
Once you verify that the site is working, go to Central Administration > Application Management > Configure Alternate Access Mappings and change the default URL to the live URL of your Web site; alternatively, you can extend your Web site.
Once you make the port forwarding and/or DNS changes (if necessary), your newly migrated site will be live!
Upgrade the Site Collection
The final step is to upgrade the site collection. Before proceeding with the site collection upgrade, create a backup or a snapshot of the SharePoint 2013 server in case the fecal matter impacts the thermantidote.
From the Web site, click site actions > site settings. In the site collection administration menu, click on the site collection upgrade link.
Click on the upgrade this site collection button.
The upgrade process will begin.
When done, click on take me to the new site. Welcome to SharePoint 2013!!!