Pipelines migration multiple problems

[phas13]

We are trying to migrate CI/CD from Azure SaaS to Azure SaaS.

As a preliminary step, we have migrated git repos using the git command(not via Azure Import repository).

I have multiple problems/questions with this migration.

1. Release pipelines were migrated without history, and what is more important, without Azure Repository Git artifacts attached. In fact, I can not say it is migrated, because now I need to fix each release pipeline by comparing with source and reattaching all artifacts. Is there a way how to make full migration without manual intervention?

2. As there is nothing related to repositories migration, I understand it is a very manual operation, because the recommended in multiple sources way(using git), does not migrate repository policies. So, now I need manually compare each repo and setup missed policies :(. Is there a way how to migrate it?

3. We have successfully migrated variable groups, task groups, something from release pipelines, but build pipelines part failed with error:

[17:12:30 FTL] Error while running AzureDevOpsPipelineProcessor
System.NullReferenceException: Object reference not set to an instance of an object.
   at MigrationTools.Endpoints.AzureDevOpsEndpoint.<UpdateTaskGroupsAsync>d__9.MoveNext() in D:\a\1\s\src\MigrationTools.Clients.AzureDevops.Rest\Endpoints\AzureDevOpsEndpoint.cs:line 252
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at MigrationTools.Processors.AzureDevOpsPipelineProcessor.<CreateTaskGroupDefinitionsAsync>d__25.MoveNext() in D:\a\1\s\src\MigrationTools.Clients.AzureDevops.Rest\Processors\AzureDevOpsPipelineProcessor.cs:line 501
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at MigrationTools.Processors.AzureDevOpsPipelineProcessor.<MigratePipelinesAsync>d__9.MoveNext() in D:\a\1\s\src\MigrationTools.Clients.AzureDevops.Rest\Processors\AzureDevOpsPipelineProcessor.cs:line 89
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at MigrationTools.Processors.AzureDevOpsPipelineProcessor.InternalExecute() in D:\a\1\s\src\MigrationTools.Clients.AzureDevops.Rest\Processors\AzureDevOpsPipelineProcessor.cs:line 47
   at MigrationTools.Processors.Processor.Execute() in D:\a\1\s\src\MigrationTools\Processors\Processor.cs:line 106

I have reviewed a lot of resources with the same problem, but any of the proposed fixes does not help in our case.

We use the last 11.11.23 version. Here is configuration file we use:

{
  "Version": "11.11",
  "workaroundForQuerySOAPBugEnabled": false,
  "ChangeSetMappingFile": null,
  "LogLevel": "Verbose",
  "Endpoints": {  
    "AzureDevOpsEndpoints": [
      {
        "Name": "Source",
        "$type": "AzureDevOpsEndpointOptions",
        "Organisation": "https://dev.azure.com/SomeSourceName/",
        "Project": "PInC",
        "AuthenticationMode": "AccessToken",
        "AccessToken": "************************",
        "EndpointEnrichers": null
      },
      {
        "Name": "Target",
        "$type": "AzureDevOpsEndpointOptions",
        "Organisation": "https://dev.azure.com/SomeTargetName/",
        "Project": "Insights",
        "AuthenticationMode": "AccessToken",
        "AccessToken": "************************",
        "EndpointEnrichers": null
      }
    ]
  },
  "GitRepoMapping": null,
  "Processors": [
    {
      "$type": "AzureDevOpsPipelineProcessorOptions",
      "Enabled": true,
      "MigrateBuildPipelines": true,
      "MigrateReleasePipelines": true,
      "MigrateTaskGroups": true,
      "MigrateVariableGroups": true,
      "MigrateServiceConnections": true,
      "BuildPipelines": null,
      "ReleasePipelines": null,
      "ProcessorEnrichers": null,
      "SourceName": "Source",
      "TargetName": "Target"
    }
  ]
}

[phas13]

Also, i have mentioned, release pipelines migrated without Agent Specification... In spite of the fact that I can choose correct specification, it is available, but looks like migration tool just skip it in migration time.

[pmukherjee13]

I am facing the same issue release pipelines migrated without Agent Specification. any help will be much appreciated.

[MrHinsh]

Check the new docs on https://nkdagility.github.io/azure-devops-migration-tools/Reference/v2/

[phas13]

Well, for us this tool was useful only for migration VariableGroups, TaskGroups, ServiceConnections. All other stuff(git including policy and settings, Secure Files, Build pipelines, release pipelines, environments, service hooks etc) we migrated with our own scripts based on Azure DevOps RestAPI.

To be honest, even Work Item migration is a pain, because of a mess with links. Under the hood, links are attached to work items using internal id, but on target azure, this id is not equal to source id, it can be missed or can be in another project. And we have a huge mess. We would like not to migrate wrong links, but it is not possible not to do this...

What I can say not about this tool - it can be useful for extremely simple migration :( Unfortunately.