At the very core of microservices, lies the capability to work on a specific functionality in isolation from the rest of the system. This translates into all of the advantages discussed earlier, such as reduced module dependency, code reusability, easier code maintenance, and better deployment.
In my opinion, the same attributes, which were attained with the implementation of microservices, should be maintained during the process of implementation. Why should the whole process of moving monoliths to microservices be painful and not be as rewarding as using the microservices themselves? Just remember that the transition can't be done overnight and will require meticulous planning. Many capable solution architects have differed in their approaches when presenting their highly capable teams. The answer lies not just in the points already mentioned...