Here is a new case study that features a high profile migration project that used Notes Migrator for SharePoint (my product) and Quest's Web Parts for SharePoint together [link].  It is a great example of how using a good data migration tool as well as a rapid application development tool for rebuilding the non-standard user interfaces can reduce the cost of the overall migration project.

There is one other thing I really liked in this case study:  The customer cited “the ability to replay the migration scenarios as many times as needed to ensure good results” as one of the primary criteria for selecting a migration tool.  This is something that we designed the Notes Migrator for SharePoint migration console was designed for from the beginning, but the value of it is not always clear. 

Our tool give you the ability to effectively build a “migration plan” consisting of lots of lots of provisioning and migration jobs.  Generation of this "plan" may be largely automated based on class rules, but with plenty of room for dealing with the exceptions and one-off cases.  Then you can executing that plan in whatever size batches you want in a controlled and repeatable manner.  You can think of the plan as a script for your migration tool.  In some cases, an organization will build the plan (testing small pieces at a time) in a test environment and then "replay" it in a production environment.