Sharepoint Migration from one domain to another domain

My suggestion:

1)  Create new SP environment.
2)  Create users in new domain with same name as old domain
3)  Backup and restore farm from old domain to new.
4)  Run stsadm -migrateuser

There are a number of potential problems that could crop up, depending on how integrated your site is with your current domain.  You'll probably just have to knock them out one at a time.

Good luck.

Content wise you can backup and restore it on the new domain. You can keep the same name (as long as there is nothing conflicting).
You will have to update the user information that is used for running the timer process, search service, application pool

So even though the domain name and server name is different i can still use the same site name on the application?  Now with the restore, i'm assuming it's easier to do the restore db within sql 2005 (which is on the same box, and should be ok)?

Use the restore method (command line or GUI) that Sharepoint provides, since this will automatically create the databases, the site collections, etc.
Also backup and restore the 12 hive folder, if you have created any custom feature (workflows, webparts)

Here's a good article on Sharepoint backup and restore
Sharepoint-backup-restore.pdf

I agree, use the SP restore.  Also, don't forget the web.config settings if you've added any special settings for custom trust levels (grab the associated file, too), AJAX, trusted webparts, etc.  Pretty sure this is not part of the backup/restore procedure.

SO i have Sp installed on the new box, did a backup from the old SP site. It is on a diferent domain, so i'm not sure if there are other options i need to adjust first.  Below is the error message i'm getting

Object WSS_Content_56632621-09e5-4d46-907b-17626d5e3528 failed in event OnRestore. For more information, see the error log located in the backup directory. SqlException: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 28 - Server doesn't support requested protocol)

When restoring from the backup, did you update the path for the SQL database location? By default it uses the same path as the previous SP setup.

I'm assuming your takling about within the Restore page. Where it tells you where the APplication sites are, the web adress etc etc?

I've also been selecting "same configuration". Unless i should be configuring a New configuration

Yes, you should be using a "New Configuration" since this is a new setup (in a different domain).
Once you have chosen the new option, you'll be prompted to fill the user account information, the SQL database name, location and SP site name

OK so it populates the names of the sites after reading my backup file. I do enter in the new domain/admin and password. rename the sites to point to the new server. and i get this error now.

Object SharePoint - 80 failed in event OnRestore. For more information, see the error log located in the backup directory. ArgumentException: The IIS Web Site you have selected is in use by SharePoint. You must select another port or hostname.

In your "Central Admin" go to "Application Management" and click "Remove Sharepoint from IIS Website".
This will remove SP and you will have a clean slate to start with.
The reason for the error is that Sharepoint already created the website and app pool in IIS when the restore failed the first time.

Latest issue:

Object SharePoint - 80 failed in event OnRestore. For more information, see the error log located in the backup directory. SPDeletedConcurrencyException: The object SPWebApplication Name=SharePoint - 80 Parent=SPWebService has been deleted by another user since it was last fetched.

This was after i removed the sharepoint iis from website

in Central Admin, under "Application Management", click on "Delete Web Application" and choose the option to remove the content database and any IIS website

i did that as well. hense why i'm stumped at this point

So, now your SP solution does not have any content database and there is no application pool or IIS website, correct?

this is on the new side. it has those errors after creating the databases and IIS pointers. but that's as far as it gets. The only thing i can think of is that i disabled the sql and MOSS services on the OLD server, as i thought it would eliminate any conflict.