So, in my current company, it was a banking-based project, so therein, we did not migrate the entire SOAP web service to the REST, but we picked a certain action method to migrate to REST because the complete SOAP web service had dependencies on more than 32 web applications, all those were Windows applications, so directly migrating the entire SOAP web service would require making changes in all the 32 web applications, which was not a correct approach to start to. So, we picked certain action methods, we checked the dependencies, we checked what all features might change once we migrate SOAP to REST, we connected with client, like, okay, if we migrate a certain action method or certain feature of SOAP web service to REST, this change, this impact it will give over the screen, how do we need to handle that, then after confirming, okay, what all changes extra we can make or what all changes we can make in order to overcome these impacts of migration, so after that, we first made the migration part, like SOAP web service to REST part, and then we made the dependent web application changes and then we presented to the client, okay, this is how it is working, and then we moved on migrating other action methods, but we did not migrate the entire web service at once.