• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 571
  • Last Modified:

How do I migrate SharePoint 2010 Enterprise onto a new server?


I have a requirement to move my existing SharePoint 2010 Enterprise content (sites, lists, permissions, infopath forms etc) onto a new server (Windows Server 2008 R2 Enterprise). The new server will also be part of a new domain and a seperate SQL server already exists containing the existing SharePoint content databases. Would the process be as follows:

1. Install SharePoint 2010 Enterprise, Service Pack 1 & 2, Cumulative Update Aug 2013 onto the new server.
2. During the SharePoint installation, join the new installation to the existing content databases.
3. Create a new SharePoint web application and site collection (or will these be created during the above database join?)
4. Activate all required enterprise features within the SharePoint farm.
5. Redeploy all the InfoPath Forms and any custom code.
6. Move all services/service apps in Central Administration (Or will all services have to be created again?)
7. Remove roles from the old Server.
8. Remove old Server from the farm.

Does moving onto a new domain complicate matters?

Any advice appreciated.

  • 2
1 Solution
Is there a trust relationship between the domains that will stick around?  Are you also migrating Active Directory and the servers into the new domain?

If not, then you'll need to basically do a new install (new farm account) and connect your service and content databases from SQL.

Then you'll need to migrate the user accounts from old to new, unless your IT department is doing an ADMT with SidHistory enabled, which will 'copy' the identity from the old domain into the new domain.
Eugene ZCommented:
<Does moving onto a new domain complicate matters?>
it can be


<link to competing site removed - GaryC123>

1.Install SharePoint Server on the new server machine
2.Backup site collections from the old server, follow this guide: http://technet.microsoft.com/en-us/library/cc263441(v=office.12).aspx
3.Create Web Applications on the new server
4.Restore site collections from the prev. backups, follow this guide: http://technet.microsoft.com/en-us/library/cc262087(v=office.12).aspx
aspnet-scotlandAuthor Commented:

There is no trust relationship between the old and new domains. Active Directory has already been migrated into the new domain. So how do I connect my existing content databases into the new farm? SQL Management Studio/Backup/Detach? Once the content dbs are detach can I then use CA to attach them to the new farm?

Provided the target SharePoint farm is the same exact version, service pack and hotfix (or a later service pack and/or hotfix) as the source farm, then the cleanest way is to

a) create a new farm at the target
b) use SQL Backup and Restore to restore the SQL databases to the new SQL server
c) Create a new Web Application with a "temp" database
d) Use Central Admin or PowerShell to deattach the temp databases, and attach the 'real' content databases
e) Use Powershell's Move-SPUser to migrate the users from the old domain to the new domain http://technet.microsoft.com/en-us/library/ff607729.aspx

Don't forget to take the old farm either offline or mark the SQL database as read-only to prevent users from updating the old farm AFTER you've migrated!
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.

Join & Write a Comment

Featured Post

Build your data science skills into a career

Are you ready to take your data science career to the next step, or break into data science? With Springboard’s Data Science Career Track, you’ll master data science topics, have personalized career guidance, weekly calls with a data science expert, and a job guarantee.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now