Hello @Axel Stallknecht Sorry for the inconvenience this must have caused!
The issue seems to occur only when move across regions is triggered from the Virtual Network blade. We have identified the issue and the fix for this should get deployed in next few days.
For the time being, can you please add virtual networks to move from the Azure Resource Mover blade. (Move resources across Regions tab). This should work fine.
----------------------------------------------------------------------------------------------------------------------
If the response helped, do "Accept Answer" and up-vote it