When attempting to migrate groups they do not appear on the target. Errors may not appear in the logs.
A conflicting profile may have been created such that SQL interference occurs.
In one instance it has been observed whereby the group that was common to both profiles may have caused interference. When the original profile was "RESET", the second profile was then allowed to complete the migration.
While this behavior is not fully documented or understood, it can be attempted to check if it allows migration to complete. However, this may be more complicated should the alternate profile you need to RESET is active and on a schedule. In this event you may need to consider any consequences that might exist for RESET of any profiles.
