Thank you for the compliments - a lot of work has gone into these forums, and I'm very happy that people are finding them useful. And don't worry - every implementation I've been on still involves a lot of yelling back and forth!
I'd update your migration process as follows:
Prior to migration weekend:
Weekend of migration:
- 4.0 to 4.5
- Apply latest v4.5 SR
- 4.5 to 5.0a
- 5.0a to 5.0b
- Apply latest v5.0 SR
If you intend to move to OTM v5.5, then you'd add the following steps:
- 5.0b to 5.5
- Apply latest v5.5 CU
The biggest issue you're likely to hit is around migration windows. The clients we're working with who are upgrading from v4.0 are having a very difficult time managing - since they need to complete everything within one weekend.
Also - it goes without saying, but if you're able to run through 2-3 test migrations prior to the production migrations, all of the kinks will be worked out and you'll have a very accurate idea of the timelines involved.
Thanks!
--Chris