This week I had to move a MOSS Portal to a new farm in a different domain. This is not common and certainly can pose a challenge. The proven steps are documented below.
- backup content database(s)
- Create new web application
- Use CA to set status of new content database to disabled
- Restore old content database to new farm SQL Server
- Use CA to add newly attached database to the new web application
- Run stsadm.exe -o migrateuser for each user account (migrateuser is the trick used to migrating security to the new domain)
- Use CA to Import AD again using profile import
- Execute "C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN\stsadm.exe" -o sync -DeleteOldDatabases 0
Do not skip the last step. Regardless of what you read elsewhere you will need to execute the command. If this step is not completed your profile database and the user data stored in the content database will not be synchronize when the Synchronize Profiles MOSS timer job fires every hour.


