Whenever we are approaching migrations in a system or a software project we usually have an ideal representation of the future aspect of our application in mind.

As soon as we start migrating the system, however, business necessities, technical challenges and changes in already-made decisions make our idealized future further away.

With this mind-provoking talk, I want to talk about a concept I call "semigration", explainable as: a chance to change some migration decisions, converting them into best practices and flows we can add to our daily job, taking opportunities whenever they arise to reduce migration complexity but achieving many of the expected results following the Pareto Principle.

I will provide an example case history of a monolith migrating to a micro-services architecture, stopping some months in the process and moving to a service-based approach, test-oriented development and CI/CD.