When copying an item that contains a self-lookup in one of it's past version and that lookup is also included in a circular dependency, this item might be different at destination.

This can also happens when you have a Document Library with no versions enabled and part of a circular dependency.

Due to a limitation, that item will now have the self-lookup on it's current version.

The item '{0}' has an older version that contains part of a circular dependency. That reference might be removed or contained in the latest version due to a limitation in the Sharepoint Azure import api.

The file '{0}' contains part of a circular dependency. That reference might be removed or contained in the latest version due to a limitation in the Sharepoint Azure import api.

When using Insane Mode, ShareGate Migrate sends all versions and items that complete a circular chain at the same time. Usually, the order in which we send those items doesn't matter. But due to a limitation on the import API that we are using, the order in that case seems to matter but in a situation where all the items are chain together, there is not really a 'first item'.

Here is an example of a source list that will have that problem:

Here is the history for each item at the source:

and

When we copy, one of those item will be put before its dependency obviously. This item will be changed. Here is the result after our migration:

This look good, but here is their versions:

and