ADTM has some other limitations you need to be aware of. For example, ADMT can't translate permissions for SQL Server or for shared folders on network attached storage (NAS) appliances. This means for example that if you have a large number of NAS appliances deployed as work storage for different departments, you might want to consider using a more powerful tool like the Dell (formerly Quest) migration tools instead of using the rather basic functionality provided by ADMT.
ADMT also isn't really a product in the integrated sense of the term. It's actually just a collection of tools (a toolkit) that has a very basic user interface. Most of the time you're going to want to write scripts to leverage various ADMT functionality since doing things manually with the user interface will simply be too slow and cumbersome. This means you will need good expertise in writing scripts, and writing/testing/debugging scripts can take a lot of time which can slow down your migration quite a lot.
So basically if your migration project is fairly basic (few server applications, no NAS appliances, only a few thousand users, and lots of time to complete it) then ADMT is probably a good tool for you to use. It's also a great tool if your budget is very limited, because buying a third-party migration product like the one from Dell or paying an outside consultancy like MCS to perform your migration can both be very expensive options.
Anyways, we'll get back now to talking about ADMT in the next article in this series while we'll postpone the discussion about third-party migration products and MCS migration offerings until we reach the final article in this series.