Migrating SharePoint ("Companyweb") site from SBS2011 to stand-alone server

We are planning to decommission an old SBS2011 server.  The SharePoint site is to be migrated to a new dedicated Server 2012 R2 virtual machine (presumably running SharePoint Foundation 2013).

What steps must we take in order to successfully migrate the site?

Both servers are fully patched with Windows updates. Thanks!
David HaycoxAsked:
Who is Participating?
Ajit SinghConnect With a Mentor Commented:
Before proceeding, back up your Source Server before you begin the migration process. Making a backup helps protect your data from accidental loss if an unrecoverable error occurs during migration.

This is probably the best documentation to follow for Migrate from Previous Versions to Windows Server 2012 R2 Essentials or Windows Server Essentials Experience: https://technet.microsoft.com/en-gb/library/dn408633.aspx

Regarding your request, maybe you could refer to the following article. It’s for SBS 2011, but the steps are similar with Windows Server 2012 Essentials. Move All SharePoint Foundation 2010 Databases for Windows SBS 2011 Standard to Another Server: http://technet.microsoft.com/en-us/library/gg616007.aspx

However, to upgrade from SharePoint 2010 Products to SharePoint 2013, you use the database-attach method to upgrade. In the database-attach method, you first create and configure a SharePoint 2013 farm. Then you copy the content and service application databases from the SharePoint 2010 Products farm, and then attach and upgrade the databases. This upgrades the data to the new version. Site owners can then upgrade individual site collections. For detailed steps: Step by Step guide to Migrate from SharePoint 2010 to SharePoint 2013

Also check this link: https://technet.microsoft.com/en-us/library/gg563792(v=ws.11).aspx

Before decommissioning your source server you need to run a gpupdate on all machines connecting to the domain.

Hope this helps!
David HaycoxAuthor Commented:
Was able to work it out with that info, thanks!  Here are the steps I took, for the record:

1.      Install SharePoint Foundation and SQL Server Management Studio on new server
2.      Windows updates and PSCONFIG, check event logs for errors
3.      Detach / backup databases and copy to new server (https://technet.microsoft.com/en-us/library/gg616007.aspx)
4.      Check settings on 2013 with “Get-SPWebApplication | fl” from SharePoint 2013 Management Shell
5.      Delete default web application and content database on 2013
6.      Create classic-mode web application in 2013 (need to use CLI as it is deprecated in the GUI): https://technet.microsoft.com/en-us/library/gg251985.aspx (“To create a classic-mode Web application in SharePoint 2013”)
a.      New-SPWebApplication -Name “SharePoint - 80” -ApplicationPool “SharePoint - 80” -AuthenticationMethod Kerberos –ApplicationPoolAccount NetworkService -Port 80 -URL http://servername
7.      Delete the content database just created (in SharePoint Central Admin and in SQL Management Studio)
8.      Attach / restore the content database from 2010 using SQL Management Studio
9.      Test the database with the following command: Test-SPContentDatabase –Name ShareWebDB –WebApplication http://servername
10.      Rectify or ignore any errors listed, as appropriate
11.      Attach the database with: Mount-SPContentDatabase –Name ShareWebDB –WebApplication http://servername
12.      Test website
13.      Add alternate site mapping (http://companyweb)
14.      Upgrade the site collection to the 2013 look (follow link at top of page)
15.      Apply new look
16.      Update internal DNS entry to point companyweb to the IP of new server

Here are some more resources I found useful:

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.