A little melodramatic? Slightly but not that much. I was so frustrated to find no other accounts of major problems with Migration Assistant that I had to write this. Consider it a cautionary tale... A first-gen Macbook Pro (1,1) I was repairing had HDD problems. I replaced the hard drive and was able to recover all files from the bad HDD. With the new HDD the laptop worked great, I did a clean install of 10.6 and ran all the updates. So far so good. My mistake was running the Migration Assistant - I chose to copy over one user's account and Applications. The result was plenty of kext errors, and Safari and Mail would crash upon launch (in any user account) (Looks like some system libraries that thsoe programs depend on are bad). Software Update says everything is fine and dandy, and multiple permission repairs didn't help. I suppose that because the data was recovered, some files may be corrupt and that stepped over the good installation. Still I was surprised that Migration Assitant offers to copy over Library settings and Applications without checking for those issues and while freely overwriting existing system files. After all this feature is often used to restore data after a major failure. Moral of the story? Migration Assistant has the potential to do this. It's just a hassle, I'm wiping and reinstalling the system again, and this time I'll opt for manual, partial data migration the safe way instead of trusting the Apple smiley face to do everything fantasticautomatically for me. Interestingly, I posted the above in Apple's user forums and it was removed by a moderator. Apparently the content was too extreme and outrageous.