Use one agent deployment for 2003 – 2007/2010 migration where is possible

We do not recommend using of two agents deployment to perform 2003-2007/2010 migration. When you use two agents deployment source and target MSMQs are used to transfer data between agents. There can be connection issues between the queues that slow down a migration speed or even break the migration process. So, use two agents only if it is not possible to use one agent.

To avoid two agents usage you can Configure stored credentials for accessing a source farm and Install QMC locally to add a source farm.

The scenario with one agent deployment is the following:

1. Install MMSP to the target SharePoint server. During installation specify a MMSP service account.
2. Make sure the MMSP service account has all the required permissions for Source and Target Farms. Add missing permissions if needed.
   

   Note: If you cannot grant Permissions for the Source farm to the MMSP service account, use Stored Credentials.
   

3. Add a source SharePoint 2003 farm into MMSP.Note: If you cannot add the source farm, you may install QMC to source farm to perform discovery. Refer to Online help

Configuring stored credentials
“Stored User Names and Passwords” option allows a particular user to logon automatically to the specified server using stored credentials.
To configure stored credentials:

1.  Logon to MMSP host under the MMSP service account.
2. On Windows 2003: Open Control Panel | Stored User Name and Password 
   On Windows 2008: Open Control Panel | User Accounts | Manage your network passwords
3.  Add user account and password for the source server.

   Note: If an alias is used for server, the original name should also be added.

4.  Restart the ServiceMonitor and CustomPageMigrator services.

The required permissions for MMSP service account:
1. The db_owner role for Repository database
2. The Log On As Service right on the MMSP host (by default it is granted automatically, when a service starts under the account)
Permissions for Target Farm
3. Local Administrator on Target server
4. Farm Administrator on Target SharePoint farm
5. The db_owner role for target Content and Configuration databases
6. Full Control granted via the Policy for Web application (for all site collections within the web application) OR the Site Collection Administrator permissions in the Target site collections (per site collection)  
Permissions for Source Farm
7. Local Administrator on Source Server
8. db_datareader for Source content and configuration databases