Skip to main content
Solved

Alternative to Veeam VM Migrator Utility


Forum|alt.badge.img

I need to migrate multiple VMs from the old vCenter to the new one and want to keep the existing Veeam backup chain. Is there an easier method than the Veeam VM Migrator Utility?

Best answer by Tommy O'Shea

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.

View original
Did this topic help you find an answer to your question?

7 comments

Tommy O'Shea
Forum|alt.badge.img+3
  • Experienced User
  • 104 comments
  • Answer
  • March 27, 2025

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.


Chris.Childerhose
Forum|alt.badge.img+21

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.


Forum|alt.badge.img
  • Author
  • Comes here often
  • 12 comments
  • March 27, 2025

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

 


Tommy O'Shea
Forum|alt.badge.img+3
  • Experienced User
  • 104 comments
  • March 27, 2025
dario72 wrote:

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).


Tommy O'Shea
Forum|alt.badge.img+3
  • Experienced User
  • 104 comments
  • March 27, 2025

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


wolff.mateus
Forum|alt.badge.img+11
  • Veeam Vanguard
  • 541 comments
  • March 28, 2025
Tommy O'Shea wrote:

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.

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


Tommy O'Shea
Forum|alt.badge.img+3
  • Experienced User
  • 104 comments
  • March 28, 2025
wolff.mateus wrote:
Tommy O'Shea wrote:

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.

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)