Unable to migrate process templates using witadmin command, workitems migration throwinf missing fields #2064
ashokvundavalli
started this conversation in
General
Replies: 2 comments 3 replies
-
No, you need to migrate the fields yourself! |
Beta Was this translation helpful? Give feedback.
0 replies
-
Thanks for the reply Martin, I have created the fields manually in ADO but ther is a mismatch in the namespace (ex: filed in TFS has namespace as Aderant.Custom.ClientID In ADO I create the ClientID filed and its namespace shows Custom.ClientID) due to this the migration tool is ignoring the field and logging error saying filed is not available in the destination. Can you please let me know how I can map the fields in the config file.
Ashok Vundavalli
Principal Dev Ops Engineer
Email: ***@***.***
www.aderant.com
|
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have tried migrating work items from TFS 2018 to Azure DevOps. I received errors related to missing fields. I tried to export the process template from TFS and import to ADO using witadmin command, from the documentation I have learned that import is not possible with ADO.
Please let me know if the tool helps migrating the process templates before the actual migration of the work items.
Beta Was this translation helpful? Give feedback.
All reactions