Basic steps for Moving a SharePoint site collection between domains

Before you start

Make sure SharePoint versions are the same on source and destination servers, service packs and patches.

Permissions

There are some basic permissions that need to be configured (if they have not already).

See Add-SPShellAdmin. If you are using Windows authentication to connect to SQL Server, the user account must also be a member the SQL Server dbcreator fixed server role on the SQL Server instance where the database will be created. If you are using SQL authentication to connect to SQL Server, the SQL authentication account that you specify when you create the content database must have dbcreator permission on the SQL Server instance where the database will be created.

Add-SPShellAdmin -UserName Domain\User Name

Migrate Data

Backup Site Collection on Farm A.

On the server farm that contains the original site collection open a SharePoint 2010 Management Shell.

In the power shell window type the following command:

Backup-SPSite –Identity http://FarmASiteCollection -Path TempPathAndFileName.bak -Force

Force will overwrite a previously backup file.

Create Content Database on Farm B.

Assuming the appropriate Web Application already exists then you just need to create a new content database.

On the server for farm B open a SharePoint 2010 Management Shell.

In the power shell window type the following command:

New-SPContentDatabase -Name ContentDbName -WebApplication WebApplicationName
 -DatabaseServer DBServerName

Restoring Site Collection on Farm B.

In the power shell window type the following command:

Restore-SPSite –Identity FarmBSiteCollection -Path TempPathAndFileName.bak
-DatabaseServer DBServerName -DatabaseName ContentDbName

Restore Access/Permissions

You need to add a user via command line because the restored site will deny all of your login attempts (unless your server is on the same domain as the original source server).

Using the central administration console, you will note that the site collection still references the original administrators which are now invalid on this new domain.

NOTE: you can view using following steps >> Central Administration >> Application Management >> Site Collection Administrators (on Farm B SharePoint central administration domain).

·         Now you need to change ownership of the site collection using following command.

Set-SPSite –Identity FarmBSiteCollection -OwnerAlias “domain/User”

·         Now if you refresh central admin console you will see the new administrator as an owner, you can change the secondary administrator at this point as well using same utility.

Set-SPSite –Identity FarmBSiteCollection - SecondaryOwnerAlias “domain/User”

·         Now reset the IIS and you can login the main site collection as an administrator.

·         Then you can optionally run this to clean up the old lingering logins explicitly

Move-SPUser –Identity olddomain\UserName  - NewAlias newdomain\UserName