Is it possible to have multiple migration jobs in the same Azure Migrate project?

Question

I've done various migrations of local servers (physical and virtual) to Azure before, and they have worked out great, but I have a different scenario where this time not all the servers are being migrated at the same time. In this scenario I have 15-30 servers that need to be migrated, but they can't all be migrated at once. I've gone through the discovery and assessment phase using a migration appliance for a Hyper-V cluster migration as part of the migration project. Is it possible to basically have a "staged" migration where you setup multiple jobs to migrate 4-8 severs in the same migration project? Or do I need to create different migration project for each job or set of servers I want to migrate at the same time? I would have thought that this is possible, but I can't find any information confirming if this is a possible setup.

Answer 1

If the question is regarding sequencing the migration of servers in a mutually exclusive way (i.e. wait until the previous set of servers have migrated/replicated before starting the next batch) then the answer is: there is no direct way to support that in the product as of now. workaround: use custom scripts to trigger and sequence replication/migration over Migrate APIs.

Answer 2

Hey, As mentioned, you should be able to automate it using APIs. https://azure.microsoft.com/en-us/blog/atscale-migration-automation-support-with-azure-migrate-and-azure-powershell/

You can also use StarWind V2V cli to automate the process of migration. https://www.starwindsoftware.com/v2v-help/CommandLineInterface.html

Cheers,

Alex Bykovskyi

StarWind Software

Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.