It’s always a good idea to get QA personnel involved in any project as early on as possible, including data migrations. Even data migrations that may appear to be simple and straightforward conceptually can quickly become complicated as analysis is done of the source data and how it maps to the target system / database. Even the type of source database / system can have an impact on how the data migration itself is carried out. QA personnel should be involved in all aspects of the analysis and design of the data migration. QA can begin their test strategizing and developing detailed test cases during the analysis phase — and can continue to refine and finalize their test cases during the design phase. Involving QA early on helps immensely in improving the overall quality of each phase of the data migration project. QA helps identify problems as early on as possible before formal testing even begins.