TF400499 When trying to migrate teams with settings

Greetings… We’re attempting to migrate from a cloud instance of Azure Devops to a Devops Server 2019 instance.

Looks like we’ve been able to achieve moving most things over via your tool… but when trying to migrate teams with team settings, I get the following error.

Processing team '<Team Name>':    
-> Team '<Team Name>' created
-> Processing team '<Team Name>' settings:  
-> Settings found for team '<Team Name>'..   
migration.exe Warning: 0 :   [EXCEPTION] System.Web.Services.Protocols.SoapException: TF400499: You have not set your team field.
 at Microsoft.TeamFoundation.Client.Channels.TfsHttpClientBase.HandleReply(TfsClientOperation operation, TfsMessage message, Object[]& outputs) 
at Microsoft.TeamFoundation.Client.Channels.TfsHttpClientBase.Invoke(TfsClientOperation operation, Object[] parameters, TimeSpan timeout, Object[]& outputs)        
at Microsoft.TeamFoundation.ProcessConfiguration.Client.TeamConfigurationService.SetTeamSettings(Guid teamId, TeamSettings teamSettings) 
at Microsoft.TeamFoundation.ProcessConfiguration.Client.TeamSettingsConfigurationService.SetTeamSettings(Guid teamId, TeamSettings settings)
 at VstsSyncMigrator.Engine.TeamMigrationContext.InternalExecute() in C:\Users\source\repos\azure-devops-migration-tools\src\VstsSyncMigrator.Core\Execution\MigrationContext\TeamMigrationContext.cs:line 109                            at VstsSyncMigrator.Engine.MigrationContextBase.Execute() in C:\Users\source\repos\azure-devops-migration-tools\src\VstsSyncMigrator.Core\Execution\MigrationContext\MigrationContextBase.cs:line 35                                  MigrationEngine: The Processor TeamMigrationContext entered the failed state...stopping run

Configuration for team migration was as such:

{
      "ObjectType": "VstsSyncMigrator.Engine.Configuration.Processing.TeamMigrationConfig",
      "Enabled": true,
      "PrefixProjectToNodes": false,
      "EnableTeamSettingsMigration": true
    }

[rogerperez1]

Still an issue

[lymedo]

I think I know the reason for this issue. When the Team is migrated, there is no default backlog iteration set in Team configuration > Iterations. When you navigate to this page, you will see an error message. If you set the default backlog issue, the exception is no longer raised in the tool…