We still like to have this opportunity to copy a List with the ID´s 1:1 with Username and versioning of the element !!!
Please create a new feature to use simply ShareGate instead of our own powershell script.

In the past (approx. ShareGate version 6) I was able to prepopulate my target list with enough dummy items for all needed id's, add a number column called SPID to the target list and populate it to match the id number, then copy content from the source list to the destination, mapping ID to SPID. That no longer works. It seems only complex keys now work. What happened to single column key mapping????? Why did you take it away?

We use Metalogix for migration of lists where the ID must stay the same :) ....GUYS!?

Yes I need this

yes i need this

Preserve GUID property of an item during a migration ($li.FieldValues.GUID).

IDs shoudl be preserved as part of migration. There might be custom code solutions expecting certain IDs.

Preserve list item id after migration

Most of the functionalities are based on the list item id, so after migration if list item changes , it is difficult to restore the same functionality again in target. It will be better if list item ids are preserved during migration.

SegreGate will preserve ids if "Insane mode" is on and also target environment should not be on-premise.

The ability to preserve list IDs is an important option. It would be nice it there was an option to do this as needed, since it doesn't always matter. In some cases we have lists that rely on the item ID. Having that change during migration becomes a huge problem. I've seen the workaround, but that only works in limited situations.

Newsfeed Lists
keep List item id's

Adding the list item GUID information would help this user associate the flawed items with his environment