Upgrading from 5.0 to 2009

I have heard a lot of different things about upgrading to 2009. A lot of customers are unclear on 2009 and how the upgrade is going to work. I wanted to share my experience with an upgrade from 5.0 to 2009 classic. Two of weeks ago I had been scheduled to go onsite for a client to upgrade them from 5.0 to sp1, after arriving and explaining to them the changes to 2009 and that it was released already. I recommended to them to merge the modified objects and upgrade to 2009 directly. 2009 is simply bug fixes after 5.0 sp1 and additional minor code changes in relation to 3 tier environment. We tested their updated license and they could run the 2009 classic client and tested all the areas that they are running in 2009. They had modified about 100 existing objects. I divided the work among the 2 client developers that we 3 finished the work merging in one day. The client uses German Language pack which I exported from German DB and loaded into their database. I always Reset the modified flag and date time back to original date after loading language pack. I wish that was an option when loading language packs. The client tested for 2 days all their processes. They have a functional super user that knows all the areas and she tested all the areas, in additional we asked the users to test. After 2 day of thorough test, we upgraded the exe. Loaded the new xp_ndo.dll and loaded the objects. The client is using the classic 2009 exe so the users did not notice any changes and no training was required. Once MS start selling the granules, they will then install and use the new Role Tailored client. They have to make the form changes to pages and update their reports to use modified objects in RTC.