API v1 vs API v2 for moving project from one collection to another

[anish2808]

Hello, I'm looking for some help in understanding API v1 vs v2 for moving items from one collection to another,
I would like to move Work items, team settings, area paths, iteration paths, project settings, project members, Test plans, Test Suites, Shared Queries etc.
What is the best approach based on your experience? I know there's an order to running processors, so if someone can shed some light here, that would be very helpful too.
Any resources/documentation on this process would also be highly appreciated.

Thank you.

[MrHinsh]

Some processors are in v1 and others are in v2. The difference is the format of the configuration file.

Example v1 Config: https://nkdagility.com/learn/azure-devops-migration-tools/Reference/v1/
Example v2 Config: https://nkdagility.com/learn/azure-devops-migration-tools/Reference/v2/

The order would be:

• Move your Git repos
• WorkItemMigrationContext
• TestConfigurationsMigrationContext
• TestVariablesMigrationContext
• TestPlansAndSuitesMigrationContext

Other than that an that its up to you.

[anish2808]

For WorkItemMigrationContext - My source has work items of the type - Code Review Request and Code Review Response. It is impossible for me to add the ReflectedWorkItemID to these fields since I can neither see them on the UI (Throws error VS403066 - Work item type Already in use when trying to add it to a custom Inherited process) in the destination project or edit them using Witadmin.

What is the solution for this?

[MrHinsh]

It is not possible to migrate Code Review Request and Code Review Response work items as they are intrinsically coupled to TFVC.

They should be excluded from any migration.