I am currently testing on a data migration project,
The migration consists of migrating data from a existing source platform to a target platform of the same application.
The majority of the migration will be a straight move from source to target without any transformation. Apart from validating the field in the target database is the same value as the source, are there any other tests we need to do where the particular field is a straight move?
Y'know, I've pontificated on this subject a number of times. So, I'll leave the majority of my thoughts to be sought out - they're here, just click on my name and then look at my posts (I'm not going to repeat myself...much.)
Beyond the validation of the migration itself (if you start with 10 records on the source system, do you end up with 10 records on the target system...if not, why not), the biggest concern to me would be whether the data is usable or not. To me, it's great that you could migrate the data perfectly. But, if you can't use the data, you really haven't solved anything.
(It's not really limited to migrations. Usability of data has been and will always be one of the things that I will keep an eye on.)
"The single biggest problem in communication is the illusion that it has taken place."
-George Bernard Shaw, Irish playwright and Nobel Prize winner, 1856-1950