concept migration in category microservice

This is an excerpt from Manning's book Microservices in Action.
This type of migration gives microservices a bad name. Few businesses have the luxury of a feature freeze for several months nor can they indulge a big-bang launch of a new architecture. Although the sample set is small, most successful microservice migrations that we’ve observed have been piecemeal, balancing architectural vision with business needs, priorities, and resource constraints. Although it’ll take longer and require more engineering effort, hopefully you’ll never recognize your team being mentioned in a cautionary tale!
But if other services call the orders service, you need to migrate those usages. Telling other teams to migrate doesn’t always work (competing priorities, release cycles, and risk). Instead, you need to either make sure your new service is compelling — make people want to invest effort in migration — or do that migration for them.