Starting the Migration Process
To begin the migration process, deploy the migration objects to the servers that will be running the migration process. Follow these steps:
Extend the attributes for members by creating a Migration attribute in the Membership Directory.
Create at least one migration profile using the Migration ProfileBuilder tool. You will need to create one for each type of migration you plan on (batch and on-demand combined).
To deploy the objects you will need to copy the completed migration objects to each server and register the objects. For more information, see Register Migration Objects.
You will also need to make sure that the registry keys are set appropriately. For more information, see the Requirements section of MigrationLogObj Object.
If you plan on migrating users with on-demand migration as they log into your new site, you will want to install the migration objects on the Web servers and use the Login.asp file found in the <Drive:>\Program Files\Microsoft Commerce Server\SDK\Tools\MembershipMigration\Client directory. Use this file as a sample of how to trigger a migration when a user first visits your new Commerce Server site.
If you want to migrate all of your users together, install the migration objects on the server from which you will migrate all of the users. For best performance, choose a computer that is dedicated to the migration process. When you build the profile for migrating a range of users using the Migration ProfileBuilder tool, establish a filter depth, a search scope, and a search filter base in the Step 3 dialog box. Experimenting with different values before beginning the actual migration process allows you to optimize migration performance. Note that the distribution patterns of user account names in the Membership Directory plays an important role in the tuning process.
Always test the on-demand migration process before putting it into production.