Thanks for posting this!
We were on R16 and were looking into a lead time of 18 months by the upgrade team, so we decided to do it ourselves as well. So early February we upgraded from R16 to R32 which we have been running since. In light of the relatively low effort and high initial success we have decided to upgrade to latest revision every 6 months going forward.
I have a cookbook of our upgrade process, which is different from yours and I will happily share if anyone is interested. For instance, we didn't let the upgrade tool do the package import, but did that step using the import tool, since we needed some adjustments to the packages. We worked with a highly skilled developer from Aras Denmark on this.
My top tip for upgrading
Spin up a few instances as step 0 and configure them exactly as your production instance. Then if something goes wrong, you can focus on locating the error, and not worry about bringing your (semi) upgraded instance back to working order. I think I broke 3 instances before having all the scripts in order for the upgrade
Hello carstenw ,
Thank you for sharing your experience. I am definitely interested in reading your cookbook so I can improve ours. I will send you a DM!
Very useful tip you shared, it is must be in the cookbook. I went through the exact same struggle but did not have the server capacity available at that moment to add another instance.
