Migrating nested Task Groups

[dduede]

We are trying to migrate a few hundred task groups. A lot of these use nested task groups inside them, sometimes multiple layers deep. It seems that the migration tool cannot handle these at all. I.e. we have the Task Group: Install Runtime and another Task Group: Deploy Service which uses the Task Group: Install Runtime. In the log we can see just the error

2023-03-22 15:25:44.746 +01:00 [WRN] TaskGroup "Deploy Service" cannot be migrated because the Task(s) "Install Runtime" are not available. This usually happens if the extension for the task is not installed.

But we can see the Install Runtime Task Group in the new project, which means it was migrated successfully - just the Deploy Service Task Group is missing.

Is this a bug or are we doing something wrong?

[MrHinsh]

@tomfrenzel added a fix for this as it would just fail before.

The extension that contains the Install Runtime task needs to be installed from https://marketplace.visualstudio.com in the Target environment before running the migration.

It's best to install all of the Extensions from the Source collection/organisation onto the Target collection/organisation!

[Xalcon]

It's not an extension. Install Runtime is just a Task Group with an Azure Powershell Task. Azure Powershell is installed and working.
There is no problem with this task group.

Install Runtime was migrated successfuly.

Deploy Service is a Task Group which has - as its only task - the Task Group Install Runtime. Migrating the Deploy Service Task Group fails with the mentioned error message.