Can the shared query migrator facilitate mapping of states and area/iteration paths?

[syeduali93]

Hi there, we used this tool to do a migration of work items from one azure DevOps project to another and it worked really well. Thanks! We wanted to utilize the query migrator feature to migrate our (over 1000+ queries) to our new project, however, there are a few variances between our project. Specifically, Area/ITeration paths have been modified in the target system and also the states. For the work item migration, we utilized the mapping array to map values for work items and I was wondering whether we could use a similar approach for query migration. I have tried but it seems like the only acceptable Type is Dictionary, and not really sure how we can achieve that.