I have a SharePoint 2013 farm (multiple servers that connects to a sql cluster). The entire farm needs to move to a different AD domain. The SharePoint servers, the SQL cluster, the service accounts, and the users accounts. The old domain is being shut off, so everything needs to move. There is an article on support.microsoft.com that shows that moving the sql cluster is not supported.

I see forum posts saying that moving SP is not supported either, but can't find mention of this from official sources. I'm assuming I need to treat this like a migration and backup the content and service databases and restore them to a new farm that's been created in the new domain, but does anyone know of an official source of this info?

2 Answers 2


You cant move SharePoint farm to new domain, Reason, their are hard-coded references in the config DB related to services, web application, servers etc. For single server it is ok but for multiple server farm, Big no. You have to create a new config db using the new domain servers.

So best way is(which you already mentioned) migrate.

  • build a new farm with new SQL cluster, new service accounts
  • create new service Applications( some you can use exisitng DBs)
  • create new web applications
  • deploy all the custom solutions and custom configuration(if any)
  • now mount the database to respected web application.
  • migrate the user from old domain to new doamin.

also check this and this one, reply from MSFT


Don't migrate Sharepoint to another domain, I don't think it is not supported It is simply painful. Cleaner way is to rebuild the farm in new domain and do SP content database detach\attach procedure (as in DR or Upgrade scenario). In the past for domain move I was trying to use this blog: http://aurramu.blogspot.com.es/2011/06/move-sharepoint-from-domain-to-another.html but with mixed results - if you farm is simple (no enterprise services) then you will be fine, but the more complex set up (Excel, PowerPivots etc) you will most probably end up rebuilding those services anyway, so I prefer a clean build and then move content.

  • Thanks, that's what I was thinking as well. I was hoping to find some official guidance from MS, as I'm anticipating the looks from IT who were planning on changing the domain and rebooting.
    – Mike2500
    Feb 25, 2016 at 15:29

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.