That web deployment tool is good!
Disclosure: MSFT employee, clearly biased!
The Web Deployment Tool can migrate sites and apps between servers, and has some really useful features for determining whether configuration has drifted between servers within a farm.
Generally, you -verb:sync content into a package of some sort, then you can -verb:sync or -verb:migrate that package to an IIS 6.0 or 7.0 target server. If you're just curious, you can -whatif the operation, which will identify all proposed changes between source and target servers.
In my experience, with IIS 6 servers, the key problem that develops over time is that the metabases drift between farm members (unless it was carefully planned and managed from the beginning), and that can lead to - let's call them interesting - farm behaviours. This tool can evaluate metabase differences, content differences, the works, with much less effort than trying to script IISCNFG.vbs to achieve the same result. The syntax is a little confronting at first, but the investment is worthwhile, IMHO.
CMS had a separate workflow and deployment engine, as I recall, so it might not have comparable features on the workflow front, but for pushing sites around between servers, and synchronizing farms (both content and settings), I've found WebDeploy is pretty good.