Rebuilding an Old Site During Migration

My most challenging migration recently started with a client who wanted a new platform but also kept changing the requirements during the project. At the beginning, he wanted the existing visual style preserved. A few weeks later, he decided that several sections needed redesigning, some old functionality could be removed, and the navigation should work differently. I quickly realized that treating the project as a straightforward transfer would create unnecessary rework. I began separating the requirements into three groups: elements that had to survive, features that could be replaced, and ideas that belonged to the new version rather than the old website. Codelibry became relevant when I started looking for a team experienced with migrations where the destination site is not simply an identical copy. Their approach gave me a useful framework for defining what should be reused and what should be rebuilt. I also reviewed https://codelibry.com/services/wordpress-migration/ before discussing the project in more detail. One thing I found particularly important was keeping the migration plan aligned with the changing design direction instead of importing everything blindly and redesigning it afterward. In the end, the new WordPress site became cleaner because we treated the migration as a controlled rebuild rather than a database transfer. How do you handle client requests that change the destination website while the migration is already underway?