Issue Summary

When doing a C2C migration, the preflight check "Project already exist in Destination" triggers but when looking at the CSV report, the project key and name are different between the source and destination.

Even when the project from source and Destination are completely different and had never been on the same instance.

This is reproducible in Data Center: no

Steps to Reproduce

1. Have a project in the Destination with the same key as one of the source.
2. Change the key of the Destination
3. Create a migration plan to the destination and run the prechecks
4. Notice that the project already exists will trigger and the CSV file will show that pkey and project name a completely different

The issue seems to happen because the precheck validates for historical pkey of projects.

Expected Results

Should not trigger when the pkey is not the same at the moment of the migration, and if there is any issue because of the historical data, have it in a separate check, so as to not cause confusion.

Actual Results

It will fail, and give a CSV file where the source project and destination project are completely different, and changing the pkey or name on the destination doesn't resolve the validation.

Workaround

Change the project key in the source.