Thanks for the info. Both the new and the old drives are WD so I think I will try the WD Arconis utility first.
I was using that myself a few weeks back, and it is simply a slightly cut down, rebadged Acronis. What I would suggest you do if you have the time, is to run the WD diagnostics across the drive drive first. If there are any problems with the drive, these will hopefully show it up before you start to use it in anger. Hard Drive Sentinel also has some good surface tests, such as "write then read" tests
I had an issue with a WD drive where everything was installed and looked good for the first month, but as more data was added to the drive, it hit a bad spot that the drive could not remap. As it was a system drive, I'd see intermittent system lockups whenever this "bad but un-remapable" block was accessed. The system would wait while the drive went off to do it's remapping and the drive would never come back. It ended up being replaced, and the replacement has been perfect.
However, this just goes to show that as drive manufacturers chase ever larger capacity drives, they are all suffering from worse quality control. It's cheaper just to replace or refurb drives that fail than to spend the extra money making them all 99.9 percent perfect. So while the disk is blank and not being used, it might be worth spending a day letting it run surface tests to make sure it's not going to cause problems in the future.
Ideally, you put the new drive in, but still boot off the old one. This way you can run tests and diagnostics on the new drive without it being a system drive at the same time. Then when you are happy it passes the tests, you clone the old drive to the new one.