Testing plays an important role in the context of software migration as it is used to validate and ensure functional equivalence as a key requirement. As developing new test cases of the migrated system is typically a costly and time-consuming activity, migrating existing test cases for the old system is thus an attractive alternative. Considering that migrated test cases are relied upon to validate an implemented system migration, it is clear that validating the corresponding test case migration is indeed crucial. The solution space involved in validating test case migration, however, is currently not well researched. In this paper, therefore, we analyze the application of mutation analysis as a validation technique for test case migration. Depending on what is mutated, we identify six scenarios which can be used as mutation patterns depending on the situation and the user’s requirements. For each scenario, we provide a discussion of implied assumptions, indications, and limitations in each case. We also present an initial evaluation of the identified mutation analysis scenarios performed in a real-world migration setting.