Migrating to the cloud is a commitment. It’s a commitment of time, resources, and corporate energy. Perhaps you are migrating an on-premises application to the cloud. Or maybe you’re moving a monolithic application to service-oriented or microservice architecture. Migrations are not easy to pull off, and can involve long transitions. Because the benefit is not always immediately obvious—and, in fact, sometimes things get worse at the beginning—it’s tempting to want to quit the migration early. Who would ever want to do that? It seems crazy, but it happens. Moving from a monolith to a service architecture, but stopping soon after the migration has begun, leaves the application in worse shape than it was before starting the migration. So how do you avoid the temptation of halting a migration in its tracks? Well, the key to avoiding this cloud migration mistake is all about managing expectations and understanding the true return on investment. The Valley o