The Veeam VM Migrator Utility is still the best way to re-map migrated VMs to pre-existing backup taken via your old vCenter server.

It is now built into the latest version of Veeam and run via Powershell, as opposed to the older executable version of the migrator.

There’s no other method to accomplish what this utility does, as far as I’m aware.

As noted by Tommy this is the best and only approach to keep the GUID the same and not break your chains.  Backup/Restore does not accomplish this task.

THX Tommy
I am not migrating all VMs at once. Is it possible to select in the script which VMs should be migrated?

Yes, after you run the “Generate-VBRViMigrationSpecificationFile” cmdlet, it will create a file you can open with notepad and edit it however you require before running the :Start-VBRViVMMigration” cmdlet.

(I believe it will only generate the file based on vms it sees have already been moved, but I’m not 100% certain off the top of my head, you may want to test this behavior).

​@dario72 ,Also, as this is modifying the Veeam database, make sure you take a configuration backup before doing anything. 

I really did not know that this is possible. Really good to know!

When your VMware team migrates to a new vCenter without telling you, and you really need to avoid breaking GFS retention or requiring an Active Full, it is very useful! (I may be speaking from experience)