Migration TFS to Azure DevOps for Release Items which is a link type

[asitjena79]

Hello Team,

I am working with a migration from TFS to DevOps Migration Tool version 11.9.31, where I am trying to migrate all the work items with the link type Release Items in TFS, but not able to. However, the child items are migrating successfully.

Found on DevOps - the link type is available as related. So in order to map these two ( TFS link type - Release Items and DevOps link type- Related), so that all the link type Release Items in TFS will link to the link type Related in DevOps

This is my JSON file
`
TFS-DevOps.json

Please suggest.

Thank you!
-Asit

[MrHinsh]

We dont provide any support for v11.9.31 which was shipped in Jan 21, 2021! We have had ~400 releases since then.

[nkdagility-actions-bot[bot]]

Hi there,

You're reporting a problem with an old version of the Azure DevOps Migration Tools. Please try the latest version and tell us if that fixes your problem. Bonus points for also trying with the latest preview version.

Good luck,

Thanks, Azure DevOps Migration Tools team

[ISSADMINS]

Hello Team,

Good day !

Thank you for the update and suggestion.

For the latest version - MigrationTools-16.1.0 , I am able to migrate the work items with closed and non-closed. While migrating the custom field value and the respective states, I am unable to migrate them to the target environment.

Please find my JSON file.

ADO-ADO Migration.Json

Please have a check and suggest - if anything I am missing here on my .json file.

Note : How do I migrate the link Type ( TFS link type - Release Items and DevOps link type- Related), so that all the link type Release Items in TFS will link to the link type Related in DevOps

Thank you!
-Asit

[MrHinsh]

All fields are migrated without the need for mapping if they are the same in the source and target. If they are different, you will need to apply a mapping.

By default all of the out of the box link types are migrted and mapped. Custom link types are not migrated.

---

Can you be more specific on whatss not working with each of the specific mappings that you are trying to configure?

[asitjena79]

Hello MrHinsh,

Good day!
Thank you for the update and information that Custom link types are not migrated.

Yes - the same fields are automatically mapped and migrated according to the source, as well as the target. The one whcih is not migrating is that - my source has a different field value whcih needs to be migrated to the target with a different field as follows.

For the task work item, the map below is in my JSON file, which is not working for state also.

"FieldMappingTool": {
"Enabled": true,
"FieldMaps": [
{
"ApplyTo": ["task"],
"FieldMapType": "FieldToFieldMap",
"sourceField": "Custom.PerformedBy", //Identity
"targetField": "Custom.TRequestor" //Identity
},
}

"FieldMapType": "FieldValueMap",
"ApplyTo": ["Task"],
//"defaultValue": "StateB",
//"sourceField": "System.State",
//"targetField": "System.State",
"valueMapping": {
"To Do": "New",
"In Progress": "Active",
"Done": "Closed",
"Removed": "Removed"
}

Attached JSON file.
ADO-ADO.Migration.Json

Please have a check and suggest!

Thank you!
-Asit

[MrHinsh]

Can you provide your log file?

[asitjena79]

Hello MrHinsh,

Good day!

Here is the log file.

migration2025062613.log
migration2025062614.log

Thank you!
-Asit

[nkdagility-actions-bot[bot]]

Hi there,

ACTION REQUIRED

In order for us to help you will need to provide both the log, and the configration file that you are using.

Generate and Attach Log

Steps:

1. In the Config file, change LogLevel to Debug.
2. Identify a work item ID that exhibits this issue and create a query that only selects this work item.
3. Delete any existing copy of that work item from the target.
4. Run the migration.
5. Comment here with the full Log attached as well as the full (redacted) configration file that you are using.

Your assistance is greatly appreciated!

Thanks, Azure DevOps Migration Tools team

[asitjena79]

Hello Team,

Here is my Logfile attached along with my .json file

LogFiles :
migration2025062613.log
migration2025062614.log

.JSON File

configuration.json

Please have a check and suggest.

Thank you in advance.

Thank you!
-Asit

[MrHinsh]

Your config is malformed. FieldMappingTool is inside WorkItemTypeMappingTool which measn it will neer run.

[ISSADMINS]

Hello MrHinsh,

Good day!

Thank you for your valuable time! It's working now for both the state value and custom fields.

It helped me a lot to migrate the data from on-premises to DevOps and within DevOps.

Thanks a lot.

Thank you!
-Asit