Can you map multiple source iterations to the same target iteration?

[chaurenservices]

Hello,

In my configuration file is it possible to map multiple source iterations to the same target iteration? In the example from my config file below, as soon as I map both Iteration 5 and Iteration 6 to the target Sprint 0, I get an error in the logs. If I take out one of these mappings or map it to a target sprint that hasn't been mapped yet, then it runs successfully. Examples below:

"Iterations": {
                  "Filters": [],
                  "Mappings": [
                    {
                      "Match": "^Our_Team\\\\Iteration 5 2025$",
                      "Replacement": "Sandbox\\Sprint 0"
                    },
                    {
                      "Match": "^Our_Team\\\\Iteration 6 2025$",
                      "Replacement": "Sandbox\\Sprint 0"
                    },
                    {
                      "Match": "^Our_Team\\\\Iteration 7 2025$",
                      "Replacement": "Sandbox\\Sprint 1"
                    },
                    {
                      "Match": "^Our_Team\\\\Iteration 8 2025$",
                      "Replacement": "Sandbox\\Sprint 2"
                    }
                  ]
                },
                "ReplicateAllExistingNodes": true,
                "ShouldCreateMissingRevisionPaths": false
              }

Log Errors:

[16:57:39 INF] [16.3.3] -> Settings found for team 'Our Team'..
[16:57:40 FTL] [16.3.3] Error while running TfsWorkItemMigrationProcessor
System.Web.Services.Protocols.SoapException: TF400495: A team iteration cannot be created for the specified iteration node. A team iteration already exists for that node.
   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 MigrationTools.Tools.TfsTeamSettingsTool.MigrateTeamSettings() in D:\a\azure-devops-migration-tools\azure-devops-migration-tools\src\MigrationTools.Clients.TfsObjectModel\Tools\TfsTeamSettingsTool.cs:line 188
   at MigrationTools.Tools.TfsTeamSettingsTool.ProcessorExecutionBegin(TfsProcessor processor) in D:\a\azure-devops-migration-tools\azure-devops-migration-tools\src\MigrationTools.Clients.TfsObjectModel\Tools\TfsTeamSettingsTool.cs:line 106
   at MigrationTools.Processors.TfsWorkItemMigrationProcessor.InternalExecute() in D:\a\azure-devops-migration-tools\azure-devops-migration-tools\src\MigrationTools.Clients.TfsObjectModel\Processors\TfsWorkItemMigrationProcessor.cs:line 129
   at MigrationTools.Processors.Infrastructure.Processor.Execute() in D:\a\azure-devops-migration-tools\azure-devops-migration-tools\src\MigrationTools\Processors\Infrastructure\Processor.cs:line 96
Error logged to Elmah.io!
!! Check for latest version - We fix issues constantly - If not, please create a discussion on https://github.com/nkdAgility/azure-devops-migration-tools/discussions so we can get this fixed !!
[16:57:40 INF] [16.3.3] TfsWorkItemMigrationProcessor completed in 00:00:10.1997420
[16:57:40 ERR] [16.3.3] TfsWorkItemMigrationProcessor The Processor MigrationEngine entered the failed state...stopping run
[16:57:40 INF] [16.3.3] Command ExecuteMigrationCommand completed in 00:00:19.3861519
[16:57:40 INF] [16.3.3] Check the logs for errors: C:\tools\MigrationTools\logs\20251120165719

I have multiple source iterations that need to go to the same target iteration "Sprint 0" since in our new setup, anything older than a certain time period will all be migrated to a single "Sprint 0". Any ideas?

Thank you!

[MrHinsh]

Note that you use 3 ticks bfore and after a multi line code statement. I updated you comment above.

---

You are hitting a bug in the team creation.. try turning it off with https://devopsmigration.io/docs/reference/tools/tfs-team-settings-tool/