migration-tools | Migration tools for NuoDB | Database library

I found a possible solution. I have created a custom process, change the process from the projects to this new one and add a new field. This is the field I'm using on the configuration.json and now I'm able to migrate work items

I use their migrator quite often and I took a look into your issue.

I was able to replicate your issue exactly. When I dug into the exception, it looks like they changed their implementation of the TfsTeamSettingsProcessorOptions to not use the Source and Target nodes, despite this configuration being in their documentation.

What you'll need to do is update your TfsTeamSettingsProcessorOptions to point to named TfsEndpoints configured within the Endpoints array using SourceName and TargetName attributes.

It would look something like this in your case:

This issue is solved in this ticket on github. I post the answer here. So it would be helpful for other members who get the same issue to find the solution easily.

In the configuration file, language maps are invalid:

The tool does not update inline links.

This is an implementation issue as we migrate by iterating through all of the existing work items. For integrated links we can just add links to work items that exist in the target, and it will add from both ends once the other item is added.

For example if we are migrating 1, 2, 3 and 1, 2 reference 3 then:

1. #1 is migrated and no links are added as #3 does not exist
2. #2 is migrated and no links are added as #3 does not exist
3. #3 is migrated and links are added to #1 and #2

At the point of adding #3 and creating the links there is no way to know which work items have inline links to any other work items.

Ideas for fixing

OK, so that's how the tool currently works, so I am imagining a fix. Ther could be an option "RefactorInlineLinks" that parsed any description that it encountered and fixed the link if it was in scope for the migration.

However this would only work as a second pass after the migration was completed and all of the work items that will exist do exist.

You should be able to remove the [Microsoft.VSTS.Common.ClosedDate] = '' condition from the QueryBit object of the WorkItemMigrationConfig processor. In your specific case, I would change the line to the following.

After reviewing the documentation, I found the SkipToFinalRevisedWorkItemType configuration element for the VstsSyncMigrator.Engine.Configuration.Processing.WorkItemMigrationConfig processor. The docs are a bit cryptic, but I tried setting this configuration element to true and found it eliminated the save exceptions, resulting in successful migration and no blank-titled work-items.

I searched all issues and did not find mention of the SkipToFinalRevisedWorkItemType except in one closed issue that included a configuration.json listing.

If the intended functionality of the SkipToFinalRevisedWorkItemType is to address this Save exception, I would suggest a documentation update to indicate that work-item types that were changed will fail to save when replaying revisions unless SkipToFinalRevisedWorkItemType is set to true. Ideally, a code update that resulted in more graceful/informative exception handling would be added, if not functionality that could successfully navigate work-item type changes when replaying revisions.

If none of those options are possible at present, then this issue can be closed to serve as nominal documentation.

My Google-fu was strong today! Here's a link to a script that does almost exactly what I want.
Migrate Azure DevOps work items queries to a new organization

The only difference is that I am staying within my Organization, so making mods accordingly. Also, the Azure Rest API has probably evolved a bit since the original script was written, so I am updating the requests to handle that.

Thanks Josh Kewley!

Since it is not posible to migrate the build history it is not posible to migrate build links. It would probably be better if those links were not migrated at all to prevent the red.