Forum Discussion
Satyam569
Aug 30, 2023Copper Contributor
Some workitem fields are missing Post Azure DevOps Migration to Cloud
We have recently completed dryrun activity for Migration of Azure DevOps Server (On-prem) to Azure DevOps Services (Cloud) As part of that, our expectation is that, all the details of work items etc...
Kidd_Ip
Aug 26, 2025MVP
How about this:
- Audit Missing Fields
Use PowerShell or REST API to compare field definitions between source and target:
# Example: List fields in a work item type
Get-WorkItemType -Project "YourProject" -TypeName "Bug" | Select-Object -ExpandProperty Fields
Or use the REST API:
GET https://dev.azure.com/{organization}/{project}/_apis/wit/workitemtypes/{type}/fields?api-version=7.1-preview.2
- Update Target Process
If fields are missing in the cloud process:
- Go to Organization Settings > Process > [Your Process] > Work Item Types
- Add the missing fields manually
- Ensure field names and reference names match the source
- Re-run Migration with Field Mapping
Update your migration config to include field mappings:
{
"FieldMapType": "FieldToFieldMap",
"SourceField": "Custom.OldFieldName",
"TargetField": "Custom.NewFieldName"
}
You can also use FieldToFieldMultiMap for multiple mappings.
- Use WorkItemTypeMappingTool (if types changed)
If work item types were renamed or restructured, map them explicitly:
{
"WorkItemTypeNameMap": {
"Bug": "Defect",
"Task": "WorkItem.Task"
}
}
- Enable Analytics for Retrospective Reporting
Once fields are restored, enable Analytics Views in Azure DevOps Services to build retrospective dashboards and reports.