Share via

Facing Issue While using the Azure Devops Migration Tool, Migrating Project from One Organization to another Organization in ADO

Swapna nela 0 Reputation points
2026-03-12T07:58:31.4366667+00:00

We are migrating projects from Source Azure DevOps Organization to a Target Organization.

I am planning to Migrate Work Items in the Project.

I am using Azure Devops Migration Tool Version 16.3.3 for this Migration.

URL : https://github.com/nkdAgility/azure-devops-migration-tools/releases/tag/v16.3.3

Config.json file:
{

        "Version": "16.0",

        "Serilog": {

          "MinimumLevel": "Information"

        },

        "MigrationTools": {

          "Endpoints": {

            "Source": {

              "EndpointType": "TfsTeamProjectEndpoint",

              "Collection": "https://dev.azure.com/$(SourceOrg)/",

              "Project": "$(ProjectName)",

              "Authentication": {

                "AuthenticationMode": "AccessToken",

                "AccessToken": "$(MIGRATION_PAT)"

              }

            },

            "Target": {

              "EndpointType": "TfsTeamProjectEndpoint",

              "Collection": "https://dev.azure.com/$(TargetOrg)/",

              "Project": "$(ProjectName)",

              "Authentication": {

                "AuthenticationMode": "AccessToken",

                "AccessToken": "$(MIGRATION_PAT)"

              },

              "ReflectedWorkItemIdField": "Custom.ReflectedWorkItemId"

            }

          },

          "Processors": [

            {

              "ProcessorType": "TfsWorkItemMigrationProcessor",

              "Enabled": true,

              "SourceName": "Source",

              "TargetName": "Target",

              "ReplayRevisions": true,

              "UpdateCreatedDate": true,

              "UpdateCreatedBy": true,

              "UpdateChangedDate": true,

              "UpdateChangedBy": true,

              "FixHtmlAttachmentLinks": true,

              "WIQLQuery": "SELECT [System.Id] FROM WorkItems WHERE [System.TeamProject] = @TeamProject ORDER BY [System.ChangedDate] desc"

            }

          ]    

        }

      }

 

ERROR:

Unhandled exception. System.InvalidOperationException: Failed to create ‘Source’ endpoint. Type not found for either main object or options: TfsWorkItemEndpoint at MigrationTools.EndpointRegistrationExtensions.AddEndPointSingleton(IServiceCollection services, IConfiguration configuration, IConfigurationSection endpointConfig, String endpointName, String endpointType) in D:\a\azure-devops-migration-tools\azure-devops-migration-tools\src\MigrationTools\Endpoints\Infrastructure\EndpointRegistrationExtensions.cs:line 94 at MigrationTools.EndpointRegistrationExtensions.AddConfiguredEndpoints(IServiceCollection services, IConfiguration configuration) in D:\a\azure-devops-migration-tools\azure-devops-migration-tools\src\MigrationTools\Endpoints\Infrastructure\EndpointRegistrationExtensions.cs:line 29 at MigrationTools.ServiceCollectionExtensions.AddMigrationToolServices(IServiceCollection context, IConfiguration configuration, String configFile) in D:\a\azure-devops-migration-tools\azure-devops-migration-tools\src\MigrationTools\ServiceCollectionExtensions.cs:line 36 at MigrationTools.Host.MigrationToolHost.<>c__DisplayClass1_0.<CreateDefaultBuilder>b__3(HostBuilderContext context, IServiceCollection services) in D:\a\azure-devops-migration-tools\azure-devops-migration-tools\src\MigrationTools.Host\MigrationToolHost.cs:line 108 at Microsoft.Extensions.Hosting.HostBuilder.InitializeServiceProvider() at Microsoft.Extensions.Hosting.HostBuilder.Build() at Microsoft.Extensions.Hosting.HostingHostBuilderExtensions.RunConsoleAsync(IHostBuilder hostBuilder, CancellationToken cancellationToken) at MigrationTools.ConsoleCore.Program.Main(String[] args) in D:\a\azure-devops-migration-tools\azure-devops-migration-tools\src\MigrationTools.ConsoleCore\Program.cs:line 28 at MigrationTools.ConsoleCore.Program.<Main>(String[] args) /home/vsts/work/_temp/7236e569-b0a6-41c8-822e-82b33f9f8a34.sh: line 4: 2160 Aborted (core dumped) dotnet “/home/vsts/work/1/migrationtool/preview/devopsmigration.dll” execute --config “/home/vsts/work/1/migrationtool/preview/config.json”

##[error]Bash exited with code ‘134’

 

Azure DevOps
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Praveen Kumar Gudipudi 1,880 Reputation points Microsoft External Staff Moderator
    2026-03-12T11:19:56.61+00:00

    Hello Swapna nela,

    Failed to create ‘Source’ endpoint. Type not found for either main object or options: TfsWorkItemEndpoint

    typically occurs when there is a configuration schema mismatch with the version of Azure DevOps Migration Tools being used.

    You mentioned that you are using version 16.3.3 of the Azure DevOps Migration Tool. In this version, the configuration schema has slightly changed, and the tool may fail to initialize the endpoint if the configuration version or endpoint definition does not fully match the expected structure.

    1. Update the configuration version

    Please update the Version field in your config.json to match the tool version.

    Current:

    "Version": "16.0"

    Update to:

    "Version": "16.3"

    2. Add the Name property to the endpoints

    In newer versions of the tool, it is recommended to explicitly specify the endpoint name inside the endpoint definition. For example:

    "Endpoints": {
  "Source": {
    "Name": "Source",
    "EndpointType": "TfsTeamProjectEndpoint",
    "Collection": "https://dev.azure.com/$(SourceOrg)/",
    "Project": "$(ProjectName)",
    "Authentication": {
      "AuthenticationMode": "AccessToken",
      "AccessToken": "$(MIGRATION_PAT)"
    }
  },
  "Target": {
    "Name": "Target",
    "EndpointType": "TfsTeamProjectEndpoint",
    "Collection": "https://dev.azure.com/$(TargetOrg)/",
    "Project": "$(ProjectName)",
    "ReflectedWorkItemIdField": "Custom.ReflectedWorkItemId",
    "Authentication": {
      "AuthenticationMode": "AccessToken",
      "AccessToken": "$(MIGRATION_PAT)"
    }
  }
}

    3. Confirm the tool execution

    From the logs it appears the tool is being executed through a preview DLL path. Please ensure that the correct binary from the downloaded release package is being used when running the migration.

    4. Verify PAT permissions

    Ensure that the Personal Access Token used for migration has sufficient permissions in both source and target Azure DevOps organizations, particularly:

    Work Items – Read & Write

    Project and Team – Read

    Identity – Read

    After making the above adjustments, please retry the migration.

    Please accept as answer and do a Thumbs-up to upvote this response if you are satisfied with the community help. Your upvote will be beneficial for the community users facing similar issues.

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.