However, we still need to define how formats would match. In the source database the fields victim name and date of birth are formatted differently for each type of victim, so it will be necessary to decide the format at the target database and make the transformations, if applicable. Similarly, the syntax rules at the target database should not be incompatible with the values at the source database (at least, without being transformed) as this could result in a loss of data. For instance, if the Victim ID field in the source database ranges from 5 to 9 digits and in the target database is limited to 7 digits, it is very likely to lose data. In this case, data profiling could help us to anticipate validation problems. All the questions and techniques mentioned above help to identify the challenges of the migration and, consequently, to allocate resources for it. Data profiling and data mapping are essential to recognize threats and select the best option to tackle them. Allocating time and resources On the basis of the analysis results and the project goals, it will be possible to estimate time and costs for the migration project. Although most of the steps and techniques presented in this document are useful for every project, regardless of its level of complexity, complex migrations might require additional human resources or specific tools to succeed. Furthermore, depending on how migration is designed, it is likely that data won’t be available during the process. It is recommendable to notify everyone who uses the data about the process stages and the availability of the data on each one. Security can be a goal itself for database migration, but it also constitutes a basic issue to consider when planning the project. In order to prevent data loss during manipulation, it is recommended to backup the database at the very beginning of the process. Additionally, the same access permissions that apply to the source database should be kept during the migration, paying special attention if third parties are involved in the process. As mentioned above, intermediate or testing files should be carefully wiped out to avoid data leaks. In general, an exhaustive planning considers all the relevant factors for the success of the project, which might be different for each organization and each migration purpose. Therefore, spending enough time at this stage is the best investment for the project’s success. 10