Cloud-to-cloud migration - don't create a new custom field with the suffix migrated when a custom field already exists

Currently, when performing a cloud-to-cloud migration the custom fields are created with a migration label even if the destination already has a custom field with the same name created.

it will be useful to reuse the existing fields to avoid seeing the migrated work on each project, or having to clean up the destination after the migration is done.