During this talk, you will see the problems associated with having legacy code and trying to migrate to a new version of Java or the libraries, considering that changing the version is not just modifying a number into a file and nothing more; migrating to a new version sometimes implies rewriting many lines of code, introducing the risk that someone does something terrible. After introducing the problem, you will see how using OpenRewrite reduces most of the issues and the work of migrating from an old version of Java or some frameworks like Spring Boot with the last ones and showing the different templates of migration that exist to do the worst part for us. In the last part of the talk, you will learn how to update the dependencies using different technologies, such as version-maven to reduce the risk that your application uses too old dependencies. The idea is give to the audience the possibility to have a solution for this problems How can you update the legacy application to use the latest technologies? Which considerations need to be made to do the updating automatically? How can you keep updating your application to the latest library version without checking each website for the latest version of each dependency? How can you prevent any possible conflict of versions before deploying the application?