Migrating to a global field misses 40% of the data
Denis Paul
Rising Star 
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Where I come from: I have a multiselect field in a JPD project that I want to re-use in a new JPD project. So we created a global field with the same values and I started the migration.
What I did: Used the migration tool and assigned non-matching values
Where I'm at: The system only copied about 60% of the field values to the global field. The rest has empty global values where there is local data. I've had to edit the rest to match my local field.
Is that a known bug?
